Introduced a workaround for the fact that Elasticsearch returns data based on indexed documents with dots in the field names in an inconsistent manner. I.e the mapping it returns for such documents indicate those kind of fields are treated as nested objects. But if you get the source map of such a document from Elasticsearch, it still contains the original fieldnames (with dots in them).
3 files changed
tree: 918acfa8054e677c1380ba173e1dfbfc2690e5b2
  1. arff/
  2. cassandra/
  3. core/
  4. couchdb/
  5. csv/
  6. dynamodb/
  7. elasticsearch/
  8. excel/
  9. fixedwidth/
  10. full/
  11. hadoop/
  12. hbase/
  13. jdbc/
  14. json/
  15. kafka/
  16. mongodb/
  17. neo4j/
  18. openoffice/
  19. pojo/
  20. salesforce/
  21. spring/
  22. sugarcrm/
  23. xml/
  24. .gitattributes
  25. .gitignore
  26. .travis.yml
  27. CHANGES.md
  28. CONTRIBUTE.md
  29. doap_MetaModel.rdf
  30. example-metamodel-integrationtest-configuration.properties
  31. LICENSE
  32. NOTICE
  33. pom.xml
  34. README.md
  35. travis-metamodel-integrationtest-configuration.properties
README.md

Apache MetaModel

MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores.

Mailing lists

Website

http://metamodel.apache.org/

Documentation

Please check out our wiki for user documentation.

Building the code

MetaModel uses maven as it's build tool. Code can be built with:

mvn clean install

Running the integration tests

  1. Copy the file ‘example-metamodel-integrationtest-configuration.properties’ to your user home.
  2. Remove the ‘example-’ prefix from its filename
  3. Modify the file to enable properties of the integration tests that you're interested in.
  4. Re-run “mvn clean install”.

Contributing

Please see CONTRIBUTE.md