final GraphTraversal<Vertex, Vertex> query1 = graph.traversal().V(); final GraphTraversal<Vertex, Vertex> query2 = graph.traversal().V(); query1.has(vertexLabel, filterProperty,

Hi Nicolas, How do we know if the graph has been dropped? You said you have to restart the server after doing that. I am doing the same, but I don't want to. Is there any way of clearing all the data,

Hi, I am able to drop remotely the graph using the script: JanusGraphFactory.drop(graph);[] After the script, I need to restart janusGraph in order to re-create the graph. Could you sent the

This may be more of a Gremlin question but... I'm looking for a way to return property values in the proper format based on their Cardinality (LIST/SET vs SINGLE, returning them in brackets vs.

I tried to start a gremlin client, but it just stuck here without any other output. janusgraph version: 0.5.2(download full version) java version:1.8.0_151 OS: CentOS 7

Hi, I'm looking to drop a graph, but the JanusgraphFactory.drop(graph) doesn't work for me. I'm using JAVA to connect to the remote server and load/remove data. Using the below properties file for

Hmm, not sure if that is the issue coz both are considered as seperate objects.

Hi, I'd like to create a graph from within a Python script on a remote server that requires authentication. Is this possible? What I've done so far is create a graph on a remote server that requires

Sparshneel , We are planning to add another vertex property with name VID. We will create index on VID and do one time property update for historical data. This is too check if same property on both

Yeah. I tried the query which you shared. p99 was 100 ms. So we thought of creating edge index too. That screwed up everything. Let me go through the technical limitations link which you shared with

https://docs.janusgraph.org/basics/technical-limitations/ read this

Delete index on edge graph query to perform better should traverse from vertex using edge For eg see below query: g.V().has(‘User’,’id’,’user1’).out(“edgeId”).values() This should be

Just to reiterate, first I created a composite index on ID with vertex type. Then I created composite index on ID with edge type. The index on vertex type seems to have stopped working. The problem

I totally agree that elastic search would improve performance. But I am trying to figure out why the performance has degraded after creating edge index A query on edge ID after creating edge index is

Actually, IF u are using cassandra as backend, Repair your keyspace to 80%. Also These queries on cassandra on unique key which is part of your partition key, now if you have row by user id it

Sparshneel, Just to check if there is any problem with just getting vertex by ID, I am running the basic query as follows Suppose my ID is "user" and label "USER" (vertex index is defined on

Tanroop, These queries on graph ,it is better to use index backend. What is your query can u paste.

Sparshneel, Unique constraint works on vertex type only. Currently I am not using any indexing backend. The problem is that 50 ms should have been there even after creating edge instance

Tanroop, 50ms is still on the higher side, Also would like to know what index backend you are using, If EalsticSearch I would suggest create mixed index, you ID data type should be string and do query

I ran reindexing. Sharing for others' knowledge. It took me approximately 24 hrs are index 270 million edges