Github user jhorcicka commented on the issue:
https://github.com/apache/metamodel/pull/179
Updated, @arjansh.
---
Github user jhorcicka commented on a diff in the pull request:
https://github.com/apache/metamodel/pull/179#discussion_r190797849
--- Diff:
neo4j/src/main/java/org/apache/metamodel/neo4j/utils/ColumnTypeResolver.java ---
@@ -0,0 +1,117 @@
+/**
+ * Licensed to the Apache Sof
The "Wide Column (store)" term comes from this article:
https://db-engines.com/en/article/Wide+Column+Stores.
Based on that article, I'm not sure if we should also use it for MongoDB,
CouchDB and Elasticsearch, but it seems like an option to introduce it and use
it for both Cassandra and HBase,
Github user arjansh commented on a diff in the pull request:
https://github.com/apache/metamodel/pull/179#discussion_r190560674
--- Diff:
neo4j/src/main/java/org/apache/metamodel/neo4j/utils/ColumnTypeResolver.java ---
@@ -0,0 +1,126 @@
+/**
+ * Licensed to the Apache Softw
Github user arjansh commented on a diff in the pull request:
https://github.com/apache/metamodel/pull/179#discussion_r190560349
--- Diff:
neo4j/src/main/java/org/apache/metamodel/neo4j/utils/ColumnTypeResolver.java ---
@@ -0,0 +1,126 @@
+/**
+ * Licensed to the Apache Softw
Github user arjansh commented on a diff in the pull request:
https://github.com/apache/metamodel/pull/179#discussion_r190558268
--- Diff:
neo4j/src/main/java/org/apache/metamodel/neo4j/utils/ColumnTypeResolver.java ---
@@ -0,0 +1,117 @@
+/**
+ * Licensed to the Apache Softw
