Reasoning from Gaurav on another thread. "There is a workaround for this but that will be bad for usability, as user has to to edit the view configuration and save it after the upgrade.²
Thanks Jayush On 8/20/16, 6:10 PM, "Jayush Luniya" <[email protected]> wrote: >+1 > >From: Jayush Luniya ><[email protected]<mailto:[email protected]>> >Date: Saturday, August 20, 2016 at 10:08 AM >To: Gaurav Nagar <[email protected]<mailto:[email protected]>> >Cc: "[email protected]<mailto:[email protected]>" ><[email protected]<mailto:[email protected]>> >Subject: Re: Approval for AMBARI-18218 > >Gaurav, >Is there a workaround for the issue? Lets explore if we can avoid churn >in 2.4.0. >Thanks >Jayush > > >From: Gaurav Nagar <[email protected]<mailto:[email protected]>> >Date: Saturday, August 20, 2016 at 4:31 AM >To: Jayush Luniya ><[email protected]<mailto:[email protected]>> >Cc: "[email protected]<mailto:[email protected]>" ><[email protected]<mailto:[email protected]>> >Subject: Approval for AMBARI-18218 > >HI Jayush > >Please review patch for Ambari -2.4.0. >https://issues.apache.org/jira/browse/AMBARI-18218 > >Thanks >Gaurav
