Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

No, it is not a bug. It is a warning letting you know that there is a query that is doing a global scan of all vertices. In this case, the specific call is `g.V().count().next()` which is trying to determine whether there is any data in the graph. Something like `g.V().hasNext()` would be a less expensive check, although it would still issue the warning.

This small example can get away a call like this because there are only 12 vertices in the loaded graph, but it would be an expensive operation if there were 1 billion vertices.

Thanks for the feedback.
-- Jason

On Thursday, May 18, 2017 at 12:36:05 PM UTC-4, Ярослав Станко wrote:

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

Thanks for the answer. I do not understand a little.

In my case I'm looking for a Vertex: traversalSource.V().has("ip4addressString", addressString);

And I get a warning: Query requires iterating over all vertices [(ip4addressString = 192.168.155.212)]. For better performance, use indexes

ip4addressString is a unique CompositeIndex. Why is my index not used?

четверг, 18 мая 2017 г., 21:11:03 UTC+3 пользователь Jason Plurad написал:

No, it is not a bug. It is a warning letting you know that there is a query that is doing a global scan of all vertices. In this case, the specific call is `g.V().count().next()` which is trying to determine whether there is any data in the graph. Something like `g.V().hasNext()` would be a less expensive check, although it would still issue the warning.

This small example can get away a call like this because there are only 12 vertices in the loaded graph, but it would be an expensive operation if there were 1 billion vertices.

Thanks for the feedback.
-- Jason

On Thursday, May 18, 2017 at 12:36:05 PM UTC-4, Ярослав Станко wrote:

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

And one more thing. My index exists and works because 

Adding this property for key [ip4addressString] and value [192.168.155.212] violates a uniqueness constraint [compositeIp4addressString]

пятница, 19 мая 2017 г., 12:53:16 UTC+3 пользователь CGen написал:

Thanks for the answer. I do not understand a little.

In my case I'm looking for a Vertex: traversalSource.V().has("ip4addressString", addressString);

And I get a warning: Query requires iterating over all vertices [(ip4addressString = 192.168.155.212)]. For better performance, use indexes

ip4addressString is a unique CompositeIndex. Why is my index not used?

четверг, 18 мая 2017 г., 21:11:03 UTC+3 пользователь Jason Plurad написал:

No, it is not a bug. It is a warning letting you know that there is a query that is doing a global scan of all vertices. In this case, the specific call is `g.V().count().next()` which is trying to determine whether there is any data in the graph. Something like `g.V().hasNext()` would be a less expensive check, although it would still issue the warning.

This small example can get away a call like this because there are only 12 vertices in the loaded graph, but it would be an expensive operation if there were 1 billion vertices.

Thanks for the feedback.
-- Jason

On Thursday, May 18, 2017 at 12:36:05 PM UTC-4, Ярослав Станко wrote:

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

Can you share your property and index definition?

On Friday, May 19, 2017 at 6:37:09 AM UTC-4, CGen wrote:

And one more thing. My index exists and works because 

Adding this property for key [ip4addressString] and value [192.168.155.212] violates a uniqueness constraint [compositeIp4addressString]

пятница, 19 мая 2017 г., 12:53:16 UTC+3 пользователь CGen написал:

Thanks for the answer. I do not understand a little.

In my case I'm looking for a Vertex: traversalSource.V().has("ip4addressString", addressString);

And I get a warning: Query requires iterating over all vertices [(ip4addressString = 192.168.155.212)]. For better performance, use indexes

ip4addressString is a unique CompositeIndex. Why is my index not used?

четверг, 18 мая 2017 г., 21:11:03 UTC+3 пользователь Jason Plurad написал:

No, it is not a bug. It is a warning letting you know that there is a query that is doing a global scan of all vertices. In this case, the specific call is `g.V().count().next()` which is trying to determine whether there is any data in the graph. Something like `g.V().hasNext()` would be a less expensive check, although it would still issue the warning.

This small example can get away a call like this because there are only 12 vertices in the loaded graph, but it would be an expensive operation if there were 1 billion vertices.

Thanks for the feedback.
-- Jason

On Thursday, May 18, 2017 at 12:36:05 PM UTC-4, Ярослав Станко wrote:

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

PropertyKey ip4addressStringPropertyKey = mgmt.makePropertyKey("ip4addressString").dataType(String.class).make();

VertexLabel ip4addressVertexLabel = mgmt.makeVertexLabel("ip4address").make();

JanusGraphIndex ip4addressStringIndex = mgmt.buildIndex("compositeIp4addressString", Vertex.class).addKey(ip4addressStringPropertyKey).indexOnly(ip4addressVertexLabel).unique().buildCompositeIndex();

        mgmt.setConsistency(ip4addressStringIndex, ConsistencyModifier.LOCK);

пятница, 19 мая 2017 г., 17:36:46 UTC+3 пользователь Jason Plurad написал:

Can you share your property and index definition?

On Friday, May 19, 2017 at 6:37:09 AM UTC-4, CGen wrote:

And one more thing. My index exists and works because 

Adding this property for key [ip4addressString] and value [192.168.155.212] violates a uniqueness constraint [compositeIp4addressString]

пятница, 19 мая 2017 г., 12:53:16 UTC+3 пользователь CGen написал:

Thanks for the answer. I do not understand a little.

In my case I'm looking for a Vertex: traversalSource.V().has("ip4addressString", addressString);

And I get a warning: Query requires iterating over all vertices [(ip4addressString = 192.168.155.212)]. For better performance, use indexes

ip4addressString is a unique CompositeIndex. Why is my index not used?

четверг, 18 мая 2017 г., 21:11:03 UTC+3 пользователь Jason Plurad написал:

No, it is not a bug. It is a warning letting you know that there is a query that is doing a global scan of all vertices. In this case, the specific call is `g.V().count().next()` which is trying to determine whether there is any data in the graph. Something like `g.V().hasNext()` would be a less expensive check, although it would still issue the warning.

This small example can get away a call like this because there are only 12 vertices in the loaded graph, but it would be an expensive operation if there were 1 billion vertices.

Thanks for the feedback.
-- Jason

On Thursday, May 18, 2017 at 12:36:05 PM UTC-4, Ярослав Станко wrote:

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

Ah, you used indexOnly() to restrict the index by vertex label, so in order to utilize the index, your query must include the vertex label. Either of these would work since ultimately they are optimized to the same traversal:

g.V().hasLabel("ip4address").has("ip4addressString", "192.168.155.212")
g.V().has("ip4address", "ip4addressString", "192.168.155.212")

On Friday, May 19, 2017 at 1:57:25 PM UTC-4, CGen wrote:

PropertyKey ip4addressStringPropertyKey = mgmt.makePropertyKey("ip4addressString").dataType(String.class).make();

VertexLabel ip4addressVertexLabel = mgmt.makeVertexLabel("ip4address").make();

JanusGraphIndex ip4addressStringIndex = mgmt.buildIndex("compositeIp4addressString", Vertex.class).addKey(ip4addressStringPropertyKey).indexOnly(ip4addressVertexLabel).unique().buildCompositeIndex();

        mgmt.setConsistency(ip4addressStringIndex, ConsistencyModifier.LOCK);

пятница, 19 мая 2017 г., 17:36:46 UTC+3 пользователь Jason Plurad написал:

Can you share your property and index definition?

On Friday, May 19, 2017 at 6:37:09 AM UTC-4, CGen wrote:

And one more thing. My index exists and works because 

Adding this property for key [ip4addressString] and value [192.168.155.212] violates a uniqueness constraint [compositeIp4addressString]

пятница, 19 мая 2017 г., 12:53:16 UTC+3 пользователь CGen написал:

Thanks for the answer. I do not understand a little.

In my case I'm looking for a Vertex: traversalSource.V().has("ip4addressString", addressString);

And I get a warning: Query requires iterating over all vertices [(ip4addressString = 192.168.155.212)]. For better performance, use indexes

ip4addressString is a unique CompositeIndex. Why is my index not used?

четверг, 18 мая 2017 г., 21:11:03 UTC+3 пользователь Jason Plurad написал:

No, it is not a bug. It is a warning letting you know that there is a query that is doing a global scan of all vertices. In this case, the specific call is `g.V().count().next()` which is trying to determine whether there is any data in the graph. Something like `g.V().hasNext()` would be a less expensive check, although it would still issue the warning.

This small example can get away a call like this because there are only 12 vertices in the loaded graph, but it would be an expensive operation if there were 1 billion vertices.

Thanks for the feedback.
-- Jason

On Thursday, May 18, 2017 at 12:36:05 PM UTC-4, Ярослав Станко wrote:

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

Ah, you used indexOnly() to restrict the index by vertex label, so in order to utilize the index, your query must include the vertex label. Either of these would work since ultimately they are optimized to the same traversal:

g.V().hasLabel("ip4address").has("ip4addressString", "192.168.155.212")
g.V().has("ip4address", "ip4addressString", "192.168.155.212")

On Friday, May 19, 2017 at 1:57:25 PM UTC-4, CGen wrote:

PropertyKey ip4addressStringPropertyKey = mgmt.makePropertyKey("ip4addressString").dataType(String.class).make();

VertexLabel ip4addressVertexLabel = mgmt.makeVertexLabel("ip4address").make();

JanusGraphIndex ip4addressStringIndex = mgmt.buildIndex("compositeIp4addressString", Vertex.class).addKey(ip4addressStringPropertyKey).indexOnly(ip4addressVertexLabel).unique().buildCompositeIndex();

        mgmt.setConsistency(ip4addressStringIndex, ConsistencyModifier.LOCK);

пятница, 19 мая 2017 г., 17:36:46 UTC+3 пользователь Jason Plurad написал:

Can you share your property and index definition?

On Friday, May 19, 2017 at 6:37:09 AM UTC-4, CGen wrote:

And one more thing. My index exists and works because 

Adding this property for key [ip4addressString] and value [192.168.155.212] violates a uniqueness constraint [compositeIp4addressString]

пятница, 19 мая 2017 г., 12:53:16 UTC+3 пользователь CGen написал:

Thanks for the answer. I do not understand a little.

In my case I'm looking for a Vertex: traversalSource.V().has("ip4addressString", addressString);

And I get a warning: Query requires iterating over all vertices [(ip4addressString = 192.168.155.212)]. For better performance, use indexes

ip4addressString is a unique CompositeIndex. Why is my index not used?

четверг, 18 мая 2017 г., 21:11:03 UTC+3 пользователь Jason Plurad написал:

No, it is not a bug. It is a warning letting you know that there is a query that is doing a global scan of all vertices. In this case, the specific call is `g.V().count().next()` which is trying to determine whether there is any data in the graph. Something like `g.V().hasNext()` would be a less expensive check, although it would still issue the warning.

This small example can get away a call like this because there are only 12 vertices in the loaded graph, but it would be an expensive operation if there were 1 billion vertices.

Thanks for the feedback.
-- Jason

On Thursday, May 18, 2017 at 12:36:05 PM UTC-4, Ярослав Станко wrote:

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?

Hello!

I get the example : https://github.com/pluradj/janusgraph-java-example

Why is there a warning in the log?

"WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes"

In my project the same thing.

Is this a bug? How to fix it?