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.1: backupccl: add deprecation notice for BACKUP TO and RESTORE FROM without subdir #78250

Merged
merged 3 commits into from
Mar 22, 2022

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Mar 22, 2022

Backport 3/3 commits from #78165 on behalf of @adityamaru.

/cc @cockroachdb/release


backupccl: add deprecation notice for BACKUP TO

Informs: #78153

Release note (sql change): The BACKUP TO syntax
to take backups is deprecated, and will be removed in a future
release. Users are recommended to create a backup collection
using the BACKUP INTO syntax in our docs.

backupccl: add deprecation notice to RESTORE FROM without subdir
Informs: #78153

Release note (sql change): The RESTORE FROM syntax without an
explicit subdirectory pointing to a backup in a collection is deprecated,
and will be removed in a future release.
Users are recommended to use RESTORE FROM <backup> IN <collection> to
restore a particular backup in a collection.

backupccl: add datadriven tests for deprecation notice
Informs: #78153

Release note: None


Release justification: Low risk, high benefit changes to existing functionality. Deprecation notice for BACKUP syntax that has been undocumented since 21.1.

Informs: #78153

Release note (sql change): The `BACKUP TO` syntax
to take backups is deprecated, and will be removed in a future
release. Users are recommended to create a backup collection
using the `BACKUP INTO` syntax in our docs.
Informs: #78153

Release note (sql change): The `RESTORE FROM` syntax without an
explicit subdirectory pointing to a backup in a collection is deprecated,
and will be removed in a future release.
Users are recommended to use `RESTORE FROM <backup> IN <collection>` to
restore a particular backup in a collection.
@blathers-crl blathers-crl bot requested review from a team and dt and removed request for a team March 22, 2022 14:42
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.1-78165 branch from 3d8d15f to b5b1dd9 Compare March 22, 2022 14:42
@blathers-crl
Copy link
Author

blathers-crl bot commented Mar 22, 2022

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?

@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Mar 22, 2022
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@adityamaru
Copy link
Contributor

Bazel flake is unrelated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants