That is not working. According to Documentation https://docs.janusgraph.org/schema/index-management/index-performance/ After build index i'm calling ManagementSystem.awaitGraphIndexStatus(graph,

Hi, Can someone please advise if previously mentioned way is incorrect for using lock consistencies on edge property keys (version in my case)? Regards, Aman

Hi Harshit, Can you check if https://groups.google.com/g/janusgraph-users/c/GfYM538KsTo helps? Best, Boxuan

Sorry because of type posting again - If I'm adding new keys to an existing index, many keys are getting stuck in the registered or installed state for example, I indexed a key "graphId" for the

If I'm adding new keys to an existing index, many keys are getting stuck in the registered or installed state for example, I indexed a key "graphId" for the vertex in an index graphVertexIndex while I

Hi All, I have a strange behaviour while using the addConnection method for creating JG schema constraints. It seems it creates duplicated connections in some cases. Please see below how to reproduce

I think I found the issue, I was using default mapping for all properties which are created in separate transactions. I have a few questions - 1. Does JG support TEXTSTRING mapping SET cardinality? 2.

Hi Marc, Thank you for your response. This is how I'm using it: 1. I created a property key called version, which is incremented at the service layer every time an update is made on an element (vertex

It looks something like this -> graph_search_graph-index-edge: { mappings: { - properties: { - all: { type: "text" }, - graphId: { type: "text", -copy_to: [ "all"] } -

Hi Aman, The JanusGraph docs on consistency, cqlLocking do not limit its use to vertices. Can you please show how you translated the example from

Could you please provide a ES mapping that was generated for this property?

Yes it is TEXTSTRING-- Regards, Harshit Sharma +91-9901459920

Hi, Is there a way by which I can prevent concurrent updates to edges? For vertices, I'm simply maintaining a version field with Lock consistency, so a concurrent update results in Permanent Locking

Hi, Is there a way by which I can prevent concurrent updates to edges? For vertices, I'm simply maintaining a version field with Lock consistency, so a concurrent update results in Permanent Locking

Sorry, I meant to ask Are you sure "key1" has TEXTSTRING mapping, rather than TEXT mapping?

Yes, key1 is of TEXT String mapping because I'm creating only TEXT or TEXTSTRING type of mapping. I can try to update but looks like an upgrade from 0.5.2 to 0.6.0 involve some major changes and

You mentioned that g.V().has("key1", textContains("val") ) is working while g.V().has("key1","val13") is not working Are you sure "key1" has TEXTSTRING mapping, rather than STRING mapping? I am

But this has query is working for other properties which are created in the same transaction as that of the index. They also have mapping as TEXTSTRING-- Regards, Harshit Sharma +91-9901459920

For these kind of queries you need TEXTSTRING mapping. As an alternative you can create composite index to "equals" queries

I tried following query g.V().has("key1", textContains("val") ) is working while g.V().has("key1","val13") is not working -- Regards, Harshit Sharma +91-9901459920