Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Varun VelamuriVarun VelamuriReporter
Varun VelamuriVarun VelamuriIs this a Regression?
UnknownGerrit Reviews
MB-61435 Track markFirstSnap per keyspace repo:indexing branch:7.2.2
MB-61435 Disable first snap optimization repo:indexing branch:7.2.2
Triage
UntriagedDue date
Apr 12, 2024Story Points
0Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Varun Velamuri
Varun VelamuriReporter
Varun Velamuri
Varun VelamuriIs this a Regression?
Unknown
Gerrit Reviews
MB-61435 Track markFirstSnap per keyspace repo:indexing branch:7.2.2
MB-61435 Disable first snap optimization repo:indexing branch:7.2.2
Triage
Untriaged
Due date
Apr 12, 2024
Story Points
0
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created April 5, 2024 at 7:38 PM
Updated October 21, 2024 at 8:02 AM
Resolved April 12, 2024 at 5:39 AM
Currently, mutation stream reader tracks the enablement of first snapshot optimisation per stream. This can lead to an issue if first snap optimisation can be enabled for one keyspace and should not be enabled for other keyspace (See linked customer ticket).
If the first keyspace that starts the stream enables the first snapshot optimisation, it will be applicable for all keyspaces which follow. This is incorrect and can lead to duplicate rows in the index.