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

[DocDB] Add migration for namespace name field added in version 2.3.0 #17713

Closed
1 task done
karan-yb opened this issue Jun 7, 2023 · 0 comments
Closed
1 task done

Comments

@karan-yb
Copy link
Contributor

karan-yb commented Jun 7, 2023

Jira Link: DB-6815

Description

See details in #17712

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@karan-yb karan-yb added area/docdb YugabyteDB core features status/awaiting-triage Issue awaiting triage labels Jun 7, 2023
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Jun 7, 2023
@yugabyte-ci yugabyte-ci removed the status/awaiting-triage Issue awaiting triage label Jun 13, 2023
@yugabyte-ci yugabyte-ci added priority/high High Priority and removed priority/medium Medium priority issue labels Jul 17, 2023
hulien22 added a commit that referenced this issue Aug 9, 2023
Summary:
The namespace_name field was introduced in 2.3 but we didn't do any migration for it. This has led to issues on newer versions where newer code expects that this field is present, causing issues with ycql system.partitions, snapshots, metrics.

Using the master migration framework to migrate this field. As part of this, I have moved the namespace loader to be before the table loader (since that way we have the namespace info when loading tables).

Note: We still need to migrate the TableInfo stored in Raft Superblocks as well, but that will be done in a later diff, after we finalize the design there.
Jira: DB-6815

Test Plan:
```
ybd --cxx-test sys_catalog-test --gtest_filter SysCatalogTest.TestNamespaceNameMigration
ybd --cxx-test yb-admin-snapshot-test --gtest_filter AdminCliTest.TestListSnapshotWithNamespaceNameMigration
```

Reviewers: hsunder, zdrudi, asrivastava, skedia

Reviewed By: zdrudi, skedia

Subscribers: yql, yguan, ybase, bogdan

Differential Revision: https://phorge.dev.yugabyte.com/D27040
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature and removed kind/bug This issue is a bug labels Sep 21, 2023
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug and removed kind/enhancement This is an enhancement of an existing feature labels Oct 10, 2023
hulien22 added a commit that referenced this issue Oct 21, 2023
…o namespace_name

Summary:
Original commit: 231d34a / D29340
The namespace_name field was introduced in 2.3 but we didn't do any migration for it. This has led to issues on newer versions where newer code expects that this field is present, causing issues with ycql system.partitions, snapshots, metrics.

Using the master migration framework to migrate this field. As part of this, I have moved the namespace loader to be before the table loader (since that way we have the namespace info when loading tables).

Note: We still need to migrate the TableInfo stored in Raft Superblocks as well, but that will be done in a later diff, after we finalize the design there.
Jira: DB-6815

Test Plan:
```
ybd --cxx-test sys_catalog-test --gtest_filter SysCatalogTest.TestNamespaceNameMigration
ybd --cxx-test yb-admin-test_ent --gtest_filter AdminCliTest.TestListSnapshotWithNamespaceNameMigration
```

Reviewers: hsunder, zdrudi, asrivastava, skedia

Reviewed By: asrivastava

Subscribers: bogdan, ybase, yguan, yql

Tags: #jenkins-ready

Differential Revision: https://phorge.dev.yugabyte.com/D29479
hulien22 added a commit that referenced this issue Oct 24, 2023
…o namespace_name

Summary:
Original commit: 8afc03a / D27040
The namespace_name field was introduced in 2.3 but we didn't do any migration for it. This has led to issues on newer versions where newer code expects that this field is present, causing issues with ycql system.partitions, snapshots, metrics.

Using the master migration framework to migrate this field. As part of this, I have moved the namespace loader to be before the table loader (since that way we have the namespace info when loading tables).

Note: We still need to migrate the TableInfo stored in Raft Superblocks as well, but that will be done in a later diff, after we finalize the design there.
Jira: DB-6815

Test Plan:
```
ybd --cxx-test sys_catalog-test --gtest_filter SysCatalogTest.TestNamespaceNameMigration
ybd --cxx-test yb-admin-snapshot-test --gtest_filter AdminCliTest.TestListSnapshotWithNamespaceNameMigration
```

Reviewers: hsunder, zdrudi, asrivastava, skedia

Reviewed By: zdrudi

Subscribers: bogdan, ybase, yguan, yql

Differential Revision: https://phorge.dev.yugabyte.com/D29173
hulien22 added a commit that referenced this issue Oct 24, 2023
…o namespace_name

Summary:
Original commit: 8afc03a / D27040
The namespace_name field was introduced in 2.3 but we didn't do any migration for it. This has led to issues on newer versions where newer code expects that this field is present, causing issues with ycql system.partitions, snapshots, metrics.

Using the master migration framework to migrate this field. As part of this, I have moved the namespace loader to be before the table loader (since that way we have the namespace info when loading tables).

Note: We still need to migrate the TableInfo stored in Raft Superblocks as well, but that will be done in a later diff, after we finalize the design there.
Jira: DB-6815

Test Plan:
```
ybd --cxx-test sys_catalog-test --gtest_filter SysCatalogTest.TestNamespaceNameMigration
ybd --cxx-test yb-admin-test_ent --gtest_filter AdminCliTest.TestListSnapshotWithNamespaceNameMigration
```

Reviewers: hsunder, zdrudi, asrivastava, skedia

Reviewed By: zdrudi

Subscribers: yql, yguan, ybase, bogdan

Tags: #jenkins-ready

Differential Revision: https://phorge.dev.yugabyte.com/D29560
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants