Skip to content
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

release-22.2: ttl: allow inbound foreign keys on TTL tables #105342

Merged
merged 2 commits into from
Jun 22, 2023
Merged

release-22.2: ttl: allow inbound foreign keys on TTL tables #105342

merged 2 commits into from
Jun 22, 2023

Conversation

ecwall
Copy link
Contributor

@ecwall ecwall commented Jun 22, 2023

Backport 2/2 commits from #101376.

/cc @cockroachdb/release


Fixes #76407

This change allows TTL tables to have inbound foreign keys. If the inbound foreign key has the ON DELETE CASCADE option, the TTL job will work as usual. If it has the ON DELETE RESTRICT option, the TTL job will fail if a row references the TTL table (see #101372).

Release note (sql change): Allow inbound foreign keys on TTL tables.

Release justification: Unblock customers needing inbound FKs on TTL table.

@ecwall ecwall requested a review from rafiss June 22, 2023 13:45
@ecwall ecwall requested a review from a team as a code owner June 22, 2023 13:45
@blathers-crl
Copy link

blathers-crl bot commented Jun 22, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

…ivenFKCascadesClusterLimit 22.2 compatibility

Informs #101265

The original backport for #101265 is incomplete in 22.2 where the session data
for jobs is initialized differently from 23.1+. This PR adds to the original
backport by reading `optDrivenFKCascadesClusterLimit` inside
`Server.newSessionData`.

Release note: None
Fixes #76407

This change allows TTL tables to have inbound foreign keys. If the inbound
foreign key has the ON DELETE CASCADE option, the TTL job will work as usual.
If it has the ON DELETE RESTRICT option, the TTL job will fail if a row
references the TTL table (see #101372).

Release note (sql change): Allow inbound foreign keys on TTL tables.
Copy link
Collaborator

@rafiss rafiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 2 of 2 files at r1, 4 of 4 files at r2, all commit messages.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @ecwall)

@ecwall ecwall merged commit dd43b32 into cockroachdb:release-22.2 Jun 22, 2023
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants