Closed atsuya046 closed 8 years ago
I am getting the same error, following the instructions . t There are the following warnings [WARNING] Could not transfer metadata com.amazonaws:aws-java-sdk-dynamodb/maven-metadata.xml from/to maven-s3-release-repo (s3://dynamodblocal/release): Cannot access s3://dynamodblocal/release with type default using the available connector factories: BasicRepositoryConnectorFactory [WARNING] Could not transfer metadata com.amazonaws:aws-java-sdk-dynamodb/maven-metadata.xml from/to maven-s3-snapshot-repo (s3://dynamodblocal/snapshot): Cannot access s3://dynamodblocal/snapshot with type default using the available connector factories: BasicRepositoryConnectorFactory
Something about s3:// so not sure what you are looking for here. Thanks
This is because the ObjectMapper.enable method used there requires Jackson 2.5+. I fixed this by editing the pom file for this.
@sayrer Set jackson version 2.5.4, I fixed, too!! Thanks a lot :smiley_cat:
@atsuya046 I'm still seeing this issue after I set jackson version to 2.5.4, is there anything I should fix too?
Same as reterVision. Having this issue with 2.5.4, 2.6.3. Never gets past this exception. Not a pathname issue per other thread, happening on osx with path /test.
I'm getting the same error and stack trace as @atsuya046. I changed the pom.xml file, restarted everything, re-ran mvn install as well. Still getting the same error. OSX 10.9.5
I was able to fix the issue by applying the change from https://github.com/awslabs/dynamodb-titan-storage-backend/issues/18, then:
jackson
from the titan-core
dependency (pom.xml
, line 86):<dependency>
<groupId>com.thinkaurelius.titan</groupId>
<artifactId>titan-core</artifactId>
<version>${titan.version}</version>
<exclusions>
<exclusion>
<groupId>com.fasterxml.jackson.jaxrs</groupId>
<artifactId>jackson-jaxrs-json-provider</artifactId>
</exclusion>
</exclusions>
</dependency>
mvn clean
mvn install
Dan Hodge, I was not able to verify your fix even when I follow your instructions. I have considered some workarounds and will update this thread when they are ready.
I have fixed the issue concerning jackson version and verified the fix with locally built server versions. See this commit: https://github.com/awslabs/dynamodb-titan-storage-backend/commit/87ed814daa9ca277bd3ef32f71232d03aaf173ca I will need to update the server zips for this fix, and I will close this issue when I do that. Meanwhile, you can change the local copies of your cloud formation scripts to point to a version of the server zip that you build and host locally.
I published new maven artifacts that include the fixed pom.
I deployed new artifact and confirmed that the new ZIP is available on S3. You can use the cloud formation template at the tip of 0.5.4 branch while the links in AWS docs get updated. Closing
I am trying to following here. On step 5, when I run
g = TitanFactory.open(conf)
on gremlin, it is failingCould not instantiate implementation: com.amazon.titan.diskstorage.dynamodb.DynamoDBStoreManager
. This is after succcessfulmvn install
and successeful running dynamodb-local withmvn test -Pstart-dynamodb-local
command.Here is the stack trace.
I hope this helps. Thank you.