Re: Review Request 73524: ATLAS-4394: Build error due to wrong version of atllass-buildtools at pom.xml

2021-08-17 Thread Sarath Subramanian 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73524/#review223350
---


Ship it!




Ship It!

- Sarath Subramanian


On Aug. 17, 2021, 4:54 p.m., Sidharth Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73524/
> ---
> 
> (Updated Aug. 17, 2021, 4:54 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Disha Talreja, Jayendra Parab, 
> Nixon Rodrigues, Radhika Kundam, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4394
> https://issues.apache.org/jira/browse/ATLAS-4394
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-4394: Fixed Apache Parent POM artifact and atlas-buildtools version
> 
> 
> Diffs
> -
> 
>   pom.xml cf0eb34a7 
> 
> 
> Diff: https://reviews.apache.org/r/73524/diff/1/
> 
> 
> Testing
> ---
> 
> Manual successful Build and Precomit - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/799/
> 
> 
> Thanks,
> 
> Sidharth Mishra
> 
>

Re: Review Request 73524: ATLAS-4394: Build error due to wrong version of atllass-buildtools at pom.xml

2021-08-17 Thread Ashutosh Mestry via Review Board 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73524/#review223349
---


Ship it!




Ship It!

- Ashutosh Mestry


On Aug. 17, 2021, 11:54 p.m., Sidharth Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73524/
> ---
> 
> (Updated Aug. 17, 2021, 11:54 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Disha Talreja, Jayendra Parab, 
> Nixon Rodrigues, Radhika Kundam, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4394
> https://issues.apache.org/jira/browse/ATLAS-4394
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-4394: Fixed Apache Parent POM artifact and atlas-buildtools version
> 
> 
> Diffs
> -
> 
>   pom.xml cf0eb34a7 
> 
> 
> Diff: https://reviews.apache.org/r/73524/diff/1/
> 
> 
> Testing
> ---
> 
> Manual successful Build and Precomit - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/799/
> 
> 
> Thanks,
> 
> Sidharth Mishra
> 
>

Review Request 73524: ATLAS-4394: Build error due to wrong version of atllass-buildtools at pom.xml

2021-08-17 Thread Sidharth Mishra 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73524/
---

Review request for atlas, Ashutosh Mestry, Disha Talreja, Jayendra Parab, Nixon 
Rodrigues, Radhika Kundam, and Sarath Subramanian.


Bugs: ATLAS-4394
https://issues.apache.org/jira/browse/ATLAS-4394


Repository: atlas


Description
---

ATLAS-4394: Fixed Apache Parent POM artifact and atlas-buildtools version


Diffs
-

  pom.xml cf0eb34a7 


Diff: https://reviews.apache.org/r/73524/diff/1/


Testing
---

Manual successful Build and Precomit - 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/799/


Thanks,

Sidharth Mishra

[jira] [Assigned] (ATLAS-4394) Build error due to wrong version of atllass-buildtools at pom.xml

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra reassigned ATLAS-4394:


Assignee: Sidharth Kumar Mishra

> Build error due to wrong version of atllass-buildtools at pom.xml
> -
>
> Key: ATLAS-4394
> URL: https://issues.apache.org/jira/browse/ATLAS-4394
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Error facing while running - 
> mvn clean install -Papache-release -DskipTests -DskipDocs -DskipCheck
>  
> Error Details:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check 
> (checkstyle-check) on project apache-atlas: Execution checkstyle-check of 
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check failed: 
> Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1 or one of its 
> dependencies could not be resolved: org.apache.atlas:atlas-buildtools:jar:1.0 
> was not found in [https://repo.maven.apache.org/maven2] during a previous 
> attempt. This failure was cached in the local repository and resolution is 
> not reattempted until the update interval of central has elapsed or updates 
> are forced -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> [http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException]
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :apache-atlas
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-4394) Build error due to wrong version of atllass-buildtools at pom.xml

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 
Sidharth Kumar Mishra created ATLAS-4394:


 Summary: Build error due to wrong version of atllass-buildtools at 
pom.xml
 Key: ATLAS-4394
 URL: https://issues.apache.org/jira/browse/ATLAS-4394
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra


Error facing while running - 
mvn clean install -Papache-release -DskipTests -DskipDocs -DskipCheck
 
Error Details:
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check (checkstyle-check) 
on project apache-atlas: Execution checkstyle-check of goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check failed: Plugin 
org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1 or one of its 
dependencies could not be resolved: org.apache.atlas:atlas-buildtools:jar:1.0 
was not found in [https://repo.maven.apache.org/maven2] during a previous 
attempt. This failure was cached in the local repository and resolution is not 
reattempted until the update interval of central has elapsed or updates are 
forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
[http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException]
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :apache-atlas
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4384) Publish release artifacts

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra resolved ATLAS-4384.
--
Resolution: Fixed

Published and verified at 
[https://repository.apache.org/content/repositories/releases/org/apache/atlas/]

> Publish release artifacts
> -
>
> Key: ATLAS-4384
> URL: https://issues.apache.org/jira/browse/ATLAS-4384
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4277) [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1 under glossary glossary_1 via bulk import

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra resolved ATLAS-4277.
--
Resolution: Fixed

Already Fixed

> [Atlas: Glossary Term Bulk Import] [Regression] Unable to create term term_1 
> under glossary glossary_1 via bulk import
> --
>
> Key: ATLAS-4277
> URL: https://issues.apache.org/jira/browse/ATLAS-4277
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Unable to create term *term_1* under glossary *glossary_1* the cluster with 
> latest bits
> Import input:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms 
> glossary_1,term_1
> glossary_1,term_2{code}
> Current result:
> {code:java}
> {
>   "failedImportInfoList":[
> {
>   "parentObjectName":"glossary_1",
>   "childObjectName":"term_1",
>   "importStatus":"FAILED",
>   "remarks":"Glossary term with qualifiedName term_1@glossary_1 already 
> exists"
> }
>   ],
>   "successImportInfoList":[
> {
>   "parentObjectName":"glossary_1",
>   "childObjectName":"term_2",
>   "importStatus":"SUCCESS",
>   
> "remarks":"{\"termGuid\":\"8fe9a26a-aa14-4ed4-9a37-ef6db69ec29b\",\"qualifiedName\":\"term_2@glossary_1\"}"
> }
>   ]
> } {code}
> Even though there is no glossary with name glossary_1 and you are creating it 
> for the first time, this error is thrown.
> This was working fine on the older bits



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4266) [Atlas: Glossary Term Bulk Import] Import fails with success state

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra resolved ATLAS-4266.
--
Resolution: Fixed

This is fixed as part of 
[ATLAS-4288|https://reviews.apache.org/r/73358/bugs/ATLAS-4288/]

> [Atlas: Glossary Term Bulk Import] Import fails with success state
> --
>
> Key: ATLAS-4266
> URL: https://issues.apache.org/jira/browse/ATLAS-4266
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png, Screenshot 
> 2021-04-28 at 5.00.33 PM.png, Screenshot 2021-04-28 at 5.00.33 PM.png
>
>
> The following is a complete failure scenario, where the user inputs blank 
> spaces, here the import fails with complete failure, but the status is *200* 
> ok
> *Scenario*: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
>   "failedImportInfoList":[
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> },
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> }
>   ]
> }{code}
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=597,height=399! There is only 
> failure report in the response
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=854,height=570!
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-4266) [Atlas: Glossary Term Bulk Import] Import fails with success state

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra reassigned ATLAS-4266:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import] Import fails with success state
> --
>
> Key: ATLAS-4266
> URL: https://issues.apache.org/jira/browse/ATLAS-4266
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png, Screenshot 
> 2021-04-28 at 5.00.33 PM.png, Screenshot 2021-04-28 at 5.00.33 PM.png
>
>
> The following is a complete failure scenario, where the user inputs blank 
> spaces, here the import fails with complete failure, but the status is *200* 
> ok
> *Scenario*: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
>   "failedImportInfoList":[
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> },
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> }
>   ]
> }{code}
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=597,height=399! There is only 
> failure report in the response
> !Screenshot 2021-04-28 at 5.00.33 PM.png|width=854,height=570!
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4265) [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an error in bulk import

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra resolved ATLAS-4265.
--
Resolution: Fixed

Fixed as part of 
[ATLAS-4261|https://reviews.apache.org/r/73313/bugs/ATLAS-4261/]

> [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an 
> error in bulk import
> 
>
> Key: ATLAS-4265
> URL: https://issues.apache.org/jira/browse/ATLAS-4265
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png
>
>
> Scenario: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
>   "failedImportInfoList":[
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> },
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> }
>   ]
> }{code}
> !Screenshot 2021-04-28 at 4.34.30 PM.png|width=546,height=217!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-4265) [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an error in bulk import

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra reassigned ATLAS-4265:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import]: Error message is displayed twice for an 
> error in bulk import
> 
>
> Key: ATLAS-4265
> URL: https://issues.apache.org/jira/browse/ATLAS-4265
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-04-28 at 4.34.30 PM.png
>
>
> Scenario: Import Blank glossary and terms
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> " ", " "{code}
> *Observation:*
> {code:java}
> {
>   "failedImportInfoList":[
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> },
> {
>   "parentObjectName":"",
>   "childObjectName":null,
>   "importStatus":"FAILED",
>   "remarks":"The GlossaryName is blank for the record : [ ,  ]"
> }
>   ]
> }{code}
> !Screenshot 2021-04-28 at 4.34.30 PM.png|width=546,height=217!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4185) [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk Import

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra resolved ATLAS-4185.
--
Resolution: Fixed

Fixed as part of 
[ATLAS-4288|https://reviews.apache.org/r/73358/bugs/ATLAS-4288/]

> [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk 
> Import
> 
>
> Key: ATLAS-4185
> URL: https://issues.apache.org/jira/browse/ATLAS-4185
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-03-04 at 3.39.32 PM.png
>
>
> Input used:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_2,BwTZ_1
> glossaryBulkImport_2,BwTZ_2
> glossaryBulkImport_2,BwTZ_3
> glossaryBulkImport_2,BwTZ_4
> glossaryBulkImport_2,BwTZ_5
> glossaryBulkImport_2,BwTZ_6
> glossaryBulkImport_2,BwTZ_7
> glossaryBulkImport_2,BwTZ_8
> glossaryBulkImport_2,BwTZ_9
> glossaryBulkImport_2,BwTZ_10
> glossaryBulkImport_2,BwTZ_11
> glossaryBulkImport_2,BwTZ_12
> glossaryBulkImport_2,BwTZ_13
> glossaryBulkImport_2,BwTZ_14
> glossaryBulkImport_2,BwTZ_15
> glossaryBulkImport_2,BwTZ_16
> glossaryBulkImport_2,BwTZ_17
> glossaryBulkImport_2,BwTZ_18
> glossaryBulkImport_2,BwTZ_19
> glossaryBulkImport_2,BwTZ_20
> glossaryBulkImport_2,BwTZ_21
> glossaryBulkImport_2,BwTZ_22
> glossaryBulkImport_2,BwTZ_23
> glossaryBulkImport_2,BwTZ_24
> glossaryBulkImport_2,BwTZ_25
> glossaryBulkImport_2,BwTZ_26
> glossaryBulkImport_2,BwTZ_27
> glossaryBulkImport_2,BwTZ_28
> glossaryBulkImport_2,BwTZ_29
> glossaryBulkImport_2,BwTZ_30 {code}
> While performing bulk import *AtlasBaseException* is thrown
> {code:java}
> 2021-03-04 03:27:33,075 INFO  - 
> [etp1527953000-559:knox:POST/api/atlas/v2/glossary/import] ~ Request from 
> authenticated user: knox, URL=/api/atlas/v2/glossary/import?doAs=hrt_qa 
> (AtlasAuthenticationFilter$KerberosFilterChainWrapper:739)
> 2021-03-04 03:27:33,896 ERROR - [etp1527953000-559 - 
> 25016961-548a-47ca-905e-3a0df3bcf8db:knox:POST/api/atlas/v2/glossary/import] 
> ~ Error handling a request: 4716c7eab64cc999 (ExceptionMapperUtil:32)
> org.apache.atlas.exception.AtlasBaseException: Error occurred while creating 
> glossary term: {0}
> at 
> org.apache.atlas.glossary.GlossaryService.createGlossaryTerms(GlossaryService.java:1107)
> at 
> org.apache.atlas.glossary.GlossaryService.importGlossaryData(GlossaryService.java:1092)
> at 
> org.apache.atlas.glossary.GlossaryService$$FastClassBySpringCGLIB$$e1f893e0.invoke()
> at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at 
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$d03b0914.importGlossaryData()
> at 
> org.apache.atlas.web.rest.GlossaryREST.importGlossaryData(GlossaryREST.java:988)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
>

[jira] [Assigned] (ATLAS-4185) [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk Import

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra reassigned ATLAS-4185:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import] Facing intermittent failures with Bulk 
> Import
> 
>
> Key: ATLAS-4185
> URL: https://issues.apache.org/jira/browse/ATLAS-4185
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-03-04 at 3.39.32 PM.png
>
>
> Input used:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossaryBulkImport_2,BwTZ_1
> glossaryBulkImport_2,BwTZ_2
> glossaryBulkImport_2,BwTZ_3
> glossaryBulkImport_2,BwTZ_4
> glossaryBulkImport_2,BwTZ_5
> glossaryBulkImport_2,BwTZ_6
> glossaryBulkImport_2,BwTZ_7
> glossaryBulkImport_2,BwTZ_8
> glossaryBulkImport_2,BwTZ_9
> glossaryBulkImport_2,BwTZ_10
> glossaryBulkImport_2,BwTZ_11
> glossaryBulkImport_2,BwTZ_12
> glossaryBulkImport_2,BwTZ_13
> glossaryBulkImport_2,BwTZ_14
> glossaryBulkImport_2,BwTZ_15
> glossaryBulkImport_2,BwTZ_16
> glossaryBulkImport_2,BwTZ_17
> glossaryBulkImport_2,BwTZ_18
> glossaryBulkImport_2,BwTZ_19
> glossaryBulkImport_2,BwTZ_20
> glossaryBulkImport_2,BwTZ_21
> glossaryBulkImport_2,BwTZ_22
> glossaryBulkImport_2,BwTZ_23
> glossaryBulkImport_2,BwTZ_24
> glossaryBulkImport_2,BwTZ_25
> glossaryBulkImport_2,BwTZ_26
> glossaryBulkImport_2,BwTZ_27
> glossaryBulkImport_2,BwTZ_28
> glossaryBulkImport_2,BwTZ_29
> glossaryBulkImport_2,BwTZ_30 {code}
> While performing bulk import *AtlasBaseException* is thrown
> {code:java}
> 2021-03-04 03:27:33,075 INFO  - 
> [etp1527953000-559:knox:POST/api/atlas/v2/glossary/import] ~ Request from 
> authenticated user: knox, URL=/api/atlas/v2/glossary/import?doAs=hrt_qa 
> (AtlasAuthenticationFilter$KerberosFilterChainWrapper:739)
> 2021-03-04 03:27:33,896 ERROR - [etp1527953000-559 - 
> 25016961-548a-47ca-905e-3a0df3bcf8db:knox:POST/api/atlas/v2/glossary/import] 
> ~ Error handling a request: 4716c7eab64cc999 (ExceptionMapperUtil:32)
> org.apache.atlas.exception.AtlasBaseException: Error occurred while creating 
> glossary term: {0}
> at 
> org.apache.atlas.glossary.GlossaryService.createGlossaryTerms(GlossaryService.java:1107)
> at 
> org.apache.atlas.glossary.GlossaryService.importGlossaryData(GlossaryService.java:1092)
> at 
> org.apache.atlas.glossary.GlossaryService$$FastClassBySpringCGLIB$$e1f893e0.invoke()
> at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at 
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$d03b0914.importGlossaryData()
> at 
> org.apache.atlas.web.rest.GlossaryREST.importGlossaryData(GlossaryREST.java:988)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
>

[jira] [Resolved] (ATLAS-4140) [Atlas: Glossary Term Bulk Import] When imported with only glossary name incorrect message is conveyed

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra resolved ATLAS-4140.
--
Resolution: Fixed

Fixed as part of 
[ATLAS-4261|https://reviews.apache.org/r/73313/bugs/ATLAS-4261/]

> [Atlas: Glossary Term Bulk Import] When imported with only glossary name 
> incorrect message is conveyed
> --
>
> Key: ATLAS-4140
> URL: https://issues.apache.org/jira/browse/ATLAS-4140
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-02-05 at 4.15.35 PM.png
>
>
> On uploading a file with no term name, incorrect message is conveyed
> Please note there is no "*,*" at the end
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1
>  {code}
> Note:
> When the data is "glossary_1," instead of "glossary_1" then the right message 
> is thrown
> The above input should convey "term name cannot be blank or empty"
> but it throws "No data found in the uploaded file"
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-4140) [Atlas: Glossary Term Bulk Import] When imported with only glossary name incorrect message is conveyed

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra reassigned ATLAS-4140:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import] When imported with only glossary name 
> incorrect message is conveyed
> --
>
> Key: ATLAS-4140
> URL: https://issues.apache.org/jira/browse/ATLAS-4140
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: Screenshot 2021-02-05 at 4.15.35 PM.png
>
>
> On uploading a file with no term name, incorrect message is conveyed
> Please note there is no "*,*" at the end
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1
>  {code}
> Note:
> When the data is "glossary_1," instead of "glossary_1" then the right message 
> is thrown
> The above input should convey "term name cannot be blank or empty"
> but it throws "No data found in the uploaded file"
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4132) [Atlas: Glossary Term Bulk Import] When all data is populated with right input bulk import fails

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra resolved ATLAS-4132.
--
Resolution: Fixed

Fixed as part of 
[ATLAS-4191|https://reviews.apache.org/r/73218/bugs/ATLAS-4191/]

> [Atlas: Glossary Term Bulk Import] When all data is populated with right 
> input bulk import fails
> 
>
> Key: ATLAS-4132
> URL: https://issues.apache.org/jira/browse/ATLAS-4132
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> When all the fields in the bulk import are populated, bulk import fails with 
> the following error
>  Please note that glossary_1 and term_1 are being created as a part of this 
> same request. 
> {code:java}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"The uploaded file has not 
> been processed due to the following errors : \n[\nThe provided Reference 
> Glossary and TermName does not exist in the system term_1:glossary_1 for 
> record with TermName  : term_3 and GlossaryName : glossary_3, \nThe provided 
> Reference Glossary and TermName does not exist in the system 
> term_1:glossary_1 for record with TermName  : term_3 and GlossaryName : 
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in 
> the system term_1:glossary_1 for record with TermName  : term_3 and 
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName 
> does not exist in the system term_1:glossary_1 for record with TermName  : 
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and 
> TermName does not exist in the system term_1:glossary_1 for record with 
> TermName  : term_3 and GlossaryName : glossary_3, \nThe provided Reference 
> Glossary and TermName does not exist in the system term_1:glossary_1 for 
> record with TermName  : term_3 and GlossaryName : glossary_3, \nThe provided 
> Reference Glossary and TermName does not exist in the system 
> term_1:glossary_1 for record with TermName  : term_3 and GlossaryName : 
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in 
> the system term_2:glossary_2 for record with TermName  : term_3 and 
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName 
> does not exist in the system term_1:glossary_1 for record with TermName  : 
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and 
> TermName does not exist in the system term_1:glossary_1 for record with 
> TermName  : term_3 and GlossaryName : glossary_3, \nThe provided Reference 
> Glossary and TermName does not exist in the system term_1:glossary_1 for 
> record with TermName  : term_3 and GlossaryName : glossary_3, \nThe provided 
> Reference Glossary and TermName does not exist in the system 
> term_1:glossary_1 for record with TermName  : term_3 and GlossaryName : 
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in 
> the system term_1:glossary_1 for record with TermName  : term_3 and 
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName 
> does not exist in the system term_1:glossary_1 for record with TermName  : 
> term_3 and GlossaryName : glossary_3]"}
> {code}
>  
> File contents:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1
> glossary_2,term_2
> glossary_3,term_3,"short description for glossary_3","this can be used as 
> long description for glossary_3 ", "random glossary Example", "G3", "Usage 
> details", "glossaryAttribute:100%|termAttribute:0%", 
> "glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1|glossary_2:term_2","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1"
>  {code}
> Expectation:
> Since term_1 of glossary_1 and term_2 of glossary_2 are created as a part of 
> this same request, glossary_3 and term_3 creation should succeed and 
> associate it will the remaining data.
> Observation:
> When the related terms are created as a part of the current import, the call 
> fails



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-4132) [Atlas: Glossary Term Bulk Import] When all data is populated with right input bulk import fails

2021-08-17 Thread Sidharth Kumar Mishra (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sidharth Kumar Mishra reassigned ATLAS-4132:


Assignee: Sidharth Kumar Mishra

> [Atlas: Glossary Term Bulk Import] When all data is populated with right 
> input bulk import fails
> 
>
> Key: ATLAS-4132
> URL: https://issues.apache.org/jira/browse/ATLAS-4132
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> When all the fields in the bulk import are populated, bulk import fails with 
> the following error
>  Please note that glossary_1 and term_1 are being created as a part of this 
> same request. 
> {code:java}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"The uploaded file has not 
> been processed due to the following errors : \n[\nThe provided Reference 
> Glossary and TermName does not exist in the system term_1:glossary_1 for 
> record with TermName  : term_3 and GlossaryName : glossary_3, \nThe provided 
> Reference Glossary and TermName does not exist in the system 
> term_1:glossary_1 for record with TermName  : term_3 and GlossaryName : 
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in 
> the system term_1:glossary_1 for record with TermName  : term_3 and 
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName 
> does not exist in the system term_1:glossary_1 for record with TermName  : 
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and 
> TermName does not exist in the system term_1:glossary_1 for record with 
> TermName  : term_3 and GlossaryName : glossary_3, \nThe provided Reference 
> Glossary and TermName does not exist in the system term_1:glossary_1 for 
> record with TermName  : term_3 and GlossaryName : glossary_3, \nThe provided 
> Reference Glossary and TermName does not exist in the system 
> term_1:glossary_1 for record with TermName  : term_3 and GlossaryName : 
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in 
> the system term_2:glossary_2 for record with TermName  : term_3 and 
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName 
> does not exist in the system term_1:glossary_1 for record with TermName  : 
> term_3 and GlossaryName : glossary_3, \nThe provided Reference Glossary and 
> TermName does not exist in the system term_1:glossary_1 for record with 
> TermName  : term_3 and GlossaryName : glossary_3, \nThe provided Reference 
> Glossary and TermName does not exist in the system term_1:glossary_1 for 
> record with TermName  : term_3 and GlossaryName : glossary_3, \nThe provided 
> Reference Glossary and TermName does not exist in the system 
> term_1:glossary_1 for record with TermName  : term_3 and GlossaryName : 
> glossary_3, \nThe provided Reference Glossary and TermName does not exist in 
> the system term_1:glossary_1 for record with TermName  : term_3 and 
> GlossaryName : glossary_3, \nThe provided Reference Glossary and TermName 
> does not exist in the system term_1:glossary_1 for record with TermName  : 
> term_3 and GlossaryName : glossary_3]"}
> {code}
>  
> File contents:
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1
> glossary_2,term_2
> glossary_3,term_3,"short description for glossary_3","this can be used as 
> long description for glossary_3 ", "random glossary Example", "G3", "Usage 
> details", "glossaryAttribute:100%|termAttribute:0%", 
> "glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1|glossary_2:term_2","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1","glossary_1:term_1"
>  {code}
> Expectation:
> Since term_1 of glossary_1 and term_2 of glossary_2 are created as a part of 
> this same request, glossary_3 and term_3 creation should succeed and 
> associate it will the remaining data.
> Observation:
> When the related terms are created as a part of the current import, the call 
> fails



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3917) While deleting parent tag, shows incorrect message.

2021-08-17 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400348#comment-17400348
 ] 

ASF subversion and git services commented on ATLAS-3917:


Commit 40591564a4552a4086017d18bcb1047cb90a19fe in atlas's branch 
refs/heads/branch-2.0 from Shraddha Chauhan
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4059156 ]

ATLAS-3917: While deleting parent tag, shows incorrect message

Signed-off-by: Nikhil Bonte 
(cherry picked from commit d160138d5e7d23cd8c4345dba55c140dc9bc84b2)


> While deleting parent tag, shows incorrect message.
> ---
>
> Key: ATLAS-3917
> URL: https://issues.apache.org/jira/browse/ATLAS-3917
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Durga Kadam
>Assignee: chaitali borole
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: tag_with_{0}_reproducible.mkv
>
>
> Actual Behaviour - While deleting parent tag if the tag is not associated 
> with any entity shows this message :: "Failed to delete classification 
> 'parent_abc'. Given type \{0} has reference."
> Expected Result - There should be value instead of \{0}
> Steps to generate
>  # Create tag with sub classification.
>  # Don't associate the created parent tag with any of the entity
>  # Try to delete the parent tag
>  # Shows validation message with some encrypted value
>  
> PFA Evidence file



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4233) [Atlas: Audits] When a term is added or removed, v1 api displays action as null instead of TERM_ADD or TERM_DELETE

2021-08-17 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400349#comment-17400349
 ] 

ASF subversion and git services commented on ATLAS-4233:


Commit 36ce8f09760db7a8d7170b2ceafc7ee4e97f1478 in atlas's branch 
refs/heads/branch-2.0 from Shraddha Chauhan
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=36ce8f0 ]

ATLAS-4233: Audits: When a term is added or removed, v1 api displays action as 
null instead of TERM_ADD or TERM_DELETE

Signed-off-by: Nikhil Bonte 
(cherry picked from commit 625bfd2064b36597eee795b51ed03b1d39190107)


> [Atlas: Audits] When a term is added or removed, v1 api displays action as 
> null instead of TERM_ADD or TERM_DELETE
> --
>
> Key: ATLAS-4233
> URL: https://issues.apache.org/jira/browse/ATLAS-4233
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Attachments: Screenshot 2021-04-01 at 7.58.12 PM.png, Screenshot 
> 2021-04-01 at 8.04.11 PM.png
>
>
> *Scenario:*
>  * Add a term to an entity.
>  * Remove the term from the entity
> Audits will be generated. Here the action should appear as *TERM_ADD or 
> TERM_DELETE*
> But the value is null instead. Please check the reference below
> {code:java}
> {
> "entityId": "d83d7d10-c137-4a16-8018-70692cd555b2",
> "timestamp": 1617286735612,
> "user": "hrt_qa",
> "action": null,
> "details": "Added term: 
> {\"guid\":\"700bafef-ac2b-489b-a54b-0dc5741e2a6f\",\"qualifiedName\":\"hdcpg_term@hdcpg_glossary\",\"name\":\"hdcpg_term\"}",
> "eventKey": 
> "d83d7d10-c137-4a16-8018-70692cd555b2:1617286735612:0:1617286735676"
> } {code}
> *v1: https://:31443/api/atlas/entities//audit*
> *TERM_ADD*
> !Screenshot 2021-04-01 at 7.58.12 PM.png|width=584,height=179!
> *TERM_DELETE*
> !Screenshot 2021-04-01 at 8.04.11 PM.png|width=581,height=174!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4233) [Atlas: Audits] When a term is added or removed, v1 api displays action as null instead of TERM_ADD or TERM_DELETE

2021-08-17 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400346#comment-17400346
 ] 

ASF subversion and git services commented on ATLAS-4233:


Commit 625bfd2064b36597eee795b51ed03b1d39190107 in atlas's branch 
refs/heads/master from Shraddha Chauhan
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=625bfd2 ]

ATLAS-4233: Audits: When a term is added or removed, v1 api displays action as 
null instead of TERM_ADD or TERM_DELETE

Signed-off-by: Nikhil Bonte 


> [Atlas: Audits] When a term is added or removed, v1 api displays action as 
> null instead of TERM_ADD or TERM_DELETE
> --
>
> Key: ATLAS-4233
> URL: https://issues.apache.org/jira/browse/ATLAS-4233
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Attachments: Screenshot 2021-04-01 at 7.58.12 PM.png, Screenshot 
> 2021-04-01 at 8.04.11 PM.png
>
>
> *Scenario:*
>  * Add a term to an entity.
>  * Remove the term from the entity
> Audits will be generated. Here the action should appear as *TERM_ADD or 
> TERM_DELETE*
> But the value is null instead. Please check the reference below
> {code:java}
> {
> "entityId": "d83d7d10-c137-4a16-8018-70692cd555b2",
> "timestamp": 1617286735612,
> "user": "hrt_qa",
> "action": null,
> "details": "Added term: 
> {\"guid\":\"700bafef-ac2b-489b-a54b-0dc5741e2a6f\",\"qualifiedName\":\"hdcpg_term@hdcpg_glossary\",\"name\":\"hdcpg_term\"}",
> "eventKey": 
> "d83d7d10-c137-4a16-8018-70692cd555b2:1617286735612:0:1617286735676"
> } {code}
> *v1: https://:31443/api/atlas/entities//audit*
> *TERM_ADD*
> !Screenshot 2021-04-01 at 7.58.12 PM.png|width=584,height=179!
> *TERM_DELETE*
> !Screenshot 2021-04-01 at 8.04.11 PM.png|width=581,height=174!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3917) While deleting parent tag, shows incorrect message.

2021-08-17 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400345#comment-17400345
 ] 

ASF subversion and git services commented on ATLAS-3917:


Commit d160138d5e7d23cd8c4345dba55c140dc9bc84b2 in atlas's branch 
refs/heads/master from Shraddha Chauhan
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d160138 ]

ATLAS-3917: While deleting parent tag, shows incorrect message

Signed-off-by: Nikhil Bonte 


> While deleting parent tag, shows incorrect message.
> ---
>
> Key: ATLAS-3917
> URL: https://issues.apache.org/jira/browse/ATLAS-3917
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Durga Kadam
>Assignee: chaitali borole
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: tag_with_{0}_reproducible.mkv
>
>
> Actual Behaviour - While deleting parent tag if the tag is not associated 
> with any entity shows this message :: "Failed to delete classification 
> 'parent_abc'. Given type \{0} has reference."
> Expected Result - There should be value instead of \{0}
> Steps to generate
>  # Create tag with sub classification.
>  # Don't associate the created parent tag with any of the entity
>  # Try to delete the parent tag
>  # Shows validation message with some encrypted value
>  
> PFA Evidence file



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 73508: ATLAS-4233 [Atlas: Audits] When a term is added or removed, v1 api displays action as null instead of TERM_ADD or TERM_DELETE

2021-08-17 Thread Nixon Rodrigues 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73508/#review223346
---


Ship it!




Ship It!

- Nixon Rodrigues


On Aug. 10, 2021, 6:09 a.m., Shraddha Pardeshi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73508/
> ---
> 
> (Updated Aug. 10, 2021, 6:09 a.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Nikhil Bonte, Nixon Rodrigues, and 
> Pinal Shah.
> 
> 
> Bugs: ATLAS-4233
> https://issues.apache.org/jira/browse/ATLAS-4233
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When we add or remove a term to an entity,in audits the action should appear 
> as TERM_ADD or TERM_DELETE
> But instead the value is giving null.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
>  5c08874ff 
> 
> 
> Diff: https://reviews.apache.org/r/73508/diff/1/
> 
> 
> Testing
> ---
> 
> PC - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/792/console
> 
> 
> Thanks,
> 
> Shraddha Pardeshi
> 
>

Re: Review Request 73508: ATLAS-4233 [Atlas: Audits] When a term is added or removed, v1 api displays action as null instead of TERM_ADD or TERM_DELETE

2021-08-17 Thread Nikhil Bonte 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73508/#review223345
---


Ship it!




Ship It!

- Nikhil Bonte


On Aug. 10, 2021, 11:39 a.m., Shraddha Pardeshi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73508/
> ---
> 
> (Updated Aug. 10, 2021, 11:39 a.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Nikhil Bonte, Nixon Rodrigues, and 
> Pinal Shah.
> 
> 
> Bugs: ATLAS-4233
> https://issues.apache.org/jira/browse/ATLAS-4233
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When we add or remove a term to an entity,in audits the action should appear 
> as TERM_ADD or TERM_DELETE
> But instead the value is giving null.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
>  5c08874ff 
> 
> 
> Diff: https://reviews.apache.org/r/73508/diff/1/
> 
> 
> Testing
> ---
> 
> PC - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/792/console
> 
> 
> Thanks,
> 
> Shraddha Pardeshi
> 
>

Re: Review Request 73502: ATLAS-3917 While deleting parent tag, shows incorrect message.

2021-08-17 Thread Nikhil Bonte 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73502/#review223344
---


Fix it, then Ship it!




Fix it, then Ship it!


repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasTypeDefGraphStoreV2.java
Line 273 (original), 273 (patched)


move #273 inside if condition (#274), so that name will be fetched only 
when exception is to be thrown.


- Nikhil Bonte


On Aug. 5, 2021, 12:46 p.m., Shraddha Pardeshi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73502/
> ---
> 
> (Updated Aug. 5, 2021, 12:46 p.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Nikhil Bonte, Nixon Rodrigues, and 
> Pinal Shah.
> 
> 
> Bugs: ATLAS-3917
> https://issues.apache.org/jira/browse/ATLAS-3917
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> -Actual Behaviour : While deleting parent tag if the tag is not associated 
> with any entity shows this message- "Given type {0} has reference."
> -Expected Result: There should be tag name instead of {0}
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasTypeDefGraphStoreV2.java
>  b9d41bbba 
>   
> repository/src/test/java/org/apache/atlas/repository/store/graph/v2/AtlasClassificationDefStoreV2Test.java
>  3242a33ad 
> 
> 
> Diff: https://reviews.apache.org/r/73502/diff/2/
> 
> 
> Testing
> ---
> 
> -Manual testing done on local server
> 
> -Test case added.
> 
> PC - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/779/console
> 
> 
> Thanks,
> 
> Shraddha Pardeshi
> 
>

[jira] [Resolved] (ATLAS-3958) When updating a type with non-existing super type as an un-authorized user gives in-correct message in response

2021-08-17 Thread Nixon Rodrigues (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nixon Rodrigues resolved ATLAS-3958.

Resolution: Duplicate

> When updating a type with non-existing super type as an un-authorized user 
> gives in-correct message in response
> ---
>
> Key: ATLAS-3958
> URL: https://issues.apache.org/jira/browse/ATLAS-3958
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Nixon Rodrigues
>Priority: Minor
>
> When an unauthorised  user updates a type, by adding a non-existing 
> super-type, incorret error message is thrown
> *Repro steps:*
> Create a classification (as authorised user)
> Update the classification  as un-authorised user(*hrt_1*), by adding a 
> non-existing super type *qqq*
> *Observed error message:*
> {code}
> {
> "errorCode": "ATLAS-400-00-029",
> "errorMessage": "Given typename qqq was invalid"
> }
> {code}
> *Expected error message:*
> {code}
> {
> "errorCode": "ATLAS-403-00-001",
> "errorMessage": "hrt_1 is not authorized to perform update classification-def 
> child"
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4096) Quick Search : Search with query text containing space returns no records.

2021-08-17 Thread Pinal Shah (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pinal Shah resolved ATLAS-4096.
---
Resolution: Fixed

> Quick Search : Search with query text containing space returns no records.
> --
>
> Key: ATLAS-4096
> URL: https://issues.apache.org/jira/browse/ATLAS-4096
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>  Labels: quicksearch
> Attachments: Screenshot from 2021-01-07 14-00-05.png, Screenshot from 
> 2021-01-07 14-00-22.png
>
>
> Selected ml_model_build entity type where some entity names contain space.
>  E.g. "Simple Model 158"
> When the "search by Text" added as "Simple*". It returned 8 records 
> containing space in the entities name. But when changed to "Simple Model*" 
> returned no records.
> Attached the screenshots for the above 2 scenarios.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-3678) User defined properties are not listed under suggestions

2021-08-17 Thread Pinal Shah (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pinal Shah resolved ATLAS-3678.
---
Resolution: Not A Bug

> User defined properties are not listed under suggestions
> 
>
> Key: ATLAS-3678
> URL: https://issues.apache.org/jira/browse/ATLAS-3678
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal Shah
>Priority: Minor
> Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot 
> 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, 
> Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 
> PM.png
>
>
> When user-defined properties are added to an entity, and when we type the 
> "user-defined property" in the global search bar, the expectation is that 
>  # The corresponding entity appears in the quick search, entities dropdown. 
> This is working 
>  # The user-defined property itself should appear in the suggestions 
> dropdown. This is not working
> Tried similar tests with labels, entities that are tagged with labels appear 
> in the quick search drop down, and the labels itself appear as part of the 
> suggestions. Attached are the screenshots.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (ATLAS-3678) User defined properties are not listed under suggestions

2021-08-17 Thread Pinal Shah (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399753#comment-17399753
 ] 

Pinal Shah edited comment on ATLAS-3678 at 8/17/21, 8:19 AM:
-

This issue is because search weight for the user-defined attributes is kept low.

Workaround: increase search weight of custom attributes greater than or equal 
to 8 (MIN_SEARCH_WEIGHT_FOR_SUGGESTIONS)


was (Author: pinal.shah):
This issue is because search weight for the user-defined attributes is kept low.

> User defined properties are not listed under suggestions
> 
>
> Key: ATLAS-3678
> URL: https://issues.apache.org/jira/browse/ATLAS-3678
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal Shah
>Priority: Minor
> Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot 
> 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, 
> Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 
> PM.png
>
>
> When user-defined properties are added to an entity, and when we type the 
> "user-defined property" in the global search bar, the expectation is that 
>  # The corresponding entity appears in the quick search, entities dropdown. 
> This is working 
>  # The user-defined property itself should appear in the suggestions 
> dropdown. This is not working
> Tried similar tests with labels, entities that are tagged with labels appear 
> in the quick search drop down, and the labels itself appear as part of the 
> suggestions. Attached are the screenshots.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-2328) Regression : Request body with invalid JSON gets accepted by Atlas

2021-08-17 Thread Shraddha Kapilsingh Pardeshi (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400167#comment-17400167
 ] 

Shraddha Kapilsingh Pardeshi commented on ATLAS-2328:
-

This is expected behaviour because the SearchParameter object would be from 
starting curly braces "\{"to end curly braces "}" and parsing stops at the 
closing braces in serialisation. So if we write anything after curly braces it 
ignores that part and accept as valid json.

> Regression : Request body with invalid JSON gets accepted by Atlas
> --
>
> Key: ATLAS-2328
> URL: https://issues.apache.org/jira/browse/ATLAS-2328
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha S
>Priority: Minor
>
> {code}
> {
> "tagFilters": null,
> "classification": "*", 
> "entityFilters": null,
> "excludeDeletedEntities": true, 
> "typeName": "hdfs_path",
> "limit": 100,
> "offset": 0,
> "includeClassificationAttributes": false, 
> "attributes": []  
> }}
> {code}
> s a wrong JSON with extra braces at the end.
> Atlas accepts such JSONs and returns 20X code.
> Options



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3682) Multivalued attributes are not listed under Business Metadata Attribute filter

2021-08-17 Thread Pinal Shah (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pinal Shah updated ATLAS-3682:
--
Issue Type: Improvement  (was: Bug)

> Multivalued attributes are not listed under Business Metadata Attribute filter
> --
>
> Key: ATLAS-3682
> URL: https://issues.apache.org/jira/browse/ATLAS-3682
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal Shah
>Priority: Major
> Attachments: Screenshot 2020-03-24 at 1.01.54 AM.png, Screenshot 
> 2020-03-24 at 1.02.28 AM.png
>
>
> Added attributes of different types, noticed that the multi valued attributes 
> are bot being listed for an entity filter, even when the attribute is 
> applicable to that entity. Screenshots attached below.
> As you can see, the attribute "Reviewed by" which is of type "array" 
> is not being listed under the Business Metadata Attribute drop down.
> CC: [~kevalbhatt]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3682) Multivalued attributes are not listed under Business Metadata Attribute filter

2021-08-17 Thread Pinal Shah (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pinal Shah updated ATLAS-3682:
--
Labels: BasicSearch  (was: )

> Multivalued attributes are not listed under Business Metadata Attribute filter
> --
>
> Key: ATLAS-3682
> URL: https://issues.apache.org/jira/browse/ATLAS-3682
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Pinal Shah
>Priority: Major
>  Labels: BasicSearch
> Attachments: Screenshot 2020-03-24 at 1.01.54 AM.png, Screenshot 
> 2020-03-24 at 1.02.28 AM.png
>
>
> Added attributes of different types, noticed that the multi valued attributes 
> are bot being listed for an entity filter, even when the attribute is 
> applicable to that entity. Screenshots attached below.
> As you can see, the attribute "Reviewed by" which is of type "array" 
> is not being listed under the Business Metadata Attribute drop down.
> CC: [~kevalbhatt]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)