-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: Do not merge heartbeat ranges #26653
Conversation
NON_RETRYABLE_ERROR_TYPES = [ | ||
# Raised on errors that are related to database operation. | ||
# For example: unexpected disconnect, database or other object not found. | ||
"OperationalError", | ||
# The schema name provided is invalid (usually because it doesn't exist). | ||
"InvalidSchemaName", | ||
# Missing permissions to, e.g., insert into table. | ||
"InsufficientPrivilege", | ||
# A column, usually properties, exceeds the limit for a VARCHAR field, | ||
# usually the max of 65535 bytes | ||
"StringDataRightTruncation", | ||
# Raised by our PostgreSQL client when failing to connect after several attempts. | ||
"PostgreSQLConnectionError", | ||
# Column missing in Redshift, likely the schema was altered. | ||
"UndefinedColumn", | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Err, didn't intend to get this out yet, working on SPMC for redshift. But anyways, won't hurt to merge now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not quite sure I understand all the complexities here but agree it makes sense to keep it simple for now
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the |
This PR was closed due to lack of activity. Feel free to reopen if it's still relevant. |
Problem
Merging heartbeat ranges in batch exports has currently two problems:
Until we update the queue to keep track of a record batch index that we can use to merge ranges together, let's just not merge.
Changes
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Does this work well for both Cloud and self-hosted?
How did you test this code?