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

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

Hi Marc, 1. Creation of property keys and indices in the schema + commit graph = (Janusgraph) GraphDBConfigurator.getGraph() mgmt = graph.openManagement() For Vertex ->

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

I'm working on a Janusgraph application. To improve gremlin query performance we are creating two mixed indexes, one for vertices and one for edges. Now Janusgraph can query indexes for property keys

Hi Pawan, Your requirement for instant synchronization cannot work with JanusGraph caches enabled, because JanusGraph will get data from the cache if available, instead of getting the latest data from

Hi Boxuan, Please see my inline response 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,

Same case also happened with two or more gremlin consoles as well where we are creating/updating something on console 1 and not reflecting on others.-- Thanks & Regard PAWAN SHRIWAS

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

Thanks team, I will check it based on your response and let you know if anything is needed.-- Thanks & Regard PAWAN SHRIWAS

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

Hmm, these figures seem perfectly reasonable. It seems I was also wrong about the db-cache heap region not being shared between graphs. So you have to gather more information about was is going wrong.

It is also possible to run spark on kubernetes (in combination with distributed storage like S3 or minio): https://spark.apache.org/docs/latest/running-on-kubernetes.html It will require some time to

Hi Pawan, Do you want to run Spark traversal on a Spark standalone cluster rather than a Hadoop Yarn cluster? In that case, you could follow the JanusGraph documentation or check out this guide on