Hello, If a query contains a connective predicate with string ids, it fails with an IllegalArgumentException: gremlin> g.V().or(has(T.id, "1933504"), has(T.id, "2265280"), has(T.id, "2027592")) java.l

Hi Marc, Your solution works if the configuration hasn't been changed yet. If you change the index backend and set a wrong hostname, you cannot access your data anymore: mgmt = graph.openManagement()

Hi Marc, IMHO, an index should not prevent a query to work. Moreover the result of a query should not depends of backends (storage and index). If an index backend cannot process a predicate, the predi

Hi, With JanusGraph 0.6.0 and Lucene index backend, queries fail if they contain predicate like textNotPrefix, textNotContains: java.lang.IllegalArgumentException: Relation is not supported for string

Thank you, this is exactly what I look for.

Hello, The vertex that has just been created are not immediately available on mixed index (documented here [1]). I'm looking for a way to make sure the vertex is indexed, by waiting the mixed index ba

I confirm, adding lucene-backward-codecs-8.9.0.jar in lib folder solves my problem. Toom.

Hi, I'm testing the new pre-release of Janusgraph (from https://github.com/JanusGraph/janusgraph/releases/download/v0.6.0/janusgraph-0.6.0.zip) with the Berkeley/Lucene database created from JG 0.5.3

Hello, I encounter the error describe in the issue #1916 (https://github.com/JanusGraph/janusgraph/issues/1916) on a mixed index (lucene). When I list property keys of the index, they are all duplicat

Thank you for your reply. In my case I can remove the database and create a new one. But what should I do if I want to retrieve data from a JanusGraph database in which the configured index backend is

Hi, I am in a case where the index backend has been incorrectly configured to Elasticsearch. Now, when I try to instantiate my graph database, I get a "ConnectException: Connection refused", even if I