Hi Anatoly, i tired below and looks like indexes are working fine graph = JanusGraphFactory.open('conf/gremlin-server/janusgraph-cql-es-server.properties'); mgmt = graph.openManagement(); vid =

can you try below 2 properties ids.block-size=1000000000 ids.renew-percentage=0.3 -- Thanks Akhilesh

Found the issue. It was due to inclusion of netty-transport-native-epoll via another application dependency. It seems cassandra core driver 3.7.1 does not like if this library is present in the

I have a graph that I need to upload which has about 1000 vertices and 3000 edges. I tried to load it using commit after a) each iteration b) every 100th iteration c) after all data uploading It

Not sure if that can cause your problem but you need to configure storage.cql.keyspace instead of storage.cassandra.keyspace if you're using CQL and the same applies to the consistency levels. Am

Didnt help. Could this be a driver 3.7.1 compatibility issue with cassandra 3.11.3? Thanks Bharat

It depends on graph structure how many properties/edges Good starting point do commit every 10k vertices. Addition info about bulk loading

I tried to use custom ids for created vertices setting graph.set-vertex-id option. Now the most time is consumed by code that creates indices and calls ManagementSystem.getOrCreateVertexLabel() (it

Can you disable thrift on Cassandra and then try

I am using cql driver. I am getting below while opening connection. The C* is running on the localhost and listening on port 9042. Cassandra version is 3.11.3 Connection

I am trying to upload several thousands vertices into JanusGraph for my testing. Is there any performance benefits to commit the transaction after adding all vertices, after adding each vertex or may

Index management can stuck when another graph instances exists but invalid. Try to check mgmt.getOpenInstances() and close invalid if exists throught mgmt.forceCloseInstance(). Some of issues already

Index still doesn't work somehow: gremlin> g =

Hi Anatoly, "id" is the internal key used by janusgraph to represent vertex id. So I would suggest you to add a different key for your use case and build index on it it will work for sure . Hope this

I am using janusgraph version 0.3.1 with hbase and elasticsearch The below error occurs when property size is bigger than 32767 (Short.MAX_LENGTH) this value is hard coded in

I am developing my backend application in java using janusgraph database version 0.3.1 . I want to manage the saved files as properties for vertex in the graph. 1- Can I save images, xml files, text

The index was created with these commands: gremlin> vid = mgmt.getPropertyKey('id') ==>id gremlin> mgmt.buildIndex('byId', Vertex.class).addKey(vid).buildCompositeIndex() gremlin> mgmt.commit() One

Hi, How was your index defined? You've shown that it exists and is enabled but not the creation. Specifically, did you create it with a label constraint? If so, your traversal is not including the

Hi, Jun The methods buildEdgeIndex and buildRelationTypeIndex are

All entities needs assigned id: edges, vertices, properties and same for schema entities too. But this pause occurred not so frequently for each 10 000 ids by default You can trace pool size and