I had to try for myself and, indeed, the ref docs are not very clear about this. In order to give the second graph a separate, independent mixed ndex you have to adapt the properties file for the seco

Hi Matt, Correct, but you should really try this out and see for yourself. Also check the janusgraph db folder after having created two graphs and see what files are created. Per graph, but you realiz

Hi Umesh, No, it is not clear at all whether the issue and cassandra-4.0 are related, but generally it is not useful to report bugs regarding unsupported configurations. To dig deeper, I would be curi

Hi Umesh, On the first line of your first post you state that you use cassandra-4.0. However, support for cassandra-4.0 is still an open issue: https://github.com/JanusGraph/janusgraph/issues/2325 htt

Hi Umesh, Can you please add the graph properties (configs) and the statements for creating the vertex labels in the graph schema (if any)? Cheers, Marc

Hi Matthew, I suppose you mean identifiers instead of indices? The identifier space is per graph. The storage backends make separate files per graph. Marc

Hi Pawan, Interesting, I could not find a JanusGraph unit test for this basic scenario (there is one with two instances and an index, though). This needs more investigation. Meawhile, are you sure tha

Hi Matthew, It would be possible to replace the employedBy, isSoldby, isLeasedBy relations with a relatedToCompany relation with employment, selling and lease properties. But I do not see any advantag

Hi Tendai, "Not serializable" sounds as if you pass a JanusGraph instance from the Spark driver to the executor. The function that runs on the Spark executor should call some static function on the si

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 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 g

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). Additio

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 y

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 ke

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 https://docs.janusgraph.org/advanced-topics/eventual-c

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 transac

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

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

Have you tried to increase JVM memory settings for JanusGraph Server? Also, check the settings for the database cache size, because I tend to remember that each graph has its own cache. Can you provid