I am trying to configure JanusGraph with Apache Cassandra 3.1 and Solr 6.1.0 .

I cannot connect to the Storage backend from the code , though all of my configuration are correct .. 

Hi Jimmy,

I started building a list of companies using JanusGraph in production; you can see the current list here: https://github.com/JanusGraph/janusgraph#users (and the logos at the bottom of http://janusgraph.org) and more additions are on the way.

They appear to be happy with JanusGraph, but I'll let them chime in if they want to provide any additional details.

BTW, if anyone else is a production user of JanusGraph, please get in touch with me and let's get you added on the list as well!

Misha

On Fri, Apr 7, 2017 at 4:03 AM, Jimmy <xuliuc...@...> wrote:

Lovely and promising project! I want to know if anyone is using JanusGraph in production at present？Thanks!

--
You received this message because you are subscribed to the Google Groups "JanusGraph users list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgra...@....
For more options, visit https://groups.google.com/d/optout.

Hello!

I need to load CSV files into JanusGraph with a size of 1.7 gigabytes.

How can I increase the load speed? 

I added to the config:

storage.batch-loading=true

schema.default=none

I have almost no access to the disk, but the CPU is always busy.

In the profiler, the hot spot is: org.janusgraph.graphdb.internal.AbstractElement equals (8%).

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?

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?

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?

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?

Going by the getting started documentation, how do I load janusgraph methods in the gremlin terminal? 
When I try to run the JanusGraphFactory's open method it obviously says NameError: name 'JanusGraphFactory' is not defined. 
What am I missing?

On Wednesday, February 22, 2017 at 10:43:24 PM UTC+5:30, Manoj Waikar wrote:

We were able to build it on Mac / Linux using the instructions mentioned, however the build fails on Windows (because of a few Linux commands used therein).

On Wednesday, February 22, 2017 at 3:52:35 AM UTC+5:30, lo...@... wrote:

Hi Misha,

What exactly is involved in building locally?  I can't seem to find any documentation.

Thanks

On Wednesday, February 8, 2017 at 10:07:39 PM UTC+1, Misha Brukman wrote:

Yes, that's correct. For now, please clone and build locally.

https://github.com/JanusGraph/janusgraph/issues/40 is tracking the work of building a release snapshot to simplify the getting started process.

On Wed, Feb 8, 2017 at 2:15 PM, e2t2 <gha...@...> wrote:

Hi All,

I am new to graph world and have done basic Titan tutorials, etc. Happy to hear that JanusGraph will continue where titan guys left.

Just a quick question, in the Getting started guide for JanusGraph it says to download zip file and unzip it to get started. However, in download link there is no release available.

Do I need to clone the repository and build it myself or I am missing something here?

Thanks

--
You received this message because you are subscribed to the Google Groups "JanusGraph users list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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?

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?

We were able to build it on Mac / Linux using the instructions mentioned, however the build fails on Windows (because of a few Linux commands used therein).

On Wednesday, February 22, 2017 at 3:52:35 AM UTC+5:30, lo...@... wrote:

Hi Misha,

What exactly is involved in building locally?  I can't seem to find any documentation.

Thanks

On Wednesday, February 8, 2017 at 10:07:39 PM UTC+1, Misha Brukman wrote:

Yes, that's correct. For now, please clone and build locally.

https://github.com/JanusGraph/janusgraph/issues/40 is tracking the work of building a release snapshot to simplify the getting started process.

On Wed, Feb 8, 2017 at 2:15 PM, e2t2 <gha...@...> wrote:

Hi All,

I am new to graph world and have done basic Titan tutorials, etc. Happy to hear that JanusGraph will continue where titan guys left.

Just a quick question, in the Getting started guide for JanusGraph it says to download zip file and unzip it to get started. However, in download link there is no release available.

Do I need to clone the repository and build it myself or I am missing something here?

Thanks

--
You received this message because you are subscribed to the Google Groups "JanusGraph users list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.