search

amazon-archives / dynamodb-janusgraph-storage-backend

The Amazon DynamoDB Storage Backend for JanusGraph
Apache License 2.0
447 stars 99 forks source link

graphindex not created while migrating from titan to janus #271

Open yzainee-zz opened 6 years ago

yzainee-zz commented 6 years ago

We were using titan and wanted to migrate to janus. We wanted to use the same tables which were used in titan. For this we have the following 3 configurations config params storage.backend = com.amazon.janusgraph.diskstorage.dynamodb.DynamoDBStoreManager storage.dynamodb.use-titan-ids= true storage.dynamodb.stores.ids.store-name= titan_ids

But what we are observing is that instead of earlier (titan) edgestore graphindex system_properties systemlog titan_ids txlog

we see (janus) edgestore system_properties titan_ids

Why dont we see the graphindex created for janus? Is there some kind of configuration that we need to set for that?

yzainee-zz commented 6 years ago

Note: We have millions of records / data which we had created using Titan. now we want to migrate from titan to janus and want to use the same data instead of creating everything from scratch.

Currently, after migrating from titan to janus, when we do a gremlin=g.V().count() we get 0. Is there any configuration that we need to set? i have paster the 3 config variables that we have used for the migration above in the issue.

yzainee-zz commented 6 years ago

config params storage.backend = com.amazon.janusgraph.diskstorage.dynamodb.DynamoDBStoreManager storage.dynamodb.use-titan-ids= true ids.store-name= titan_ids graph.titan-version=1.1.0-SNAPSHOT

Have also tried these configuration.