I want to load GraphOfTheGodsFactory using cassandra & es. It is giving me this exception when i try to do gremlin> graph =

Sorry! I found it's my own fault. The property is a String type, and is a mixed index. while this went wrong, gremlin> g.E().has('contents','hdfs').values() Could not find a suitable index to

Hi everyone, The Opensource Graph Technologies meetup community in London has been nicely growing the past few months! We've been organising it (GRAKN.AI) and we've had cool talks from people Apache

Here's a recent one: https://twitter.com/CELUM/status/857934890934964225

FYI, the Titan mailing list is here. What does your index definition look like?Are you using JanusGraph or is this a problem you can recreate on JanusGraph?

This issue has been reported https://github.com/JanusGraph/janusgraph/issues/228 Please follow the discussion there.

cqlsh communicates using CQL interface, but JanusGraph uses Thrift. I'd suggest double checking that the RPC settings (rpc_address, rpc_port) in cassandra.yaml match what you have in

Hi Collin, I'm not aware of what "level of testing and rigor that went into the 1.0 release of Titan". The version is just a number, and I wouldn't get too hung up on it if you've tested it in your

We have a Titan instance running on Cassandra. When migrating from Titan to Janus, a new table "titan.janusgraph_ids" is generated. Does this table respect the existing "titan.titan_ids" in terms of

When I try to open a graph, I am constantly getting the TimeOutExceptions. My Cassandra Cluster is fine and I was able to use cqlsh with no issues. Are there any Thrift settings that need to be

I tried this with Cassandra + Embedded Elastic configuration. It works there as well, however one has to add configuration to use "titan" keyspace name. storage.cassandra.keyspace=titan In this case

This solutions worked for me. Commit had to be done after the force closure. JanusGraphManagement jMgmt = jGraph.openManagement(); Set<String> open = jMgmt.getOpenInstances(); for (String string :

Hello: I'm using titan with hbase and elasticsearch, all was ok at first, but yesterday when I was searching as usual, it worn Could not find a suitable index to answer graph query and graph

Hey all, We're pretty excited about Janus over here and are considering switching over in the near future (I'm actually trying out OLAP with hadoop 2 as we speak). I'm normally quite hesitant to put

For those coming from google, here are the current maven coordinates. https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.janusgraph%22

The first error message said that there were multiple open instances. In order to close them, again you must work through the management system (do not close the graph you are already connect to). Try

Hi Jason, I tried to do that. JanusGraphManagement janusGraphManagement=janusGraph.openManagement(); janusGraphManagement.set("index.search.index-name",

Hi Jason, Thanks for quick response. Will try this and it should work. Thanks Akshaya

Doh, you're right Daniel. Meta-properties do not support cardinality, only vertex properties do.

Hi Akshya, Thanks for the info, and unfortunately it looks like some scenarios were missed. Note that if you created the Titan graph originally with the `index.search.index-name` property set, it