Try dropping the existing HBase table first (default HBase table name is janusgraph), and then create a new graph with graph = JanusGraphFactory.open('conf/janusgraph-hbase.properties') which does not use any index provider.

Most likely what happened was you used the janusgraph-hbase-es.properties first, which failed to connect to Elasticsearch, but the ES configuration properties were stored in the table itself.

-- Jason

On Monday, January 23, 2017 at 12:00:14 PM UTC-5, Rohit Jain wrote:

Since I did  want to use an index since performance is not of essence at the current time and I did not want to use either Elastic Search or SOLR, I used the following in Gremlin:

graph = JanusGraphFactory.open('conf/janusgraph-hbase.properties')

However, that gives me this error:

“Could not instantiate implementation: org.janusgraph.diskstorage.es.ElasticSearchIndex

So I figured I would just use SOLR already installed on the CDH deployment I was running on.  Then I get this error:

gremlin> graph = JanusGraphFactory.open('conf/janusgraph-hbase-solr.properties')

23:33:13 WARN  org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration  - Local setting index.search.backend=solr (Type: GLOBAL_OFFLINE) is overridden by globally managed value (elasticsearch).  Use the ManagementSystem interface instead of the local configuration to control this setting.

23:33:13 WARN  org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration  - Local setting index.search.solr.mode=http (Type: GLOBAL_OFFLINE) is overridden by globally managed value (cloud).  Use the ManagementSystem interface instead of the local configuration to control this setting.

Could not instantiate implementation: org.janusgraph.diskstorage.es.ElasticSearchIndex

It seemed that Titan had a ManagementSystem but perhaps JanusGraph doesn’t?  Anyway, how do I not use any index or use SOLR instead of Elastic Search?

Rohit