Skip to:

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

Allow Dataset upgrade

Description

Dataset upgrade is currently done in an ad-hoc manner by running a force upgrade by suspending checks. This JIRA is to do it the right way.

Release Notes

None

Activity

Show:

Priyanka Nambiar March 25, 2015 at 1:18 AM

Marking this a blocker for 3.0

Gary Helmling February 25, 2015 at 9:55 PM

This requires support for dataset versioning, so that we know when an upgrade can/should be performed.

NitinM February 21, 2015 at 11:52 PM
Edited

Let's port the changes then to 2.8.0. Moving the parent to 3.0.0 and then creating a new JIRA issue for porting the changes.

Poorna Chandra February 21, 2015 at 11:51 PM

If we are going to move this to 3.0.0, then we'll have to port the changes from CDAP-1253 to 2.8.0.

Gary Helmling February 21, 2015 at 11:48 PM

Yes this is a long term issue. Will not happen in 2.8. The short term fix is the force upgrade flag in 2.6.2. That should be ported to 2.8 / develop.

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Affects versions

Components

Priority

Created January 24, 2015 at 2:22 AM
Updated June 9, 2020 at 1:27 AM
Resolved June 9, 2020 at 1:27 AM
Configure