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

Do we need reindexing even for properties created after index?-- Regards, Harshit Sharma +91-9901459920

sorry for the typo, it is addIndexKey() only what I'm using. Example- Created a vertex label -> vertexA created a property key -> vertexA_key_s create mixedIndex if not exist -> vertex_index add

Hi Harshit, Thanks for the explanation. I noticed your example code contains the following snippet: if(existingIndex) janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

Hi Boxuan, Thanks for the quick response. Actually, I'm following a strict schema in my service. i.e we first register a schema and then use it for vertex/edge creation. So I'm not creating schema

Sorry I misread your email. I thought you were using TEXT mapping only. You said you were able to create index, add vertices and edges, and query them utilizing index in the same transaction, but not

Only For SET cardinality, I'm using TEXT mapping because looks like SET does not work with TEXTSTRING.-- Regards, Harshit Sharma +91-9901459920

but is that the reason I'm not able to use property keys created in a new transaction? Also, can we mix index property keys of cardinality SET? -- Regards, Harshit Sharma +91-9901459920