Will there be any performance impact if i will index a property key in multiple indices (mixed index)?

Is there a way I can check if a particular property is indexed or not? I know the following method but there I will have to traverse all indexes List<JanusgraphIndex> indexList = mgmt.getIndexes(Verte

Is it allowed to index the same property key in two different indexes. For example I created a property key graphId and created two indexes vertexIndex, edgeIndex. Index graphId in both indexes. The p

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, INDEX

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 verte

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

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.

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

Yes it is TEXTSTRING

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 thing

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

I tried following query g.V().has("key1", textContains("val") ) is working while g.V().has("key1","val13") is not working

Do we need reindexing even for properties created after index?

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 prope

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

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

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?

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

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