Thank you so much Peter for the detailed answer! I think we need to switch betweenScyllaDB and Cassandra to understand the differences better. It is good that JanusGraph enables you to switch

Hi, ElasticSearch is used for mixed indexes only. If you don't use mixed indexes, you don't need ElasticSearch. All other indexes are stored in a storage backend you are using (Cassandra, HBase,

Hi, `count` step doesn't use mixed index right now. There is a WIP PR which will allow to use mixed index for count step: https://github.com/JanusGraph/janusgraph/pull/2200 Right now, the best you can

Hi Madhan, I am not familiar with this part thus cannot say much on this, but do you have any example (or even better, unit test) that can reproduce the issue? Regards, Boxuan

Created a PR to fix this bug: https://github.com/JanusGraph/janusgraph/pull/2244 Appreciate any review!

Transactions created in ConsistentKeyLocker.overrideTimestamp() are neither committed or rolled back by the callers. This results in leaked transactions. This issue (of leaked transactions) was seen

Hi, This is more about english than about java. I think the author means that if you get an answer after 10 seconds that you have the lock for 1 second starting 5 seconds ago, you need a new

Thanks Marc, for you help and time. Regards, Anjani

Hi Anjani, No, existing schema elements cannot be modified (apart from renames), see: https://docs.janusgraph.org/basics/schema/#changing-schema-elements Best wishes, Marc Op dinsdag 3 november

Thanks Mark, i missed step 4. Thank you very much for pointing it. One more question, Our graph is already running on prod and properties are defined but consistency is not set on them. If i add

Hi i am using Janus with hbase as storage backend. I am getting floowing exception while committing trasaction: 20/11/03 04:32:30 WARN consistentkey.ConsistentKeyLocker: Lock write succeeded but took

I am getting the same errors you got but the fix is not doing it for me. ```yaml hosts: [localhost] port: 8182 serializer: className:

Hi Anjani, See step 4 in the ref docs link I sent earlier: the locks are not released until the entire transaction is committed or rolled back. Marc Op maandag 2 november 2020 om 13:21:57 UTC+1

Hi Marc, Thanks for your detailed response. My understanding is node is locked automatically during operation and get released after it, does not wait for commit. Suppose i need to update 3 nodes. I

Hi Anjani, Do you mean that there are still (extremely rare) failure situations possible despite the use of locking and the use of JanusGraph transactions? I am not sure if I can think of one and it

Environment: JG-0.5.2 with HBase and Elasticsearch When running a java program to delete verteics and edges, many warnings "Lock write succeeded but took too long" show up. Wanting to know what

Comments inline. Everyone's going to have a bias, and I want to be transparent. I work for ScyllaDB, so of course I think they are the best. I will do my best, however, to give you reasons which I

Hi Marc, Thanks for your response. Earlier i had look on the page you shared and from that my understanding is we can define consistency at property level and if same property is modified by two

Hi Anjani, I am not sure if I understand your question and if your question already took the following into

Hi All, We are using Janus 0.5.2 with Cassandra and Elastic-search. Currently for adding or updating a node we are using gremlin queries in java. We have a use case where we need to update