Closed patricknee closed 7 years ago
I can confirm this issue. You cannot install from this repo on new mac os. I get the following errors and the missing directories:
[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
[WARNING] Failure to transfer com.amazonaws:aws-java-sdk-dynamodb/maven-metadata.xml from s3://dynamodblocal/release was cached in the local repository, resolution will not be reattempted until the update interval of maven-s3-release-repo has elapsed or updates are forced. Original error: 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] Failure to transfer com.amazonaws:aws-java-sdk-dynamodb/maven-metadata.xml from s3://dynamodblocal/snapshot was cached in the local repository, resolution will not be reattempted until the update interval of maven-s3-snapshot-repo has elapsed or updates are forced. Original error: 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
[WARNING] Failure to transfer com.amazonaws:aws-java-sdk-dynamodb/maven-metadata.xml from s3://dynamodblocal/release was cached in the local repository, resolution will not be reattempted until the update interval of maven-s3-release-repo has elapsed or updates are forced. Original error: 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] Failure to transfer com.amazonaws:aws-java-sdk-dynamodb/maven-metadata.xml from s3://dynamodblocal/snapshot was cached in the local repository, resolution will not be reattempted until the update interval of maven-s3-snapshot-repo has elapsed or updates are forced. Original error: 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
[WARNING] Could not transfer metadata com.amazonaws:aws-java-sdk-dynamodb/maven-metadata.xml from/to maven-s3-release-repo (s3://dynamodb-local/release): Cannot access s3://dynamodb-local/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://dynamodb-local/snapshot): Cannot access s3://dynamodb-local/snapshot with type default using the available connector factories: BasicRepositoryConnectorFactory
@codelion - Are you aware of this repository change that recently went in? https://github.com/awslabs/dynamodb-titan-storage-backend/pull/57
@jfstephe I hadn't checked that. I did a workaround by downloading the file myself manually and putting it in the server folder after installation.
The repository links are now updated. I will double check the urls of the server zips, one moment.
It seems like the repackaged server zip links also work as is. Closing for now; please reopen if you need more help with this issue.
About one month ago I successfully installed dynamodb-titan-storage-backend on my development machine (Mac OSX) using these instructions: http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.TitanDB.DownloadingAndRunning.html.
As I try to move to a testing server, I am now unable to perform the install again. I have tried an additional installation on my dev machine, and the same problem occurs here as well.
Result: the dynamodb-titan-storage-backend/server/dynamodb-titan100-storage-backend-1.0.0-hadoop1 directory is missing most subdirectories.
During installation, mvn install appears to complete with success (step 2 of the instructions above), but Closer inspection of the output shows a number of resources that cannot be accessed:
Step 5 of the instructions (src/test/resources/install-gremlin-server.sh) has similar warnings about not being able to access some resources. After the "Build Success 13.607s" message, the process hesitates for a couple of minutes, then completes with the warning signs. The output is below as the second code block.
Did some resource the server installer is trying to download get moved in the past month?
mvn install output:
src/test/resources/install-gremlin-server.sh: