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 things are breaking in my local

On Mon, Jan 10, 2022 at 5:23 PM Boxuan Li <liboxuan@...> wrote:

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 unable to reproduce it on 0.6.0. Can you try the 0.6.0 version?

--

Regards,

Harshit Sharma

+91-9901459920

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 unable to reproduce it on 0.6.0. Can you try the 0.6.0 version?

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

Do we need reindexing even for properties created after index?

On Mon, Jan 10, 2022 at 1:39 PM Harshit Sharma via lists.lfaidata.foundation <harshit.sharma1080=gmail.com@...> wrote:

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 property key "vertexA_key_s" in vertex_index

Created a vertex label -> vertexB

created a proproperty key -> vertexB_key_s

create mixedIndex if not exist -> vertex_index 

add property key "vertexB_key_s" in vertex_index

Created a edge label -> edge1

created a proproperty key -> edge1_key_s

create mixedIndex if not exist -> edge_index 

*Note -> We are crating index (vertex_index, edge_index) on the start of the service with some system properties like graphID, name, etc)

PrintIndexes in janusgraph -

Vertex Index Name. |    Type.  | Unique.  | Backing.   | key:   Status

--------------------------------------------------------------------------------------------

vertex_index. |    Mixed | false.  | search.   | vertexA_key_s: ENABLED

| vertexB_key_s: ENABLED

Edge Index (VCI) Name. |    Type.  | Unique.  | Backing.   | key  | Status

--------------------------------------------------------------------------------------------

edge_index. |    Mixed | false.  | search.   | vedge1_key_s: ENABLED

In elastic i'm able to search on that property using endpoint /_search?q=oltp_vertexA_key_s

On Mon, Jan 10, 2022 at 12:51 PM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

Thanks for the explanation. I noticed your example code contains the following snippet:

if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

I don’t have a computer with me right now, but IIRC there is no “addIndex” API. Do you mean by “addIndexKey”?

Another question: let’s say you create a new mixed index with property A. Later, you add a new property B to it using “mgmt.addIndexKey” API. Then you create a vertex with both property A and property B. Now, are you only able to leverage the mixed index to query property A only, but not property B? Also, what new document(s) do you observe on ES? A concrete example would be greatly appreciated if possible.

Best,

Boxuan

On Mon, Jan 10, 2022 at 3:04 PM Harshit Sharma <harshit.sharma1080@...> wrote:

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 and vertex/edge in the same transaction. Only property key and index creation are happening in one transaction that is also at starting of the service only. From next time is index already exists then my service adds new properties to it.

These new properties are created after the creation of the index in a separate transaction are visible in management API printIndexes and printSchema. Also, they are visible in elastic mapping.

On Mon, Jan 10, 2022 at 12:26 PM Boxuan Li <liboxuan@...> wrote:

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 in a new transaction. Can you give complete code examples that demonstrate how you do so in the same transaction AND in a new transaction, as Marc asked? Specifically, do include how you open and commit/rollback transactions.

In addition, I wonder if this always happens no matter how long you wait, or only happens in a short period of time. Schema propagation takes some time, and you may see a sync delay across JanusGraph instances. If you create the index on one JanusGraph instance, and immediately insert & query data in another JanusGraph instance, it might be the case that schema propagation is not done yet and your other JanusGraph instance is not aware of the recently created index.

Another thing you could check is the Elasticsearch. After creating the index, do you see the index on your ES cluster? After inserting vertices/edges, do you see documents created at ES side?

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:41 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Only For SET cardinality, I'm using TEXT mapping because looks like SET does not work with TEXTSTRING.

On Mon, Jan 10, 2022 at 11:07 AM Harshit Sharma via lists.lfaidata.foundation <harshit.sharma1080=gmail.com@...> wrote:

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?

On Mon, Jan 10, 2022 at 10:56 AM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

--

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 property key "vertexA_key_s" in vertex_index

Created a vertex label -> vertexB

created a proproperty key -> vertexB_key_s

create mixedIndex if not exist -> vertex_index 

add property key "vertexB_key_s" in vertex_index

Created a edge label -> edge1

created a proproperty key -> edge1_key_s

create mixedIndex if not exist -> edge_index 

*Note -> We are crating index (vertex_index, edge_index) on the start of the service with some system properties like graphID, name, etc)

PrintIndexes in janusgraph -

Vertex Index Name. |    Type.  | Unique.  | Backing.   | key:   Status

--------------------------------------------------------------------------------------------

vertex_index. |    Mixed | false.  | search.   | vertexA_key_s: ENABLED

| vertexB_key_s: ENABLED

Edge Index (VCI) Name. |    Type.  | Unique.  | Backing.   | key  | Status

--------------------------------------------------------------------------------------------

edge_index. |    Mixed | false.  | search.   | vedge1_key_s: ENABLED

In elastic i'm able to search on that property using endpoint /_search?q=oltp_vertexA_key_s

On Mon, Jan 10, 2022 at 12:51 PM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

Thanks for the explanation. I noticed your example code contains the following snippet:

if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

I don’t have a computer with me right now, but IIRC there is no “addIndex” API. Do you mean by “addIndexKey”?

Another question: let’s say you create a new mixed index with property A. Later, you add a new property B to it using “mgmt.addIndexKey” API. Then you create a vertex with both property A and property B. Now, are you only able to leverage the mixed index to query property A only, but not property B? Also, what new document(s) do you observe on ES? A concrete example would be greatly appreciated if possible.

Best,

Boxuan

On Mon, Jan 10, 2022 at 3:04 PM Harshit Sharma <harshit.sharma1080@...> wrote:

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 and vertex/edge in the same transaction. Only property key and index creation are happening in one transaction that is also at starting of the service only. From next time is index already exists then my service adds new properties to it.

These new properties are created after the creation of the index in a separate transaction are visible in management API printIndexes and printSchema. Also, they are visible in elastic mapping.

On Mon, Jan 10, 2022 at 12:26 PM Boxuan Li <liboxuan@...> wrote:

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 in a new transaction. Can you give complete code examples that demonstrate how you do so in the same transaction AND in a new transaction, as Marc asked? Specifically, do include how you open and commit/rollback transactions.

In addition, I wonder if this always happens no matter how long you wait, or only happens in a short period of time. Schema propagation takes some time, and you may see a sync delay across JanusGraph instances. If you create the index on one JanusGraph instance, and immediately insert & query data in another JanusGraph instance, it might be the case that schema propagation is not done yet and your other JanusGraph instance is not aware of the recently created index.

Another thing you could check is the Elasticsearch. After creating the index, do you see the index on your ES cluster? After inserting vertices/edges, do you see documents created at ES side?

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:41 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Only For SET cardinality, I'm using TEXT mapping because looks like SET does not work with TEXTSTRING.

On Mon, Jan 10, 2022 at 11:07 AM Harshit Sharma via lists.lfaidata.foundation <harshit.sharma1080=gmail.com@...> wrote:

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?

On Mon, Jan 10, 2022 at 10:56 AM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

Hi Harshit,

Thanks for the explanation. I noticed your example code contains the following snippet:

if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

I don’t have a computer with me right now, but IIRC there is no “addIndex” API. Do you mean by “addIndexKey”?

Another question: let’s say you create a new mixed index with property A. Later, you add a new property B to it using “mgmt.addIndexKey” API. Then you create a vertex with both property A and property B. Now, are you only able to leverage the mixed index to query property A only, but not property B? Also, what new document(s) do you observe on ES? A concrete example would be greatly appreciated if possible.

Best,

Boxuan

On Mon, Jan 10, 2022 at 3:04 PM Harshit Sharma <harshit.sharma1080@...> wrote:

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 and vertex/edge in the same transaction. Only property key and index creation are happening in one transaction that is also at starting of the service only. From next time is index already exists then my service adds new properties to it.

These new properties are created after the creation of the index in a separate transaction are visible in management API printIndexes and printSchema. Also, they are visible in elastic mapping.

On Mon, Jan 10, 2022 at 12:26 PM Boxuan Li <liboxuan@...> wrote:

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 in a new transaction. Can you give complete code examples that demonstrate how you do so in the same transaction AND in a new transaction, as Marc asked? Specifically, do include how you open and commit/rollback transactions.

In addition, I wonder if this always happens no matter how long you wait, or only happens in a short period of time. Schema propagation takes some time, and you may see a sync delay across JanusGraph instances. If you create the index on one JanusGraph instance, and immediately insert & query data in another JanusGraph instance, it might be the case that schema propagation is not done yet and your other JanusGraph instance is not aware of the recently created index.

Another thing you could check is the Elasticsearch. After creating the index, do you see the index on your ES cluster? After inserting vertices/edges, do you see documents created at ES side?

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:41 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Only For SET cardinality, I'm using TEXT mapping because looks like SET does not work with TEXTSTRING.

On Mon, Jan 10, 2022 at 11:07 AM Harshit Sharma via lists.lfaidata.foundation <harshit.sharma1080=gmail.com@...> wrote:

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?

On Mon, Jan 10, 2022 at 10:56 AM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

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 and vertex/edge in the same transaction. Only property key and index creation are happening in one transaction that is also at starting of the service only. From next time is index already exists then my service adds new properties to it.

These new properties are created after the creation of the index in a separate transaction are visible in management API printIndexes and printSchema. Also, they are visible in elastic mapping.

On Mon, Jan 10, 2022 at 12:26 PM Boxuan Li <liboxuan@...> wrote:

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 in a new transaction. Can you give complete code examples that demonstrate how you do so in the same transaction AND in a new transaction, as Marc asked? Specifically, do include how you open and commit/rollback transactions.

In addition, I wonder if this always happens no matter how long you wait, or only happens in a short period of time. Schema propagation takes some time, and you may see a sync delay across JanusGraph instances. If you create the index on one JanusGraph instance, and immediately insert & query data in another JanusGraph instance, it might be the case that schema propagation is not done yet and your other JanusGraph instance is not aware of the recently created index.

Another thing you could check is the Elasticsearch. After creating the index, do you see the index on your ES cluster? After inserting vertices/edges, do you see documents created at ES side?

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:41 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Only For SET cardinality, I'm using TEXT mapping because looks like SET does not work with TEXTSTRING.

On Mon, Jan 10, 2022 at 11:07 AM Harshit Sharma via lists.lfaidata.foundation <harshit.sharma1080=gmail.com@...> wrote:

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?

On Mon, Jan 10, 2022 at 10:56 AM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

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 in a new transaction. Can you give complete code examples that demonstrate how you do so in the same transaction AND in a new transaction, as Marc asked? Specifically, do include how you open and commit/rollback transactions.

In addition, I wonder if this always happens no matter how long you wait, or only happens in a short period of time. Schema propagation takes some time, and you may see a sync delay across JanusGraph instances. If you create the index on one JanusGraph instance, and immediately insert & query data in another JanusGraph instance, it might be the case that schema propagation is not done yet and your other JanusGraph instance is not aware of the recently created index.

Another thing you could check is the Elasticsearch. After creating the index, do you see the index on your ES cluster? After inserting vertices/edges, do you see documents created at ES side?

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:41 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Only For SET cardinality, I'm using TEXT mapping because looks like SET does not work with TEXTSTRING.

On Mon, Jan 10, 2022 at 11:07 AM Harshit Sharma via lists.lfaidata.foundation <harshit.sharma1080=gmail.com@...> wrote:

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?

On Mon, Jan 10, 2022 at 10:56 AM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

--

Regards,

Harshit Sharma

+91-9901459920

--

Regards,

Harshit Sharma

+91-9901459920

Only For SET cardinality, I'm using TEXT mapping because looks like SET does not work with TEXTSTRING.

On Mon, Jan 10, 2022 at 11:07 AM Harshit Sharma via lists.lfaidata.foundation <harshit.sharma1080=gmail.com@...> wrote:

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?

On Mon, Jan 10, 2022 at 10:56 AM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

--

Regards,

Harshit Sharma

+91-9901459920

--

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?

On Mon, Jan 10, 2022 at 10:56 AM Boxuan Li <liboxuan@...> wrote:

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

--

Regards,

Harshit Sharma

+91-9901459920

Hi Harshit,

You should use STRING mapping if you want exact string match. TEXT mapping is for full text search. See 

https://docs.janusgraph.org/index-backend/text-search/#full-text-and-string-search

Best,

Boxuan

On Mon, Jan 10, 2022 at 1:15 PM Harshit Sharma <harshit.sharma1080@...> wrote:

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

Hi Marc,

1. Creation of property keys and indices in the schema + commit

      graph = (Janusgraph) GraphDBConfigurator.getGraph()

      mgmt = graph.openManagement()

      

     For Vertex ->

           propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SET).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(VERTEX_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(VERTEX_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

  

    For Edge ->

            propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

             propertyKey = mgmt.makePropertyKey(propertyKeyName).dataType (String.class).cardinality(Cardinality.SINGLE).make()

          if(existingIndex) 

                janusgraphIndex = mgmt.getGraphIndex(EDGE_INDEX_NAME)

                mgmt.addIndex(janusgraphIndex, propertyKey)

          else

               indexBuilder = mgmt.buildIndex(EDGE_INDEX_NAME,  Vertex.class)

               if(cardinality is SET)

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXT.asParameter() : Mapping.DEFAULT.asParameter())

               else

                        indexBuilder.addKey(propertyKey, String.class.equals(propertyKey.dataType) ? Mapping.TEXTSTRING.asParameter() : Mapping.DEFAULT.asParameter())

         

            mgmt.commit();

    

       3.   Query of a vertex based on a property value in another transaction

             Let say i created a property key "domain_vertex_key1_s" for vertex

             Query = g.V().has("domain_vertex_key1_s", "val1);

             

             Let say I created a property key "domain_edge_key1_s" for edge

            

             Query = g.V().has("domain_vertex_key1_s","val2");

          

On Mon, 10 Jan, 2022, 12:46 am , <hadoopmarc@...> wrote:

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

Hi Harshit,

Can you please describe the steps you have taken in more detail:

• creation of property keys and indices in the schema + commit,
• creation of a vertex with a property in one committed transaction,
• query of a vertex based on a property value in another transaction.

Marc

Hi Pawan,

A couple of questions:

1. What do you mean by creating some data? For example, do you mean by creating new vertices or just updating existing vertices? If it’s the latter case, then you could try turning off cache.db-cache option as it might lead to stale data read.

2. What is your typical “duration” after which data gets reflected?

3. What is your cql replication factor and read & write consistency levels? Are they default values? Also, how many Cassandra nodes do you have and are they in the same data center?

Best,

Boxuan

On Thu, Jan 6, 2022 at 3:03 PM Pawan Shriwas <shriwas.pawan@...> wrote:

Hi All,

I am facing one problem for synchronization of data stored between multiple embedded mode janusgraph instances.

If we are creating some data into graph using JVM 1 and after committing when we get same data from JVM 2 its not reflecting for some duration.

I want to avail the same information to all instances after any CRUD operation once it gets committed.

I am using the same graph property in all instances of embedded janusgraph.

##############graph.properties#####################

gremlin.graph=org.janusgraph.core.JanusGraphFactory
storage.backend=cql
storage.hostname=cql-dns
storage.cql.keyspace=janusgraphdbks
storage.port=30808
storage.username=user123
storage.password=user12345
schema.default=none

schema.constraints=true

index.search-central-graph.backend=elasticsearch
index.search-central-graph.hostname=api-es-instance1:9200
index.search-central-graph.index-name=search-central-graph
index.search-central-graph.elasticsearch.http.auth.type=basic
index.search-central-graph.elasticsearch.http.auth.basic.username=admin
index.search-central-graph.elasticsearch.http.auth.basic.password=admin 

cache.db-cache = true
cache.db-cache-clean-wait = 20
cache.db-cache-time = 180000
cache.db-cache-size = 0.25
query.batch = true
query.fast-property = true
query.batch-property-prefetch = true
storage.buffer-size=1024

######################property file end############################

Please let me know if someone faces this and how to prevent this. 

Thanks,

Pawan

Hi All,

I am facing one problem for synchronization of data stored between multiple embedded mode janusgraph instances.

If we are creating some data into graph using JVM 1 and after committing when we get same data from JVM 2 its not reflecting for some duration.

I want to avail the same information to all instances after any CRUD operation once it gets committed.

I am using the same graph property in all instances of embedded janusgraph.

##############graph.properties#####################

gremlin.graph=org.janusgraph.core.JanusGraphFactory
storage.backend=cql
storage.hostname=cql-dns
storage.cql.keyspace=janusgraphdbks
storage.port=30808
storage.username=user123
storage.password=user12345
schema.default=none

schema.constraints=true

index.search-central-graph.backend=elasticsearch
index.search-central-graph.hostname=api-es-instance1:9200
index.search-central-graph.index-name=search-central-graph
index.search-central-graph.elasticsearch.http.auth.type=basic
index.search-central-graph.elasticsearch.http.auth.basic.username=admin
index.search-central-graph.elasticsearch.http.auth.basic.password=admin 

cache.db-cache = true
cache.db-cache-clean-wait = 20
cache.db-cache-time = 180000
cache.db-cache-size = 0.25
query.batch = true
query.fast-property = true
query.batch-property-prefetch = true
storage.buffer-size=1024

######################property file end############################

Please let me know if someone faces this and how to prevent this. 

Thanks,

Pawan