We already have a strongly-worded note in our public docs saying that the user should take care to make sure that min_checkpoint_frequency <= resolved since we won't emit resolved timestamps more frequently than min_checkpoint_frequency. We should either enforce this condition in code or at least issue a warning if the user violates this.
One argument against making this an error would be that it could be a breaking change for existing changefeeds.
blathers-crl[bot]
commented
3 months ago
We already have a strongly-worded note in our public docs saying that the user should take care to make sure that
min_checkpoint_frequency<=resolvedsince we won't emit resolved timestamps more frequently thanmin_checkpoint_frequency. We should either enforce this condition in code or at least issue a warning if the user violates this.One argument against making this an error would be that it could be a breaking change for existing changefeeds.
Jira issue: CRDB-39646