Rajdeep, Alternatively, you could evaluate moving away from running JanusGraph embedded. As you know, we don't have a release yet, but when 0.1.0 releases, it'll be on at least Apache TinkerPop

The Scala dependency is defined via Apache TinkerPop. JanusGraph is aligned currently with the TinkerPop 3.2.x branch, which is using Scala 2.10.5 (and Spark 1.6.1). Scala 2.11 (and Spark 2.0.2) is

The Scala dependency is defined via Apache TinkerPop. JanusGraph is aligned currently with the TinkerPop 3.2.x branch, which is using Scala 2.10.5 (and Spark 1.6.1). Scala 2.11 (and Spark 2.0.2) is

We are using Scala 2.11.8 in our project but Janusgraph build seems to use scala 2.10.(5/6?) libraries. We are wondering if there is near future release (perhaps through maven) with scala 2.11? If

Ted, We are using Scala 2.11.8 in our project but Janusgraph build uses scala 2.10.(6?) libraries. We are wondering if there is near future release (perhaps through maven) with scala 2.11? If not,

Thanks for the follow-up! Marc Op vrijdag 31 maart 2017 17:13:53 UTC+2 schreef Adam Holley:

As it turns out, the documentation is correct and I was using underscores instead of hyphens. The correct configuration is: storage.backend=cassandrathrift storage.cassandra.frame-size-mb=20

JanusGraph provides native support for the property graph data model exposed by Apache TinkerPop and uses Gremlin as its query language. It does not have native support for RDF or SPARQL. That being

Hi all,           I'm relatively new to graph databases, and there seems to be a significant difference among "graph/property stores" and "RDF stores". Not a big difference in theory, but

Good to know. Manual flush on the table should not be required. HBase keeps recent writes in memory. But they have been written to WAL logs as well. When you reboot your system without properly shuts

Hi It seems hbase automatically flushes to disk based on the flush interval and memstore size limit configuration. So Its not a problem. Everything working fine now. Thanks

Hi Jerry Thanks for helping me out. When I manually run 'flush' on the table on the hbase shell, The data persists after system reboot in my local machine. Is there any command to flush the table in

I am not sure what storage model you use for HBase on AWS. If you are using this: http://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hbase-s3.html There is a section 'Shutting Down and Restoring a

Yes I am able to run all operations successfully. I tried on on both AWS server and my local machine. AWS server stores hbase data in s3, and I configured the local machine to point to a directory in

You are able to run the graph ops all successfully? You are able to retrieve the Vertices or count them correctly before the system restart?I doubt it is related to Solr configuration. HBase is

Yes. I used Graph.tx().commit() on gremlin.sh and also graph.close() I tried using titan db 1.0 also. The data exists till I reboot the system. I also changed the hbase home directory to not point

Do you commit your transactions? Robert Dale

Hi all I am new to Janusgraph/ Titan, I installed janusgraph 0.1.0 in aws EMR, using db backend hbase and index backend solr. Everything works, But when I reboot the system, All the graph data is

Did you use the snapshot recently released? Verify that conf/gremlin-server/gremlin-server.yaml has a graph section like: Then verify that the graph property file exists and has a graph defined,

Congrats and well deserved! --Ted