> On Sept. 5, 2019, 6:16 p.m., Ashutosh Mestry wrote: > > dashboardv2/public/js/utils/CommonViewFunction.js > > Lines 758 (patched) > > <https://reviews.apache.org/r/71439/diff/1/?file=2164049#file2164049line758> > > > > Is there any central logic for creating qualifiedNames?
Extracted the logic into a function (getUpdatedQualifiedName()). - Saqeeb ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/71439/#review217595 ----------------------------------------------------------- On Sept. 6, 2019, 9:32 a.m., Saqeeb Shaikh wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/71439/ > ----------------------------------------------------------- > > (Updated Sept. 6, 2019, 9:32 a.m.) > > > Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, > and Sarath Subramanian. > > > Bugs: ATLAS-3391 > https://issues.apache.org/jira/browse/ATLAS-3391 > > > Repository: atlas > > > Description > ------- > > When a term (with name T) belonging to glossary (G) is updated to (T1), its > qualified name does not gets updated. Search by term displays qualified names > of the terms, hence old name is seen there. The handling for updating > qualified name was present but since we were copying the qualified name from > the DB object, the handling code never got trigerred. > > This patch also includes required UI side changes. > > > Diffs > ----- > > dashboardv2/public/js/utils/CommonViewFunction.js 9cea1b8 > repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java > 9229d2d > > > Diff: https://reviews.apache.org/r/71439/diff/2/ > > > Testing > ------- > > Manually tested by updating term and searching using the updated term > qualified name. > > > Thanks, > > Saqeeb Shaikh > >
