fix: fix activityTypes Tinybird data source sorting key#3509
Conversation
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
1 similar comment
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
6a59a90 to
ac0ac69
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
ac0ac69 to
1afca5a
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
1afca5a to
894178a
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
894178a to
e5e8419
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
gaspergrom
left a comment
There was a problem hiding this comment.
Please fix copilot comment
e5e8419 to
5afb9f4
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
In the activityTypes Tinybird data source, we were missing the
activityTypefield in theENGINE_SORTING_KEY, which caused problems with deduplication.This fixes it, and also removes isCodeContribution and isCollaboration from the sorting key to also prevent issues with duplicates, in case we change a setting in one of the activity types.
Note: there's no Jira ticket for this one, as this was an emergency fix yesterday.