Hi Marc, Thanks for the feedback and suggestion. We investigated applying the JanusGraphFactory inside a singleton object as you've suggested, but ran into the issue that the JanusGraphFactory is not

Hi Pawan, You are right, if issues already arise without index, you should investigate that first, even though a large graph without indices is useless in itself. See the third question from Boxuan Li

Hi Marc, Thanks a lot for looking into this. As requested, I filled an issue about this on Github: https://github.com/JanusGraph/janusgraph/issues/2950 Thanks, Peter

Hi Marc, I don't think data cache was created due to elastic search/mixed index only. I have seen this on basic property/node without index as well. I am thinking let's work on basic node/property

Hi Peter, Thanks for reporting. I think it is a bug. I checked with the standalone gremlin REPL of janusgraph-0.6.0, using: graph = JanusGraphFactory.open('conf/janusgraph-inmemory.properties') This

Hi Harshit, The performance impact for JanusGraph when including a property key in multiple mixed indices, is negligable (the selection of the index for a specific query will be a tat slower).

Hi Pawan, OK, let's investigate further. You say that the issue occurs for both vertex creation and modification. Let's take the clearest case first: vertex creation with an indexed property. So, in

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

Hi Harshit, The concept "property is indexed or not" is ambiguous because an index can have multiple property keys. If you want to know if there is an index with a specific property key as the only

Hi Marc, I have removed cache properties from instances and we already have new transactions for each api operation but still facing stale data issues in other instances for some time. Below is the

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 =

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

Can you post the stacktrace (or the place where NPE is thrown)?

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.