updated the readme doc #76
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
taherkl
requested changes
Jan 21, 2025
v2/spanner-to-sourcedb/README.md
Outdated
| - Check that the Cassandra credentials are correctly specified in the [source shards file](#Sample-source-shards-File-for-Cassandra). | ||
| - Check that the Cassandra server is up. | ||
| - The Cassandra user configured in the [source shards file](#Sample-source-shards-File-for-Cassandra) should be granted the necessary permissions to perform insert , update and delete operations, as a part of [Cassandra Role Management](https://cassandra.apache.org/doc/stable/cassandra/cql/security.html#create-role-statement). | ||
| 2. Ensure that Dataflow permissions are present.[Basic permissions](https://cloud.google.com/dataflow/docs/guides/templates/using-flex-templates#before_you_begin:~:text=Grant%20roles%20to%20your%20Compute%20Engine%20default%20service%20account.%20Run%20the%20following%20command%20once%20for%20each%20of%20the%20following%20IAM%20roles%3A%20roles/dataflow.admin%2C%20roles/dataflow.worker%2C%20roles/bigquery.dataEditor%2C%20roles/pubsub.editor%2C%20roles/storage.objectAdmin%2C%20and%20roles/artifactregistry.reader) and [Flex template permissions](https://cloud.google.com/dataflow/docs/guides/templates/configuring-flex-templates#permissions). |
There was a problem hiding this comment.
Most of the guidelines are duplicate. No need for rewriting. Within the Before you begin section, we can add details for cassandra wherever required.
v2/spanner-to-sourcedb/README.md
Outdated
| 7. Ensure that the target Spanner instance is ready. | ||
| 8. [Source shards file](#Sample-source-shards-File-for-Cassandra) already uploaded to GCS. | ||
| 9. Resources needed for reverse replication incur cost. Make sure to read [cost](#cost). | ||
| 10. Reverse replication uses shard identifier column per table to route the Spanner records to a given source shard.The column identified as the sharding column needs to be selected via Spanner Migration Tool when performing migration.In the event that the shard identifier column is not an existing column,the application code needs to be changed to populate this shard identifier column when writing to Spanner. Or use a custom shard identifier plugin to supply the shard identifier. |
There was a problem hiding this comment.
There is no shard in cassandra. lets mention it as source db config.
v2/spanner-to-sourcedb/README.md
Outdated
| @@ -153,6 +218,29 @@ The file should be a list of JSONs as: | |||
| ] | |||
| ``` | |||
|
|
|||
|
|
|||
| ### Sample source shards file for Cassandra | |||
There was a problem hiding this comment.
There is no shard in cassandra. lets mention it as source db config.
| @@ -40,14 +40,12 @@ on [Metadata Annotations](https://github.com/GoogleCloudPlatform/DataflowTemplat | |||
| * **dlqMaxRetryCount**: The max number of times temporary errors can be retried through DLQ. Defaults to 500. | |||
| * **runMode**: This is the run mode type, whether regular or with retryDLQ.Default is regular. retryDLQ is used to retry the severe DLQ records only. | |||
| * **dlqRetryMinutes**: The number of minutes between dead letter queue retries. Defaults to 10. | |||
| * **sourceType**: The type of source database to reverse replicate to. Defaults to: mysql. | |||
| * **sourceType**: The type of source database to reverse replicate to. Defaults to: mysql, but it can also be configured to use Cassandra. | |||
There was a problem hiding this comment.
cassandra will be in small case.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.