Add 3 new analytics_export rake tasks.#73935
Open
sureshc wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude <claude@users.noreply.github.com>
sureshc
marked this pull request as ready for review
July 17, 2026 17:31
This was referenced Jul 17, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a rake task
analytics_export:resync_zero_etl_tableto enable an Infrastructure Engineer to restart synchronization of a table from MySQL to Redshift that had previously failed and where the issue has been resolved (table schema has been updated to be compatible with Zero ETL, etc.).Also added a couple of additional helper rake tasks to analytics_export:
zero_etl_export_status- Get the current Zero ETL Integration status of each table.configure_zero_etl_target_database- Set ACCEPTINVCHARS and TRUNCATECOLUMNS to true on the target Zero ETL database to ensure that Zero ETL Integration modifies/truncates individual rows that have encoding issues or column content longer than the Redshift max (32KB?) do not disrupt the streaming of other rows. This is a configuration step we apply to the target Redshift database when initially provisioning a MySQL to Redshift Zero ETL Integration that must be configured manually because Zero ETL does not yet support configuring it via CloudFormation.Testing story
Deployment notes
Privacy and security