Build #4,952

License check with RAT and Checkstyle

Build result summary


5 minutes
fedf09ea6574933f420a2da3ee54958c95ed34c2 fedf09ea6574933f420a2da3ee54958c95ed34c2
Successful since
#4616 ()

Code commits

Author Commit Message Commit date
Ajai <> Ajai <> fedf09ea6574933f420a2da3ee54958c95ed34c2 fedf09ea6574933f420a2da3ee54958c95ed34c2 Merge pull request #12349 from cdapio/bugfix-ui/CDAP-16975-6.3
[CDAP-16975] Default to latest version while adding plugin from left …
Ajai Narayan Ajai Narayan 2385162f33f71701dd1f303e6441b9dbd4dd83c6 m 2385162f33f71701dd1f303e6441b9dbd4dd83c6 [CDAP-16975] Default to latest version while adding plugin from left panel +  [CDAP-16976] Reset the default plugin store post CDAP upgrade
This is to ensure we have the following behavior,

1. Pre-upgrade - When the user chooses a plugin from side panel in studio we
choose the latest version and set that as default.

2. Pre-upgrade - When the user consciously changes to a older version of the plugin we
default to that specific version after that.

3. Post-upgrade - Once the user upgrades the CDAP platform, we no longer want them to use
the default plugin version they were using in the previous version of CDAP. So we reset
the default plugins and start afresh

4. Post-upgrade, Post-reset - After reset post upgrade we then follow the pre-upgrade behavior
where from then on we choose the latest version of the plugin for the first time and default
to that for subsequent usage.

As part of that we now store the current version of CDAP in the user store. Post upgrade
there will be a mis-match between the cdap version in the user store and the current cdap
version the user is running, indicating that there was an upgrade upon which we then reset.

JIRA issues

Unknown Issue TypeCDAP-16975Could not obtain issue details from JIRA
Unknown Issue TypeCDAP-16976Could not obtain issue details from JIRA