-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rows are not restored using AzureStorageDriver #449
Comments
rozele
added a commit
to rozele/dcos-cassandra-service
that referenced
this issue
Jun 7, 2017
AzureStorageDriver downloads to a different location from the S3StorageDriver. This makes the download behavior more consistent. Fixes mesosphere-backup#449
rozele
added a commit
to rozele/dcos-cassandra-service
that referenced
this issue
Jun 7, 2017
AzureStorageDriver downloads to a different location from the S3StorageDriver. This makes the download behavior more consistent. Fixes mesosphere-backup#449
rozele
added a commit
to rozele/dcos-cassandra-service
that referenced
this issue
Jul 11, 2017
AzureStorageDriver downloads to a different location from the S3StorageDriver. This makes the download behavior more consistent. Fixes mesosphere-backup#449
This repo is deprecated and will be archived in one week. Please see the latest version of Cassandra or DSE for DC/OS: https://docs.mesosphere.com/service-docs/cassandra/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue:
When you try to restore Cassandra from the DC/OS CLI from Azure blob, the rows are not restored correctly.
Version: 1.0.25-3.0.10
Environment: Azure ACS
Repro steps:
SELECT * FROM demo.map
and find no data.The text was updated successfully, but these errors were encountered: