Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

UpgradeTool assume default namespace exists

Description

The UpgradeTool fails with exception like this if default namespace doesn't exist:

Release Notes

Fix the CDAP UpgradeTool to not rely on the existence of a 'default' namespace.

Activity

Show:

Leonid FedotovFebruary 10, 2017 at 6:42 PM
Edited

Looking to upgrade to 4.1 very soon.
This needs to be fixed.

Ali AnwarFebruary 8, 2017 at 2:25 AM
Edited

Avoid depending on default namespace in UpgradeTool:
against release/3.5 for 3.5.4: https://github.com/caskdata/cdap/pull/7870
release/4.0: https://github.com/caskdata/cdap/pull/7924
Changes were brought into release/4.1 by a merge from release/4.0: https://github.com/caskdata/cdap/pull/7938

Terence YimJanuary 26, 2017 at 6:20 AM

Ideally the `NamespaceId.DEFAULT` should only be used in the `DefaultNamespaceEnsurer` and unit tests.

Poorna ChandraJanuary 26, 2017 at 12:36 AM

As part of this effort we should also scan all usages of NamespaceId.DEFAULT to evaluate if it is really required or not.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Affects versions

Fix versions

Priority

Created January 26, 2017 at 12:32 AM
Updated February 24, 2017 at 1:34 AM
Resolved February 10, 2017 at 8:16 PM