Hi Matthias, Thanks for taking the trouble to report this. It took a while, but your report did not go unnoticed: https://github.com/JanusGraph/janusgraph/issues/2857 Best wishes, Marc

Hi, There is an issue tracking this, but no PR's yet, see: https://github.com/JanusGraph/janusgraph/issues/2325 Best wishes, Marc

Hi Krishna, Nope. However, you are not the first to ask, see: https://stackoverflow.com/questions/46363737/tinkerpop-gremlin-merge-vertices-and-edges/46435070#46435070 Best wishes, Marc

Hi Hazal, Your comment is correct: the graph.set-vertex-id feature is not documented further than this, so using it is not advised. You are also right that lookups in the index require additional proc

I read some conceptual confusion, so let me try: a single query is handled by a single janusgraph instance (In this case JanusGraph Server) you can handle many queries from many nodejs clients in para

Hi Pawan, 1. See https://docs.janusgraph.org/schema/#displaying-schema-information 2. See the manuals of your storage and indexing backends (and older questions on this list) 3. Please elaborate; some

Hi Toom, Yes, you are right, this behavior is not 100% consistent. Also, as noted, the documentation regarding text predicates on properties without index is incomplete. Use cases are sparse, though,

Hi, There are three solution directions: if you have keys to your vertices available, either vertex ids or unique values of some vertex property, you can start as many gremlin clients as your backends

Hi Toom, See, https://docs.janusgraph.org/index-backend/text-search/#full-text-search_1 Indeed, the negative text predicates are only available to Elasticsearch (and, apparently as you say, to the Com

Hi Claudio, Paging with range can only work with a vertex centric index, otherwise the vertex table is scanned for every page. If you just want all results, the alternative is to forget about the rang

Hi Tanroop, Does the problem also occur if you replace v() with V().limit(1) inside your query? If not, at what result size does your issue start to occur? Btw, your post has a typo: "user" and "uidx"

Hi Pawan, OK, I did a small upgrade session myself and did not encounter any issues (apart from having to set numTokens: 4 in conf/cassandra.yaml). This is what I did: Start from a fresh janusgraph-fu

Hi Pawan, It seems I miss the practical experience, but it seems you have to set graph.allow-upgrade=true (although it is not clear whether this applies to all version changes or only to "storage vers

Hi Pawan, This part of your stacktrace suggests that something changed on your Cassandra cluster or with the graph_user. So, check the CREATE permission, with your admin or try to create a keyspace wi

Hi Mladen, You are right, your issue is different than the one I mentioned about GraphManager. I mentioned earlier that the JanusGraph test suite covers your use case: https://github.com/JanusGraph/ja

No, JanusGraph does not have a storage backend for a single-node cluster that persists to single file (such as sqlite would). It is possible though to have a single Cassandra instance co-hosted on you

Hi Mladen, After your original post, the following issue was reported: https://github.com/JanusGraph/janusgraph/issues/2822 Marc

Hi Mladen, The good news: there actually is an explicit MultiHost test for this in the janusgraph test suite: https://github.com/JanusGraph/janusgraph/blob/v0.6.0/janusgraph-cql/src/test/java/org/janu

Hi Anjani, In individual query for a subgraph of 40 nodes will typically take between 0.1 and 1 seconds (with scyllaDb being the fastest storage backend). The number of 200 TPS can be reached easily b

Hi Chris, Hard to interpret your report. It maybe worthwhile to try the documented way of remote connection with traversal.withRemote(...) or Cluster.open(...): https://tinkerpop.apache.org/docs/curre