Hi Sergey, I think I see your point, but for completeness can you be explicit on step 1) and specify your mgmt.buildIndex() statements? Best wishes, Marc

Hi Toom, OK, I tried two things. I start with the janusgraph-full-0.5.3 distribution and run (this has gremlin server running with conf/janusgraph-cql-es.properties): $ bin/janusgraph.sh start Now I

Hi, the problem is probably simply that the Python driver doesn’t support serialization for JanusGraph predicates with GraphBinary. So, you would need to write your GraphBinary serializer for

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

Janusgraph setup: Storage backend: Scylla 3 Indexing backend: Elasticsearch 6 JG version: 0.5.3 Steps to reproduce: 1) Create a vertex with two fields mapped in ES index as TEXTSTRING("x" and "y") 2)

Hi, I'm trying to use JanusGraph's full-text predicates in the gremlin-python client library. Using GraphSON serializer, I can use a predicate with e.g. "textContains" as the operator and it works

Hi Vinayak, Your properties file says: spark.master=spark://127.0.0.1:7077 Do you have a spark standalone cluster running? Does the spark master reside on 127.0.0.1 and does it listen on 7077? With

Hi Vinayak, For other readers, see also this other recent thread. A couple of remarks: In the separate edge count does it make any difference if you select the edges by label rather than by property,

Hi All, gremlin> graph = GraphFactory.open('conf/hadoop-graph/read-cql-standalone-cluster.properties') ==>hadoopgraph[cqlinputformat->nulloutputformat] gremlin> g =

Hi, JanusGraph keeps a record of open instances that sometimes is not updated properly. You can clean it with the methods

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

Hi All, The Data Model of the graph is as follows: Nodes: Label: Node1, count: 130K Label: Node2, count: 183K Label: Node3, count: 437K Label: Node4, count: 156 Relations: Node1 to Node2 Label:

https://github.com/JanusGraph/janusgraph/issues/2558

Hi Anton, No, my last post only concerned the gremlin server on port 8185, although the first line of step3 should have been (This was a hand edit error): :remote connect tinkerpop.server

Hi Mark, I'm glad that you managed to reproduce it in the Gremlin Console. But I believe that in fact you do it with two JanusGraph servers, not with a single server as you assumed. As far as I

Hi All, query.batch = true AND query.fast-property = true this doesn't work. facing the same problem. Is there any other way?? Thanks & Regards, Vinayak

You could also check the scenario at line 65

Hi Anton, OK, it took me some time to reach your level of understanding, but hopefully the scenario below really starts adding to our common understanding. While the issue hurts you in a setup with

Hi, > 1. Is this behavior expected, or it's just bigtable or hbase that might have this issue? This (very likely) is not related to bigtable/hbase, but JanusGraph itself. > 2. What is the expected

Hi, We are running janusgraph on GCP with bigtable as the backend. I have observed some query behavior that really confuses me. Basically, I am guessing batch fetching from the backend is not