feat(capture): Add historical_migration flag to batch capture #20350
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
tiina303
approved these changes
Feb 15, 2024
No, new capture doesn't support |
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.
Problem
Rather than (or in addition to) having to manually add/remove tokens to/from
TOKENS_HISTORICAL_DATA, we could automatically opt in migration tools.Changes
Add
historical_migrationflag to thebatchendpoint, to be used by migration scripts in the future.(Historical migrations should always use the
batchendpoint.)👉 Stay up-to-date with PostHog coding conventions for a smoother review.
How did you test this code?
New and existing tests.