[jira] [Commented] (ATLAS-3992) UI: Upgrade to JQuery 3.5.1

2020-10-21 Thread Durga Kadam (Jira)


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

Durga Kadam commented on ATLAS-3992:


+1

> UI: Upgrade to JQuery 3.5.1
> ---
>
> Key: ATLAS-3992
> URL: https://issues.apache.org/jira/browse/ATLAS-3992
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3992.patch
>
>




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


[jira] [Created] (ATLAS-3990) UI: When user clicks to view hive-table details, shown some wrong tabs

2020-10-13 Thread Durga Kadam (Jira)
Durga Kadam created ATLAS-3990:
--

 Summary: UI: When user clicks to view hive-table details, shown 
some wrong tabs
 Key: ATLAS-3990
 URL: https://issues.apache.org/jira/browse/ATLAS-3990
 Project: Atlas
  Issue Type: Bug
Reporter: Durga Kadam
 Attachments: wrong_tabs_showing_on_clicks.mkv

Steps to reproduce::
 # Have a hive_db with at least one table
 # Click on 'Tables' tab
 # Click on one of the tables listed in the tab
 # The page renders the table details, including addition of 'Schema' tab
 # However, 'Tables' tab is still visible; this tab needs to be hidden
 # Also, on clicking the db link in Properties page of hive_table, 'Schema' tab 
is still visible. This should be hidden

PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv



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


[jira] [Commented] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work

2020-10-09 Thread Durga Kadam (Jira)


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

Durga Kadam commented on ATLAS-3978:


+1

> In Administration, Audits filter for 'OR' condition does not work
> -
>
> Key: ATLAS-3978
> URL: https://issues.apache.org/jira/browse/ATLAS-3978
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3978.patch, OR condition not working.mkv
>
>
> Description::
> When user uses OR condition it does not apply on filter, results are listed 
> with AND condition. PFA evidence file [OR condition not working.mkv]
> Steps to regenerate::
>  # Go to Administration- Audits
>  # Select the OR condition filter
>  # Check the console for response
>  # Results are listed with 'AND' operator instead of 'OR'



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


[jira] [Commented] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.

2020-10-08 Thread Durga Kadam (Jira)


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

Durga Kadam commented on ATLAS-3979:


+1

> Beta UI : Removing one of the filters with an attribute name removes all of 
> the filters with that attribute name.
> -
>
> Key: ATLAS-3979
> URL: https://issues.apache.org/jira/browse/ATLAS-3979
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3979.patch
>
>
> Create a basic search with filters:
> typename = _ALL_ENTITY_TYPES
> filters:
> _classificationNames = tag1 and
> _classificationNames = tag2 and
> _createdBy = hive
> Fire Search.
> From UI , remove "_classificationNames = tag1" filter .
> This removes "_classificationNames = tag2" filter too since the attribute 
> name _classificationNames is same.
> Other attribute _createdBy is intact.



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


[jira] [Commented] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger

2020-10-08 Thread Durga Kadam (Jira)


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

Durga Kadam commented on ATLAS-3981:


+1

> UI: Create Entity button is shown for a user without create entity permission 
> in ranger
> ---
>
> Key: ATLAS-3981
> URL: https://issues.apache.org/jira/browse/ATLAS-3981
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3981.patch
>
>




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


[jira] [Created] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work

2020-10-06 Thread Durga Kadam (Jira)
Durga Kadam created ATLAS-3978:
--

 Summary: In Administration, Audits filter for 'OR' condition does 
not work
 Key: ATLAS-3978
 URL: https://issues.apache.org/jira/browse/ATLAS-3978
 Project: Atlas
  Issue Type: Bug
Reporter: Durga Kadam
 Attachments: OR condition not working.mkv

Description::

When user uses OR condition it does not apply on filter, results are listed 
with AND condition. PFA evidence file [OR condition not working.mkv]

Steps to regenerate::
 # Go to Administration- Audits
 # Select the OR condition filter
 # Check the console for response
 # Results are listed with 'AND' operator instead of 'OR'



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


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

2020-08-11 Thread Durga Kadam (Jira)
Durga Kadam created ATLAS-3917:
--

 Summary: While deleting parent tag, shows incorrect message.
 Key: ATLAS-3917
 URL: https://issues.apache.org/jira/browse/ATLAS-3917
 Project: Atlas
  Issue Type: Bug
Reporter: Durga Kadam
 Attachments: tag_with_{0}_reproducible.mkv

Actual Behaviour - While deleting parent tag if the tag is 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
 # Associate the created tag with any of the entity
 # Try to delete the 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-3897) UI: Normalize list of propagated classifications

2020-07-22 Thread Durga Kadam (Jira)


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

Durga Kadam commented on ATLAS-3897:


+1 for the patch [~kevalbhatt]

> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3897-1.patch, ATLAS-3897-2.patch, 
> ATLAS-3897-3.patch, ATLAS-3897.patch, Screen Shot 2020-07-17 at 6.13.04 PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)
>  
> !Screen Shot 2020-07-17 at 6.13.04 PM.png|width=593,height=359!



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


[jira] [Created] (ATLAS-3887) Consistency and highlighting issues while switching between old and new UI

2020-07-10 Thread Durga Kadam (Jira)
Durga Kadam created ATLAS-3887:
--

 Summary: Consistency and highlighting issues while switching 
between old and new UI
 Key: ATLAS-3887
 URL: https://issues.apache.org/jira/browse/ATLAS-3887
 Project: Atlas
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Durga Kadam
 Attachments: classification and glossari does not highlight also 
glossary does not show title when switched to new UI.mkv

Description::

When switched from old to new UI,
 # Classification and Glossary does not highlight the content, also
 # Glossary does not show the title. 

PFA video



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


[jira] [Created] (ATLAS-3872) While creating Column entity shows error message

2020-06-30 Thread Durga Kadam (Jira)
Durga Kadam created ATLAS-3872:
--

 Summary: While creating Column entity shows error message
 Key: ATLAS-3872
 URL: https://issues.apache.org/jira/browse/ATLAS-3872
 Project: Atlas
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Durga Kadam
 Attachments: column_entity_name_field_issue.ogv

Description:: While creating Column entity(whose entity-type has been generated 
from running quick_start.py) if user does not provide the 'name'(by enabling 
the toggle 'Required All') it shows below error message.

Error message:: 

Invalid instance creation/updation parameters passed : Column.name: mandatory 
attribute value missing in type Asset

Steps to reproduce issue::
 # Go to Create  entity
 # Select 'Column' type
 # Enter 'QualifiedName(string)' and select the 'Table(Table)' from drop-down
 # Click on Create buttonIt will show error message

Note-
 # If user provides the 'name' which is listed inside the 'Required All' tab it 
will allow user to save the entity. PFA attached video.
 # Working fine for Hive_column and Hbase_column as user provides the mandatory 
name field which is listed outside the 'Required All' tab



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


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

2020-06-25 Thread Durga Kadam (Jira)


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

Durga Kadam resolved ATLAS-3857.

Resolution: Fixed

https://issues.apache.org/jira/browse/ATLAS-3857 and 
https://issues.apache.org/jira/browse/ATLAS-3156 

have the same solution as added loader on the delete button.

> [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] [Closed] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

2020-06-25 Thread Durga Kadam (Jira)


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

Durga Kadam closed ATLAS-3861.
--

not able to reproduce on new and old ui, hence colsing this.

> [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: Screenshot from 2020-06-25 20-49-29.png, Screenshot from 
> 2020-06-25 20-49-29.png, 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] [Resolved] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

2020-06-25 Thread Durga Kadam (Jira)


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

Durga Kadam resolved ATLAS-3861.

Resolution: Cannot Reproduce

> [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: Screenshot from 2020-06-25 20-49-29.png, Screenshot from 
> 2020-06-25 20-49-29.png, 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

2020-06-25 Thread 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:
---
Attachment: Screenshot from 2020-06-25 20-49-29.png

> [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: Screenshot from 2020-06-25 20-49-29.png, Screenshot from 
> 2020-06-25 20-49-29.png, 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] [Commented] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

2020-06-25 Thread Durga Kadam (Jira)


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

Durga Kadam commented on ATLAS-3861:


Not able to reproduce, hence closing this Jira. !Screenshot from 2020-06-25 
20-49-29.png!

> [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: Screenshot from 2020-06-25 20-49-29.png, Screenshot from 
> 2020-06-25 20-49-29.png, 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

2020-06-25 Thread 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:
---
Attachment: Screenshot from 2020-06-25 20-49-29.png

> [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: Screenshot from 2020-06-25 20-49-29.png, 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-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

2020-06-23 Thread 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)


[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

2020-06-23 Thread 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-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

2020-06-23 Thread 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-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

2020-06-23 Thread 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-3862) [UI] When added term with large name validation msgs are misaligned. PFA snaps

2020-06-23 Thread 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

2020-06-23 Thread 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)


[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

2020-06-23 Thread 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] [Created] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment

2020-06-23 Thread 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] [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

2020-06-23 Thread 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] [Created] (ATLAS-3859) [UI] In edit entity window shows calender with 'Invalid date'

2020-06-23 Thread 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] [Created] (ATLAS-3858) [UI] Misaligment happened in Glossaries when added term with large name

2020-06-23 Thread 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-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.

2020-06-23 Thread 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] [Updated] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.

2020-06-23 Thread 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-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.

2020-06-23 Thread 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] [Updated] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg

2020-06-23 Thread 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

2020-06-23 Thread 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] [Created] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg

2020-06-23 Thread 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] [Updated] (ATLAS-3830) UI: Business Metadata tab misalignment issue

2020-06-09 Thread Durga Kadam (Jira)


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

Durga Kadam updated ATLAS-3830:
---
Summary: UI: Business Metadata tab misalignment issue  (was: Business 
Metadata tab overlapping issue)

> UI: Business Metadata tab misalignment issue
> 
>
> Key: ATLAS-3830
> URL: https://issues.apache.org/jira/browse/ATLAS-3830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: missalignment-due-to-business-metadata-selection.webm
>
>
> Misalignment happens when the drop-downs are closed and reopened from left 
> panel.
> Please find attached video clip for steps to reproduce.
>  



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


[jira] [Updated] (ATLAS-3830) Business Metadata tab overlapping issue

2020-06-09 Thread Durga Kadam (Jira)


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

Durga Kadam updated ATLAS-3830:
---
Description: 
Misalignment happens when the drop-downs are closed and reopened from left 
panel.

Please find attached video clip for steps to reproduce.

 

  was:
Misalignment happens when closed and reopen the drop-downs from left panel.

Please find attached video clip for steps to reproduce.

 


> Business Metadata tab overlapping issue
> ---
>
> Key: ATLAS-3830
> URL: https://issues.apache.org/jira/browse/ATLAS-3830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: missalignment-due-to-business-metadata-selection.webm
>
>
> Misalignment happens when the drop-downs are closed and reopened from left 
> panel.
> Please find attached video clip for steps to reproduce.
>  



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


[jira] [Created] (ATLAS-3830) Business Metadata tab overlapping issue

2020-06-09 Thread Durga Kadam (Jira)
Durga Kadam created ATLAS-3830:
--

 Summary: Business Metadata tab overlapping issue
 Key: ATLAS-3830
 URL: https://issues.apache.org/jira/browse/ATLAS-3830
 Project: Atlas
  Issue Type: Bug
Reporter: Durga Kadam
 Attachments: missalignment-due-to-business-metadata-selection.webm

Misalignment happens when closed and reopen the drop-downs from left panel.

Please find attached video clip for steps to reproduce.

 



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