[jira] [Updated] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3857:
---
Description: 
When deleted term, it does not get delete immediately when tried again to 
delete shows 'Something went wrong msg'

Expected :: On first delete it should show loading sign and/or delete button 
should get disabled

Actual:: It takes long to delete a term and as the delete button is enabled 
user tried to delete it again. When deleted the same term again Shows 
'Something went wrong' msg.

 

Server Logs are::

2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
to exception (StandardJanusGraph:808)
org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
contention
 at 
org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
 at 
org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
 at 
org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
 at 
org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
 at 
org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
 at 
org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
 at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.commit(StandardJanusGraphTx.java:1425)
 at 
org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.doCommit(JanusGraphBlueprintsGraph.java:297)
 at 
org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.commit(AbstractTransaction.java:104)
 at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.commit(AtlasJanusGraph.java:248)
 at 
org.apache.atlas.GraphTransactionInterceptor.doCommit(GraphTransactionInterceptor.java:157)
 at 
org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:152)
 at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:91)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
 at 
org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$71fceabc.deleteTerm()
 at 
org.apache.atlas.web.rest.GlossaryREST.deleteGlossaryTerm(GlossaryREST.java:590)
 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$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:167)

  was:When deleted term, it does not get delete immediately when tried again to 
delete shows 'Something went wrong msg'


> [UI] When deleted term same term twice shows 'Something went wrong' msg
> ---
>
> Key: ATLAS-3857
> URL: https://issues.apache.org/jira/browse/ATLAS-3857
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Major
>
> When deleted term, it does not get delete immediately when tried again to 
> delete shows 'Something went wrong msg'
> Expected :: On first delete it should show loading sign and/or delete button 
> should get disabled
> Actual:: It takes long to delete a term and as the delete button is enabled 
> user tried to delete it again. When deleted the same term again Shows 
> 'Something went wrong' msg.
>  
> Server Logs are::
> 2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
> 1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
> to exception (StandardJanusGraph:808)
> org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
> contention
>  at 
> org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
>  at 
> org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
>  at 
> org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
>  at 
> org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
>  at 
> 

[jira] [Updated] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3857:
---
Attachment: delete term something went wrong issue.webm

> [UI] When deleted term same term twice shows 'Something went wrong' msg
> ---
>
> Key: ATLAS-3857
> URL: https://issues.apache.org/jira/browse/ATLAS-3857
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Major
> Attachments: delete term something went wrong issue.webm
>
>
> When deleted term, it does not get delete immediately when tried again to 
> delete shows 'Something went wrong msg'
> Expected :: On first delete it should show loading sign and/or delete button 
> should get disabled
> Actual:: It takes long to delete a term and as the delete button is enabled 
> user tried to delete it again. When deleted the same term again Shows 
> 'Something went wrong' msg.
>  
> Server Logs are::
> 2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
> 1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
> to exception (StandardJanusGraph:808)
> org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
> contention
>  at 
> org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
>  at 
> org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
>  at 
> org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
>  at 
> org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
>  at 
> org.janusgraph.graphdb.transaction.StandardJanusGraphTx.commit(StandardJanusGraphTx.java:1425)
>  at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.doCommit(JanusGraphBlueprintsGraph.java:297)
>  at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.commit(AbstractTransaction.java:104)
>  at 
> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.commit(AtlasJanusGraph.java:248)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommit(GraphTransactionInterceptor.java:157)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:152)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:91)
>  at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
>  at 
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$71fceabc.deleteTerm()
>  at 
> org.apache.atlas.web.rest.GlossaryREST.deleteGlossaryTerm(GlossaryREST.java:590)
>  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$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:167)



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

[jira] [Updated] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3857:
---
Description: 
When deleted term, it does not get delete immediately when tried again to 
delete the same term shows 'Something went wrong msg'. PFA Video

*Expected ::* On first delete it should show loading sign and/or delete button 
should get disabled

*Actual::* It takes long to delete a term and as the delete button is enabled 
user tried to delete it again. When deleted the same term again Shows 
'Something went wrong' msg.

 Server Logs are as follows::

2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
to exception (StandardJanusGraph:808)
 org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
contention
 at 
org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
 at 
org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
 at 
org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
 at 
org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
 at 
org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
 at 
org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
 at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.commit(StandardJanusGraphTx.java:1425)
 at 
org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.doCommit(JanusGraphBlueprintsGraph.java:297)
 at 
org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.commit(AbstractTransaction.java:104)
 at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.commit(AtlasJanusGraph.java:248)
 at 
org.apache.atlas.GraphTransactionInterceptor.doCommit(GraphTransactionInterceptor.java:157)
 at 
org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:152)
 at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:91)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
 at 
org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$71fceabc.deleteTerm()
 at 
org.apache.atlas.web.rest.GlossaryREST.deleteGlossaryTerm(GlossaryREST.java:590)
 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$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:167)

  was:
When deleted term, it does not get delete immediately when tried again to 
delete shows 'Something went wrong msg'

Expected :: On first delete it should show loading sign and/or delete button 
should get disabled

Actual:: It takes long to delete a term and as the delete button is enabled 
user tried to delete it again. When deleted the same term again Shows 
'Something went wrong' msg.

 

Server Logs are::

2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
to exception (StandardJanusGraph:808)
org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
contention
 at 
org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
 at 
org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
 at 
org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
 at 
org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
 at 
org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
 at 
org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
 at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.commit(StandardJanusGraphTx.java:1425)
 at 
org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.doCommit(JanusGraphBlueprintsGraph.java:297)
 at 
org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.commit(AbstractTransaction.java:104)
 at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.commit(AtlasJanusGraph.java:248)
 at 

[jira] [Updated] (ATLAS-3862) [UI] When added term with large name validation msgs are misaligned. PFA snaps

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3862:
---
Attachment: deleted_term_with_embedded_tag_validation_msg_misalignment.png
added_glossary_with_embedded_tag_success_msg_misalignment.png

> [UI] When added term with large name validation msgs are misaligned. PFA snaps
> --
>
> Key: ATLAS-3862
> URL: https://issues.apache.org/jira/browse/ATLAS-3862
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Durga Kadam
>Priority: Major
> Attachments: 
> added_glossary_with_embedded_tag_success_msg_misalignment.png, 
> deleted_term_with_embedded_tag_validation_msg_misalignment.png
>
>




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

[jira] [Created] (ATLAS-3862) [UI] When added term with large name validation msgs are misaligned. PFA snaps

[Durga Kadam (Jira)]

Durga Kadam created ATLAS-3862:
--

 Summary: [UI] When added term with large name validation msgs are 
misaligned. PFA snaps
 Key: ATLAS-3862
 URL: https://issues.apache.org/jira/browse/ATLAS-3862
 Project: Atlas
  Issue Type: Sub-task
Reporter: Durga Kadam






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

Re: Review Request 72610: ATLAS-3850 : Regression, Terms are not getting displayed

[Pinal Shah]

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

(Updated June 23, 2020, 11:47 a.m.)


Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
Nixon Rodrigues, and Sarath Subramanian.


Changes
---

Update index field names for testcases


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


Repository: atlas


Description
---

During basic search, terms(meanings) in the entity response header is empty, 
because while fetching terms from the vertex edge, term label is wrong

**Solution: Removed "__" prefix from the term edge label while fetching.**

TO-DO: Find out reason or remove this line
GraphBackedSearchIndexer.initialize(){
 --> createEdgeLabel(management, Constants.TERM_ASSIGNMENT_LABEL);
}


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
 4a09b08a4 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 757fcb116 
  test-tools/src/main/resources/solr/core-template/solrconfig.xml ef74a0a45 


Diff: https://reviews.apache.org/r/72610/diff/3/

Changes: https://reviews.apache.org/r/72610/diff/2-3/


Testing
---

Precommit : 
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1971/console


Thanks,

Pinal Shah

[jira] [Created] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

[Durga Kadam (Jira)]

Durga Kadam created ATLAS-3861:
--

 Summary: [UI] When Entity added with existing BusinessMetadata 
Attribute shows misalignment
 Key: ATLAS-3861
 URL: https://issues.apache.org/jira/browse/ATLAS-3861
 Project: Atlas
  Issue Type: Bug
Reporter: Durga Kadam
 Attachments: while adding exisitng Business metadata to an entity 
shows misalignment .png

{color:#00}Steps to reproduce the bug::{color}
 # {color:#00}Create business metadata with any large attribute name {color}
 # {color:#00}Create/Update any entity with same BM attribute in 'Business 
Metadata' section{color}



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

[jira] [Updated] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3861:
---
Priority: Minor  (was: Major)

> [UI] When Entity added with existing BusinessMetadata Attribute shows 
> misalignment
> --
>
> Key: ATLAS-3861
> URL: https://issues.apache.org/jira/browse/ATLAS-3861
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: while adding exisitng Business metadata to an entity 
> shows misalignment .png
>
>
> {color:#00}Steps to reproduce the bug::{color}
>  # {color:#00}Create business metadata with any large attribute name 
> {color}
>  # {color:#00}Create/Update any entity with same BM attribute in 
> 'Business Metadata' section{color}



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

[jira] [Updated] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3857:
---
Priority: Minor  (was: Major)

> [UI] When deleted term same term twice shows 'Something went wrong' msg.
> 
>
> Key: ATLAS-3857
> URL: https://issues.apache.org/jira/browse/ATLAS-3857
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: delete term something went wrong issue.webm
>
>
> When deleted term, it does not get delete immediately when tried again to 
> delete the same term shows 'Something went wrong msg'. PFA Video
> *Expected ::* On first delete it should show loading sign and/or delete 
> button should get disabled
> *Actual::* It takes long to delete a term and as the delete button is enabled 
> user tried to delete it again. When deleted the same term again Shows 
> 'Something went wrong' msg.
>  Server Logs are as follows::
> 2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
> 1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
> to exception (StandardJanusGraph:808)
>  org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
> contention
>  at 
> org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
>  at 
> org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
>  at 
> org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
>  at 
> org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
>  at 
> org.janusgraph.graphdb.transaction.StandardJanusGraphTx.commit(StandardJanusGraphTx.java:1425)
>  at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.doCommit(JanusGraphBlueprintsGraph.java:297)
>  at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.commit(AbstractTransaction.java:104)
>  at 
> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.commit(AtlasJanusGraph.java:248)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommit(GraphTransactionInterceptor.java:157)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:152)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:91)
>  at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
>  at 
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$71fceabc.deleteTerm()
>  at 
> org.apache.atlas.web.rest.GlossaryREST.deleteGlossaryTerm(GlossaryREST.java:590)
>  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$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:167)



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

[jira] [Created] (ATLAS-3858) [UI] Misaligment happened in Glossaries when added term with large name

[Durga Kadam (Jira)]

Durga Kadam created ATLAS-3858:
--

 Summary: [UI] Misaligment happened in Glossaries when added term 
with large name
 Key: ATLAS-3858
 URL: https://issues.apache.org/jira/browse/ATLAS-3858
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Durga Kadam
 Attachments: embedded_tag_added_in_glossries.webm

Steps to reproduce:
 # {color:#00}Go to Glossaries and add term with this Name :: 
{color}{color:#00}SRC="data:image/svg+xml;base64,PHN2ZyB4bWxuczpzdmc9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
 MjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hs 
aW5rIiB2ZXJzaW9uPSIxLjAiIHg9IjAiIHk9IjAiIHdpZHRoPSIxOTQiIGhlaWdodD0iMjAw 
IiBpZD0ieHNzIj48c2NyaXB0IHR5cGU9InRleHQvZWNtYXNjcmlwdCI+YWxlcnQoIlh 
TUyIpOzwvc2NyaXB0Pjwvc3ZnPg==" type="image/svg+xml" 
AllowScriptAccess="always{color}
 # {color:#00}Save the Term {color}
 # {color:#00}Now check the aligment on the left hand panel{color}

*{color:#4c9aff}_NOTE- Issue is producible only on New UI. It works fine on Old 
UI._{color}*



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

[jira] [Updated] (ATLAS-3860) When added string in Business Metadata Attribute name and added type as any enum which is created with string, shows 'Something went wrong' msg

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3860:
---
Description: 
{color:#00}When added string in Business Metadata Attribute name and added 
type as any enum which is created with string, shows 'Something went wrong' 
msg{color}

{color:#00}Steps to reproduce the bug:{color}
 # {color:#00}Create enum with value set to any  string {color}
 # {color:#00}Create Business Metadata attribute{color}
 # {color:#00}While creating BusinessMeatdata attribute set name as string 
and in type select the created enum from dropdown list{color}
 # {color:#00}Click on Add button {color}
 # {color:#00}Shows 'Something went wrong msg'{color}

  was:
{color:#00}When added XSS string in Business Metadata Attribute name and 
added type as any enum which is created with XSS string, shows 'Something went 
wrong' msg{color}

{color:#00}Steps to reproduce the bug:{color}
 # {color:#00}Create enum with value set to any XSS string 
{color}
 # {color:#00}Create Business Metadata attribute{color}
 # {color:#00}While creating BusinessMeatdata attribute set name as XSS 
string and in type select the created enum from dropdown list{color}
 # {color:#00}Click on Add button {color}
 # {color:#00}Shows 'Something went wrong msg'{color}


> When added  string in Business Metadata Attribute name and added type as any 
> enum which is created with string, shows 'Something went wrong' msg
> 
>
> Key: ATLAS-3860
> URL: https://issues.apache.org/jira/browse/ATLAS-3860
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: Something went wrong while adding enum to attribues.mkv
>
>
> {color:#00}When added string in Business Metadata Attribute name and 
> added type as any enum which is created with string, shows 'Something went 
> wrong' msg{color}
> {color:#00}Steps to reproduce the bug:{color}
>  # {color:#00}Create enum with value set to any  string {color}
>  # {color:#00}Create Business Metadata attribute{color}
>  # {color:#00}While creating BusinessMeatdata attribute set name as 
> string and in type select the created enum from dropdown list{color}
>  # {color:#00}Click on Add button {color}
>  # {color:#00}Shows 'Something went wrong msg'{color}



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

Re: Review Request 72610: ATLAS-3850 : Regression, Terms are not getting displayed

[Pinal Shah]

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

(Updated June 23, 2020, 11:49 a.m.)


Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
Nixon Rodrigues, and Sarath Subramanian.


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


Repository: atlas


Description (updated)
---

During basic search, terms(meanings) in the entity response header is empty, 
because while fetching terms from the vertex edge, term label is wrong

**Solution: Removed "__" prefix from the term edge label while fetching.**

TO-DO: Find out reason or remove this line
GraphBackedSearchIndexer.initialize(){
 --> createEdgeLabel(management, Constants.TERM_ASSIGNMENT_LABEL);
}

Added below index field names for FreetextSearchProcessor
"Referenceable.qualifiedName" -> "3eh1_t"
"__labels" -> "yrp_t"
"__propagatedClassificationNames" -> "m4l_t"
"__classificationNames" -> "kjp_t"
"__classificationsText" -> "iyt_t"
"__typeName" -> "cn9_t"
"__customAttributes" -> "x6t_t"
"__state" -> "hdx_t"
"Asset.__s_name" -> "3ksl_s"
"Asset.__s_owner" -> "3qbp_s"
"Asset.__s_displayName" -> "3mdh_s"
"Asset.__s_userDescription" -> "3oqt_s"
"Asset.description" -> "3nyd_t"
"hive_db.clusterName" -> "7uv9_t"
"hive_table.tableType" -> "7ldx_t"


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
 4a09b08a4 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 757fcb116 
  test-tools/src/main/resources/solr/core-template/solrconfig.xml ef74a0a45 


Diff: https://reviews.apache.org/r/72610/diff/3/


Testing
---

Precommit : 
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1971/console


Thanks,

Pinal Shah

[jira] [Created] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg

[Durga Kadam (Jira)]

Durga Kadam created ATLAS-3857:
--

 Summary: [UI] When deleted term same term twice shows 'Something 
went wrong' msg
 Key: ATLAS-3857
 URL: https://issues.apache.org/jira/browse/ATLAS-3857
 Project: Atlas
  Issue Type: Bug
Reporter: Durga Kadam


When deleted term, it does not get delete immediately when tried again to 
delete shows 'Something went wrong msg'



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

[jira] [Created] (ATLAS-3859) [UI] In edit entity window shows calender with 'Invalid date'

[Durga Kadam (Jira)]

Durga Kadam created ATLAS-3859:
--

 Summary: [UI] In edit entity window shows calender with 'Invalid 
date'
 Key: ATLAS-3859
 URL: https://issues.apache.org/jira/browse/ATLAS-3859
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Durga Kadam
 Attachments: shows Invalid date with 'NaN'.webm

Steps to reproduce::
 # {color:#00}Open entity in edit mode{color}
 # {color:#00}Click on toggle 'Required' set to ALL {color}
 # {color:#00}For 'Created Time' shows 'Invalid Date' {color}
 # {color:#00}When Opened calender shows 'NaN' for all the dates{color}

{color:#00}Expected: Calender should be available with dates to select the 
required date
{color}

{color:#00}Actual: Shows NaN all over the calender{color}



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

[jira] [Updated] (ATLAS-3860) When added string in Business Metadata Attribute name and added type as any enum which is created with string, shows 'Something went wrong' msg

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3860:
---
Summary: When added  string in Business Metadata Attribute name and added 
type as any enum which is created with string, shows 'Something went wrong' msg 
 (was: When added  string in Business Metadata Attribute name and added type as 
any enum which is created with XSS string, shows 'Something went wrong' msg)

> When added  string in Business Metadata Attribute name and added type as any 
> enum which is created with string, shows 'Something went wrong' msg
> 
>
> Key: ATLAS-3860
> URL: https://issues.apache.org/jira/browse/ATLAS-3860
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: Something went wrong while adding enum to attribues.mkv
>
>
> {color:#00}When added XSS string in Business Metadata Attribute name and 
> added type as any enum which is created with XSS string, shows 'Something 
> went wrong' msg{color}
> {color:#00}Steps to reproduce the bug:{color}
>  # {color:#00}Create enum with value set to any XSS string 
> {color}
>  # {color:#00}Create Business Metadata attribute{color}
>  # {color:#00}While creating BusinessMeatdata attribute set name as XSS 
> string and in type select the created enum from dropdown list{color}
>  # {color:#00}Click on Add button {color}
>  # {color:#00}Shows 'Something went wrong msg'{color}



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

[jira] [Updated] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3857:
---
Summary: [UI] When deleted term same term twice shows 'Something went 
wrong' msg.  (was: [UI] When deleted term same term twice shows 'Something went 
wrong' msg)

> [UI] When deleted term same term twice shows 'Something went wrong' msg.
> 
>
> Key: ATLAS-3857
> URL: https://issues.apache.org/jira/browse/ATLAS-3857
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Major
> Attachments: delete term something went wrong issue.webm
>
>
> When deleted term, it does not get delete immediately when tried again to 
> delete shows 'Something went wrong msg'
> Expected :: On first delete it should show loading sign and/or delete button 
> should get disabled
> Actual:: It takes long to delete a term and as the delete button is enabled 
> user tried to delete it again. When deleted the same term again Shows 
> 'Something went wrong' msg.
>  
> Server Logs are::
> 2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
> 1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
> to exception (StandardJanusGraph:808)
> org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
> contention
>  at 
> org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
>  at 
> org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
>  at 
> org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
>  at 
> org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
>  at 
> org.janusgraph.graphdb.transaction.StandardJanusGraphTx.commit(StandardJanusGraphTx.java:1425)
>  at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.doCommit(JanusGraphBlueprintsGraph.java:297)
>  at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.commit(AbstractTransaction.java:104)
>  at 
> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.commit(AtlasJanusGraph.java:248)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommit(GraphTransactionInterceptor.java:157)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:152)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:91)
>  at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
>  at 
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$71fceabc.deleteTerm()
>  at 
> org.apache.atlas.web.rest.GlossaryREST.deleteGlossaryTerm(GlossaryREST.java:590)
>  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$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:167)



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

[jira] [Created] (ATLAS-3860) [UI] When added XSS string in Business Metadata Attribute name and added type as any enum which is created with XSS string, shows 'Something went wrong' msg

[Durga Kadam (Jira)]

Durga Kadam created ATLAS-3860:
--

 Summary: [UI] When added XSS string in Business Metadata Attribute 
name and added type as any enum which is created with XSS string, shows 
'Something went wrong' msg
 Key: ATLAS-3860
 URL: https://issues.apache.org/jira/browse/ATLAS-3860
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Durga Kadam
 Attachments: Something went wrong while adding enum to attribues.mkv

{color:#00}When added XSS string in Business Metadata Attribute name and 
added type as any enum which is created with XSS string, shows 'Something went 
wrong' msg{color}

{color:#00}Steps to reproduce the bug:{color}
 # {color:#00}Create enum with value set to any XSS string 
{color}
 # {color:#00}Create Business Metadata attribute{color}
 # {color:#00}While creating BusinessMeatdata attribute set name as XSS 
string and in type select the created enum from dropdown list{color}
 # {color:#00}Click on Add button {color}
 # {color:#00}Shows 'Something went wrong msg'{color}



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

[jira] [Updated] (ATLAS-3860) When added XSS string in Business Metadata Attribute name and added type as any enum which is created with XSS string, shows 'Something went wrong' msg

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3860:
---
Summary: When added XSS string in Business Metadata Attribute name and 
added type as any enum which is created with XSS string, shows 'Something went 
wrong' msg  (was: [UI] When added XSS string in Business Metadata Attribute 
name and added type as any enum which is created with XSS string, shows 
'Something went wrong' msg)

> When added XSS string in Business Metadata Attribute name and added type as 
> any enum which is created with XSS string, shows 'Something went wrong' msg
> ---
>
> Key: ATLAS-3860
> URL: https://issues.apache.org/jira/browse/ATLAS-3860
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: Something went wrong while adding enum to attribues.mkv
>
>
> {color:#00}When added XSS string in Business Metadata Attribute name and 
> added type as any enum which is created with XSS string, shows 'Something 
> went wrong' msg{color}
> {color:#00}Steps to reproduce the bug:{color}
>  # {color:#00}Create enum with value set to any XSS string 
> {color}
>  # {color:#00}Create Business Metadata attribute{color}
>  # {color:#00}While creating BusinessMeatdata attribute set name as XSS 
> string and in type select the created enum from dropdown list{color}
>  # {color:#00}Click on Add button {color}
>  # {color:#00}Shows 'Something went wrong msg'{color}



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

[jira] [Updated] (ATLAS-3860) When added string in Business Metadata Attribute name and added type as any enum which is created with XSS string, shows 'Something went wrong' msg

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3860:
---
Summary: When added  string in Business Metadata Attribute name and added 
type as any enum which is created with XSS string, shows 'Something went wrong' 
msg  (was: When added XSS string in Business Metadata Attribute name and added 
type as any enum which is created with XSS string, shows 'Something went wrong' 
msg)

> When added  string in Business Metadata Attribute name and added type as any 
> enum which is created with XSS string, shows 'Something went wrong' msg
> 
>
> Key: ATLAS-3860
> URL: https://issues.apache.org/jira/browse/ATLAS-3860
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: Something went wrong while adding enum to attribues.mkv
>
>
> {color:#00}When added XSS string in Business Metadata Attribute name and 
> added type as any enum which is created with XSS string, shows 'Something 
> went wrong' msg{color}
> {color:#00}Steps to reproduce the bug:{color}
>  # {color:#00}Create enum with value set to any XSS string 
> {color}
>  # {color:#00}Create Business Metadata attribute{color}
>  # {color:#00}While creating BusinessMeatdata attribute set name as XSS 
> string and in type select the created enum from dropdown list{color}
>  # {color:#00}Click on Add button {color}
>  # {color:#00}Shows 'Something went wrong msg'{color}



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

[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.

[Nixon Rodrigues (Jira)]

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

Nixon Rodrigues updated ATLAS-3853:
---
Description: 
 

*_The issue :_* 

The enumValue which we assigned  ">"  has double quotes in it.the 
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]{'

{', '}

', '"', '\u001e'}; into it.

*_How to reproduce it ? Steps to reproduce :_*

Step 1 : Create an enum e.g enumXSS.

Step 2 : create a classification with some attribute of type enumXSS.

Step 3 : Assign a value for this attribute with  ">"Now this will result into an error with 
500 saying "Something went wrong"

*Approach for resolving this :* 

As the janusgraph has this check for special characters and our enumValue has 
that double quotes in it it throws an illelagalArgumentException.

Now at Atlas end we are not handling the unexpected exception so we just have 
to catch the Exception and throw it with proper error code and error-message 
which helps user to  understand the issue properly.And for that i have provided 
the patch on RR.

 

 *Stack-trace:-*
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 
__type.edge.classitest.">
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at 
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at 
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.makeEdgeLabel(StandardJanusGraphTx.java:1052)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getOrCreateEdgeLabel(StandardJanusGraphTx.java:1038)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:167)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:37)
at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.addEdge(AtlasJanusGraph.java:147)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.addEdge(AtlasTypeDefGraphStoreV2.java:395)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.getOrCreateEdge(AtlasTypeDefGraphStoreV2.java:387)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.addReferencesForAttribute(AtlasStructDefStoreV2.java:523)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.updateVertexAddReferences(AtlasStructDefStoreV2.java:471)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateVertexAddReferences(AtlasClassificationDefStoreV2.java:338)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateByGuid(AtlasClassificationDefStoreV2.java:254)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:183)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:48)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateGraphStore(AtlasTypeDefGraphStore.java:1029)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateTypesDef(AtlasTypeDefGraphStore.java:481)
{noformat}
 

  was:
 

_The issue :_ 

The enumValue which we assigned  ">"  has double quotes in it.the 
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]{'

{', '}

', '"', '\u001e'}; into it.

_How to reproduce it ? Steps to reproduce :_

Step 1 : Create an enum e.g enumXSS.

Step 2 : create a classification with some attribute of type enumXSS.

Step 3 : Assign a value for this attribute with  ">"Now this will result into an error with 
500 saying "Something went wrong"

_Approach for resolving this :_ 

As the janusgraph has this check for special characters and our enumValue has 
that double quotes in it it throws an illelagalArgumentException.

Now at Atlas end we are not handling the unexpected exception so we just have 
to catch the Exception and throw it with proper error code and error-message 
which helps user to  understand the issue properly.And for that i have provided 
the patch on RR.

 

 Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 

[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.

[Mayank Jain (Jira)]

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

Mayank Jain updated ATLAS-3853:
---
Description: 
 

_The issue :_ 

The enumValue which we assigned  ">"  has double quotes in it.the 
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]{'

{', '}

', '"', '\u001e'}; into it.

_How to reproduce it ? Steps to reproduce :_

Step 1 : Create an enum e.g enumXSS.

Step 2 : create a classification with some attribute of type enumXSS.

Step 3 : Assign a value for this attribute with  ">"Now this will result into an error with 
500 saying "Something went wrong"

_Approach for resolving this :_ 

As the janusgraph has this check for special characters and our enumValue has 
that double quotes in it it throws an illelagalArgumentException.

Now at Atlas end we are not handling the unexpected exception so we just have 
to catch the Exception and throw it with proper error code and error-message 
which helps user to  understand the issue properly.And for that i have provided 
the patch on RR.

 

 Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 
__type.edge.classitest.">
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at 
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at 
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.makeEdgeLabel(StandardJanusGraphTx.java:1052)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getOrCreateEdgeLabel(StandardJanusGraphTx.java:1038)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:167)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:37)
at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.addEdge(AtlasJanusGraph.java:147)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.addEdge(AtlasTypeDefGraphStoreV2.java:395)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.getOrCreateEdge(AtlasTypeDefGraphStoreV2.java:387)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.addReferencesForAttribute(AtlasStructDefStoreV2.java:523)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.updateVertexAddReferences(AtlasStructDefStoreV2.java:471)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateVertexAddReferences(AtlasClassificationDefStoreV2.java:338)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateByGuid(AtlasClassificationDefStoreV2.java:254)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:183)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:48)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateGraphStore(AtlasTypeDefGraphStore.java:1029)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateTypesDef(AtlasTypeDefGraphStore.java:481)
{noformat}
 

  was:
 

The issue : 

The enumValue which we assigned  ">"  has double quotes in it.the 
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]\{'{', 
'}', '"', '\u001e'}; into it.


How to reproduce it ? Steps to reproduce :

Step 1 : Create an enum e.g enumXSS.Step 2 : create a classification with some 
attribute of type enumXSS.Step 3 : Assign a value for this attribute with  
">"Now this will result into an 
error with 500 saying "Something went wrong"

Approach for resolving this : 

As the janusgraph has this check for special characters and our enumValue has 
that double quotes in it it throws an illelagalArgumentException.

Now at Atlas end we are not handling the unexpected exception so we just have 
to catch the Exception and throw it with proper error code and error-message 
which helps user to  understand the issue properly.And for that i have provided 
the patch on RR.

 

 Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 
__type.edge.classitest.">
   

[jira] [Updated] (ATLAS-3855) Bulk entity tag association and bulk api enhancement

[chaitali borole (Jira)]

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

chaitali borole updated ATLAS-3855:
---
Description: 
API : /api/atlas/v2/entity/bulk/classification

Body :
{code:java}
{"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
 {code}
when user doesn't have authorisation on either of guid1 or guid2 , the bulk 
entity call fails with 403. 

bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its 
guids.
This bulk api fails with 403 if some guids belong to entities on which user is 
*unauthorized* and other guids belong to entities on which user is *authorized*.

> Bulk entity tag association and bulk api enhancement
> 
>
> Key: ATLAS-3855
> URL: https://issues.apache.org/jira/browse/ATLAS-3855
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> API : /api/atlas/v2/entity/bulk/classification
> Body :
> {code:java}
> {"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
>  {code}
> when user doesn't have authorisation on either of guid1 or guid2 , the bulk 
> entity call fails with 403. 
> bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its 
> guids.
> This bulk api fails with 403 if some guids belong to entities on which user 
> is *unauthorized* and other guids belong to entities on which user is 
> *authorized*.



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

[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.

[Mayank Jain (Jira)]

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

Mayank Jain updated ATLAS-3853:
---
Description: 
 

The issue : 

The enumValue which we assigned  ">"  has double quotes in it.the 
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]\{'{', 
'}', '"', '\u001e'}; into it.


How to reproduce it ? Steps to reproduce :

Step 1 : Create an enum e.g enumXSS.Step 2 : create a classification with some 
attribute of type enumXSS.Step 3 : Assign a value for this attribute with  
">"Now this will result into an 
error with 500 saying "Something went wrong"

Approach for resolving this : 

As the janusgraph has this check for special characters and our enumValue has 
that double quotes in it it throws an illelagalArgumentException.

Now at Atlas end we are not handling the unexpected exception so we just have 
to catch the Exception and throw it with proper error code and error-message 
which helps user to  understand the issue properly.And for that i have provided 
the patch on RR.

 

 Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 
__type.edge.classitest.">
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at 
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at 
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.makeEdgeLabel(StandardJanusGraphTx.java:1052)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getOrCreateEdgeLabel(StandardJanusGraphTx.java:1038)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:167)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:37)
at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.addEdge(AtlasJanusGraph.java:147)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.addEdge(AtlasTypeDefGraphStoreV2.java:395)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.getOrCreateEdge(AtlasTypeDefGraphStoreV2.java:387)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.addReferencesForAttribute(AtlasStructDefStoreV2.java:523)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.updateVertexAddReferences(AtlasStructDefStoreV2.java:471)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateVertexAddReferences(AtlasClassificationDefStoreV2.java:338)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateByGuid(AtlasClassificationDefStoreV2.java:254)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:183)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:48)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateGraphStore(AtlasTypeDefGraphStore.java:1029)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateTypesDef(AtlasTypeDefGraphStore.java:481)
{noformat}
 

  was:
I had created an enum with some value in it, and a classification 
ClassificationTest1, now while i was adding an attribute to my 
ClassificationTest1 the value i assigne the enumValue was  

">

and instead of throwing some kind of error message the application threw 
"Something went wrong"  with 500 error code.

The end user in such scenario won't be able to identify what exactly went wrong.

 Stacktrace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 
__type.edge.classitest.">
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at 
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at 
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at 

[GitHub] [atlas] v-odier-heetch opened a new pull request #102: Tdh 145

[GitBox]

v-odier-heetch opened a new pull request #102:
URL: https://github.com/apache/atlas/pull/102


   hack mode



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Review Request 72610: ATLAS-3850 : Regression, Terms are not getting displayed

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On June 23, 2020, 11:49 a.m., Pinal Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72610/
> ---
> 
> (Updated June 23, 2020, 11:49 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
> Nixon Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3850
> https://issues.apache.org/jira/browse/ATLAS-3850
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> During basic search, terms(meanings) in the entity response header is empty, 
> because while fetching terms from the vertex edge, term label is wrong
> 
> **Solution: Removed "__" prefix from the term edge label while fetching.**
> 
> TO-DO: Find out reason or remove this line
> GraphBackedSearchIndexer.initialize(){
>  --> createEdgeLabel(management, Constants.TERM_ASSIGNMENT_LABEL);
> }
> 
> Added below index field names for FreetextSearchProcessor
> "Referenceable.qualifiedName" -> "3eh1_t"
> "__labels" -> "yrp_t"
> "__propagatedClassificationNames" -> "m4l_t"
> "__classificationNames" -> "kjp_t"
> "__classificationsText" -> "iyt_t"
> "__typeName" -> "cn9_t"
> "__customAttributes" -> "x6t_t"
> "__state" -> "hdx_t"
> "Asset.__s_name" -> "3ksl_s"
> "Asset.__s_owner" -> "3qbp_s"
> "Asset.__s_displayName" -> "3mdh_s"
> "Asset.__s_userDescription" -> "3oqt_s"
> "Asset.description" -> "3nyd_t"
> "hive_db.clusterName" -> "7uv9_t"
> "hive_table.tableType" -> "7ldx_t"
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  4a09b08a4 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
>  757fcb116 
>   test-tools/src/main/resources/solr/core-template/solrconfig.xml ef74a0a45 
> 
> 
> Diff: https://reviews.apache.org/r/72610/diff/3/
> 
> 
> Testing
> ---
> 
> Precommit : https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1973
> 
> 
> Thanks,
> 
> Pinal Shah
> 
>

[GitHub] [atlas] v-odier-heetch closed pull request #102: Tdh 145

[GitBox]

v-odier-heetch closed pull request #102:
URL: https://github.com/apache/atlas/pull/102


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [atlas] v-odier-heetch commented on pull request #102: Tdh 145

[GitBox]

v-odier-heetch commented on pull request #102:
URL: https://github.com/apache/atlas/pull/102#issuecomment-648230968


   this is a fail



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [atlas] v-odier-heetch commented on pull request #102: Tdh 145

[GitBox]

v-odier-heetch commented on pull request #102:
URL: https://github.com/apache/atlas/pull/102#issuecomment-648229619


   env var DRY="true" pour avoir les logs direct sur stdout sans tail puis 
bin/startAtlas



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Assigned] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

[Keval Bhatt (Jira)]

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

Keval Bhatt reassigned ATLAS-3861:
--

Assignee: Keval Bhatt

> [UI] When Entity added with existing BusinessMetadata Attribute shows 
> misalignment
> --
>
> Key: ATLAS-3861
> URL: https://issues.apache.org/jira/browse/ATLAS-3861
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: while adding exisitng Business metadata to an entity 
> shows misalignment .png
>
>
> {color:#00}Steps to reproduce the bug::{color}
>  # {color:#00}Create business metadata with any large attribute name 
> {color}
>  # {color:#00}Create/Update any entity with same BM attribute in 
> 'Business Metadata' section{color}



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

[jira] [Assigned] (ATLAS-3862) [UI] When added term with large name validation msgs are misaligned. PFA snaps

[Keval Bhatt (Jira)]

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

Keval Bhatt reassigned ATLAS-3862:
--

Assignee: Keval Bhatt

> [UI] When added term with large name validation msgs are misaligned. PFA snaps
> --
>
> Key: ATLAS-3862
> URL: https://issues.apache.org/jira/browse/ATLAS-3862
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: 
> added_glossary_with_embedded_tag_success_msg_misalignment.png, 
> deleted_term_with_embedded_tag_validation_msg_misalignment.png
>
>




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

[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

[Vasanth kumar RJ (Jira)]

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

Vasanth kumar RJ commented on ATLAS-3852:
-

[~mad...@apache.org] [~sarath] Please review this ticket.

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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

[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

[Madhan Neethiraj (Jira)]

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

Madhan Neethiraj commented on ATLAS-3852:
-

[~vasanthkumar] - can you please add more details, with necessary data to 
reproduce the issue?

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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

[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

[Vasanth kumar RJ (Jira)]

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

Vasanth kumar RJ commented on ATLAS-3852:
-

[~madhan] - Currently in Entity Bulk POST API, every entity referenced ( Table 
entity -> DB reference) using guid or unique attribute which is created 
already. We cannot create DB and Table Entity with referenced in same bulk 
request.

Fix to support bulk create DB entity and table entity reference to DB in same 
request.

Use case to support creation new DB entity, its new Table entities and new 
Column Entities in a bulk request.

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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

[jira] [Assigned] (ATLAS-3858) [UI] Misaligment happened in Glossaries when added term with large name

[Keval Bhatt (Jira)]

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

Keval Bhatt reassigned ATLAS-3858:
--

Assignee: Keval Bhatt

> [UI] Misaligment happened in Glossaries when added term with large name
> ---
>
> Key: ATLAS-3858
> URL: https://issues.apache.org/jira/browse/ATLAS-3858
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: embedded_tag_added_in_glossries.webm
>
>
> Steps to reproduce:
>  # {color:#00}Go to Glossaries and add term with this Name :: 
> {color}{color:#00}SRC="data:image/svg+xml;base64,PHN2ZyB4bWxuczpzdmc9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
>  MjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hs 
> aW5rIiB2ZXJzaW9uPSIxLjAiIHg9IjAiIHk9IjAiIHdpZHRoPSIxOTQiIGhlaWdodD0iMjAw 
> IiBpZD0ieHNzIj48c2NyaXB0IHR5cGU9InRleHQvZWNtYXNjcmlwdCI+YWxlcnQoIlh 
> TUyIpOzwvc2NyaXB0Pjwvc3ZnPg==" type="image/svg+xml" 
> AllowScriptAccess="always{color}
>  # {color:#00}Save the Term {color}
>  # {color:#00}Now check the aligment on the left hand panel{color}
> *{color:#4c9aff}_NOTE- Issue is producible only on New UI. It works fine on 
> Old UI._{color}*



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

[jira] [Assigned] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.

[Keval Bhatt (Jira)]

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

Keval Bhatt reassigned ATLAS-3857:
--

Assignee: Keval Bhatt

> [UI] When deleted term same term twice shows 'Something went wrong' msg.
> 
>
> Key: ATLAS-3857
> URL: https://issues.apache.org/jira/browse/ATLAS-3857
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: delete term something went wrong issue.webm
>
>
> When deleted term, it does not get delete immediately when tried again to 
> delete the same term shows 'Something went wrong msg'. PFA Video
> *Expected ::* On first delete it should show loading sign and/or delete 
> button should get disabled
> *Actual::* It takes long to delete a term and as the delete button is enabled 
> user tried to delete it again. When deleted the same term again Shows 
> 'Something went wrong' msg.
>  Server Logs are as follows::
> 2020-06-23 12:12:44,315 ERROR - [pool-2-thread-10 - 
> 1a7a6991-e5c3-4519-9b5b-e0a926abd4be:] ~ Could not commit transaction [7] due 
> to exception (StandardJanusGraph:808)
>  org.janusgraph.diskstorage.locking.PermanentLockingException: Local lock 
> contention
>  at 
> org.janusgraph.diskstorage.locking.AbstractLocker.writeLock(AbstractLocker.java:327)
>  at 
> org.janusgraph.diskstorage.locking.consistentkey.ExpectedValueCheckingStore.acquireLock(ExpectedValueCheckingStore.java:103)
>  at 
> org.janusgraph.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:51)
>  at 
> org.janusgraph.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:236)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.prepareCommit(StandardJanusGraph.java:551)
>  at 
> org.janusgraph.graphdb.database.StandardJanusGraph.commit(StandardJanusGraph.java:731)
>  at 
> org.janusgraph.graphdb.transaction.StandardJanusGraphTx.commit(StandardJanusGraphTx.java:1425)
>  at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.doCommit(JanusGraphBlueprintsGraph.java:297)
>  at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.commit(AbstractTransaction.java:104)
>  at 
> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.commit(AtlasJanusGraph.java:248)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommit(GraphTransactionInterceptor.java:157)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:152)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:91)
>  at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
>  at 
> org.apache.atlas.glossary.GlossaryService$$EnhancerBySpringCGLIB$$71fceabc.deleteTerm()
>  at 
> org.apache.atlas.web.rest.GlossaryREST.deleteGlossaryTerm(GlossaryREST.java:590)
>  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$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:167)



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

Re: Review Request 72614: ATLAS-3856 Create new entity types for Apache Ozone

[Madhan Neethiraj]

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




addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 5 (patched)


If each instance of this struct represent one location, consider renaming 
keyLocations => keyLocation.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 88 (patched)


Consider using an enum for storageType - if the list of values is 
well-known in Ozone.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 96 (patched)


versioning => supportsVersioning/versioningEnabled



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 137 (patched)


Consider using an enum for replicationType - if the list of values is 
well-known in Ozone.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 169 (patched)


Given Atlas may not track all updates to Ozone objects, I suggest to not 
have 'modificationTime' attribute in the model.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 181 (patched)


ozone_volume_ozone_bucket => ozone_volume_buckets



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 185 (patched)


I suggest to not specify explicit 'relationshipLabel' here; this is 
necessary only for earlier version entity-types that didn't use relationships.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 188 (patched)


bucket => buckets



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 201 (patched)


ozone_bucket_ozone_key => ozone_bucket_keys



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 205 (patched)


I suggest to not specify explicit 'relationshipLabel' here; this is 
necessary only for earlier version entity-types that didn't use relationships.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 208 (patched)


key => keys


- Madhan Neethiraj


On June 23, 2020, 5:45 a.m., Nikhil Bonte wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72614/
> ---
> 
> (Updated June 23, 2020, 5:45 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, madhan, Nixon 
> Rodrigues, Sarath Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3856
> https://issues.apache.org/jira/browse/ATLAS-3856
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add following ozone typeDefs to Atlas models
> 
> Ozone volume
> Ozone bucket
> Ozone key
> 
> 
> Diffs
> -
> 
>   addons/models/3000-Cloud/3050-ozone-typedefs.json PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/72614/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Nikhil Bonte
> 
>

[jira] [Assigned] (ATLAS-3859) [UI] In edit entity window shows calender with 'Invalid date'

[Keval Bhatt (Jira)]

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

Keval Bhatt reassigned ATLAS-3859:
--

Assignee: Keval Bhatt

> [UI] In edit entity window shows calender with 'Invalid date'
> -
>
> Key: ATLAS-3859
> URL: https://issues.apache.org/jira/browse/ATLAS-3859
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: shows Invalid date with 'NaN'.webm
>
>
> Steps to reproduce::
>  # {color:#00}Open entity in edit mode{color}
>  # {color:#00}Click on toggle 'Required' set to ALL {color}
>  # {color:#00}For 'Created Time' shows 'Invalid Date' {color}
>  # {color:#00}When Opened calender shows 'NaN' for all the dates{color}
> {color:#00}Expected: Calender should be available with dates to select 
> the required date
> {color}
> {color:#00}Actual: Shows NaN all over the calender{color}



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

[jira] [Assigned] (ATLAS-3860) When added string in Business Metadata Attribute name and added type as any enum which is created with string, shows 'Something went wrong' msg

[Keval Bhatt (Jira)]

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

Keval Bhatt reassigned ATLAS-3860:
--

Assignee: Keval Bhatt

> When added  string in Business Metadata Attribute name and added type as any 
> enum which is created with string, shows 'Something went wrong' msg
> 
>
> Key: ATLAS-3860
> URL: https://issues.apache.org/jira/browse/ATLAS-3860
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: Something went wrong while adding enum to attribues.mkv
>
>
> {color:#00}When added string in Business Metadata Attribute name and 
> added type as any enum which is created with string, shows 'Something went 
> wrong' msg{color}
> {color:#00}Steps to reproduce the bug:{color}
>  # {color:#00}Create enum with value set to any  string {color}
>  # {color:#00}Create Business Metadata attribute{color}
>  # {color:#00}While creating BusinessMeatdata attribute set name as 
> string and in type select the created enum from dropdown list{color}
>  # {color:#00}Click on Add button {color}
>  # {color:#00}Shows 'Something went wrong msg'{color}



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

[jira] [Commented] (ATLAS-3850) Regression, Terms are not getting displayed

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3850:


Commit 992b8b47cc332efe71f82c5ecbbee94d3e2774e5 in atlas's branch 
refs/heads/master from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=992b8b4 ]

ATLAS-3850: regression - search results don't include glossary-term associations

Signed-off-by: Madhan Neethiraj 


> Regression, Terms are not getting displayed
> ---
>
> Key: ATLAS-3850
> URL: https://issues.apache.org/jira/browse/ATLAS-3850
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> For the entity E1 , if term T1@G1 is associated,
> then while searching entity E1, Term is not displayed in the column of the 
> basic search panel
> "meanings":  in the response is empty



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

[jira] [Commented] (ATLAS-3850) Regression, Terms are not getting displayed

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3850:


Commit 9e328ed31d928214e25915d10425dd375af1 in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9e328ed ]

ATLAS-3850: regression - search results don't include glossary-term associations

Signed-off-by: Madhan Neethiraj 
(cherry picked from commit 992b8b47cc332efe71f82c5ecbbee94d3e2774e5)


> Regression, Terms are not getting displayed
> ---
>
> Key: ATLAS-3850
> URL: https://issues.apache.org/jira/browse/ATLAS-3850
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> For the entity E1 , if term T1@G1 is associated,
> then while searching entity E1, Term is not displayed in the column of the 
> basic search panel
> "meanings":  in the response is empty



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

[jira] [Resolved] (ATLAS-3850) Regression, Terms are not getting displayed

[Madhan Neethiraj (Jira)]

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

Madhan Neethiraj resolved ATLAS-3850.
-
Fix Version/s: 3.0.0
   2.1.0
   Resolution: Fixed

> Regression, Terms are not getting displayed
> ---
>
> Key: ATLAS-3850
> URL: https://issues.apache.org/jira/browse/ATLAS-3850
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> For the entity E1 , if term T1@G1 is associated,
> then while searching entity E1, Term is not displayed in the column of the 
> basic search panel
> "meanings":  in the response is empty



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

Re: Review Request 72614: ATLAS-3856 Create new entity types for Apache Ozone

[Sarath Subramanian]

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




addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 6 (patched)


"Atlas Type representing the locations for key" => "location information 
about Ozone key"



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 15 (patched)


"isOptional" is set to false for all attributes of "keyLocations". Can 
there be cases where you don't have all the information and only some.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 22 (patched)


consider setting "isIndexable" to true for all string, int and date type 
attributes. This will enable searching on this attributes using basic search.



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 28 (patched)


does "length" type needs to be of string type?



addons/models/3000-Cloud/3050-ozone-typedefs.json
Lines 49 (patched)


ozone => Ozone


- Sarath Subramanian


On June 22, 2020, 10:45 p.m., Nikhil Bonte wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72614/
> ---
> 
> (Updated June 22, 2020, 10:45 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, madhan, Nixon 
> Rodrigues, Sarath Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3856
> https://issues.apache.org/jira/browse/ATLAS-3856
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add following ozone typeDefs to Atlas models
> 
> Ozone volume
> Ozone bucket
> Ozone key
> 
> 
> Diffs
> -
> 
>   addons/models/3000-Cloud/3050-ozone-typedefs.json PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/72614/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Nikhil Bonte
> 
>