[jira] [Commented] (ATLAS-3840) Atlas website's html meta description is set to "My awesome app using docz"
[
https://issues.apache.org/jira/browse/ATLAS-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149388#comment-17149388
]
Keval Bhatt commented on ATLAS-3840:
Thanks [~umesh.padashetty] for the patch
> Atlas website's html meta description is set to "My awesome app using docz"
> ---
>
> Key: ATLAS-3840
> URL: https://issues.apache.org/jira/browse/ATLAS-3840
> Project: Atlas
> Issue Type: Bug
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Major
> Attachments: ATLAS-3840-1.patch, ATLAS-3840.patch, Screenshot
> 2020-06-04 at 3.11.48 PM.png, Screenshot 2020-06-12 at 9.36.43 PM.png
>
>
> As seen at [view-source:https://atlas.apache.org/#/] meta tag is set to
> {code:java}
> {code}
> !Screenshot 2020-06-12 at 9.36.43 PM.png|width=1390,height=122!
> When Atlas website link is posted in apps which support thumbnail view (like
> Slack, WhatsApp etc), the thumbnail view shows "My awesome app using docz"
> !Screenshot 2020-06-04 at 3.11.48 PM.png|width=596,height=194!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3840) Atlas website's html meta description is set to "My awesome app using docz"
[
https://issues.apache.org/jira/browse/ATLAS-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3840:
---
Fix Version/s: 3.0.0
2.1.0
> Atlas website's html meta description is set to "My awesome app using docz"
> ---
>
> Key: ATLAS-3840
> URL: https://issues.apache.org/jira/browse/ATLAS-3840
> Project: Atlas
> Issue Type: Bug
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3840-1.patch, ATLAS-3840.patch, Screenshot
> 2020-06-04 at 3.11.48 PM.png, Screenshot 2020-06-12 at 9.36.43 PM.png
>
>
> As seen at [view-source:https://atlas.apache.org/#/] meta tag is set to
> {code:java}
> {code}
> !Screenshot 2020-06-12 at 9.36.43 PM.png|width=1390,height=122!
> When Atlas website link is posted in apps which support thumbnail view (like
> Slack, WhatsApp etc), the thumbnail view shows "My awesome app using docz"
> !Screenshot 2020-06-04 at 3.11.48 PM.png|width=596,height=194!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3870) UI: hive_table entity table not updating queryparams based on filter selected
[
https://issues.apache.org/jira/browse/ATLAS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3870:
---
Attachment: ATLAS-3870.patch
> UI: hive_table entity table not updating queryparams based on filter selected
> -
>
> Key: ATLAS-3870
> URL: https://issues.apache.org/jira/browse/ATLAS-3870
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 2.0.0
> Reporter: Keval Bhatt
> Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3870.patch, Screenshot 2020-06-30 at 2.33.11
> PM.png, Screenshot 2020-06-30 at 2.34.06 PM.png
>
>
> * Go to hive_db entity detail page
> * Click on Table tab
> * toggle "Show historical entities" checkbox and check the network for the
> API
> API always send the same value for
> {code:java}
> excludeDeletedEntities: true
> {code}
> !Screenshot 2020-06-30 at 2.33.11 PM.png|width=374,height=219!
> !Screenshot 2020-06-30 at 2.34.06 PM.png|width=397,height=142!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3870) UI: hive_table entity table not updating queryparams based on filter selected
Keval Bhatt created ATLAS-3870:
--
Summary: UI: hive_table entity table not updating queryparams
based on filter selected
Key: ATLAS-3870
URL: https://issues.apache.org/jira/browse/ATLAS-3870
Project: Atlas
Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Keval Bhatt
Assignee: Keval Bhatt
Fix For: 2.1.0, 3.0.0
Attachments: Screenshot 2020-06-30 at 2.33.11 PM.png, Screenshot
2020-06-30 at 2.34.06 PM.png
* Go to hive_db entity detail page
* Click on Table tab
* toggle "Show historical entities" checkbox and check the network for the API
API always send the same value for
{code:java}
excludeDeletedEntities: true
{code}
!Screenshot 2020-06-30 at 2.33.11 PM.png|width=374,height=219!
!Screenshot 2020-06-30 at 2.34.06 PM.png|width=397,height=142!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3849) UI: Create icons for new entity types for Apache ozone
[ https://issues.apache.org/jira/browse/ATLAS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3849: --- Affects Version/s: (was: 3.0.0) > UI: Create icons for new entity types for Apache ozone > -- > > Key: ATLAS-3849 > URL: https://issues.apache.org/jira/browse/ATLAS-3849 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3849.patch > > > New typeDefs: > * ozone_volume > * ozone_bucket > * ozone_key -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3849) UI: Create icons for new entity types for Apache ozone
[ https://issues.apache.org/jira/browse/ATLAS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3849: --- Fix Version/s: 3.0.0 2.1.0 > UI: Create icons for new entity types for Apache ozone > -- > > Key: ATLAS-3849 > URL: https://issues.apache.org/jira/browse/ATLAS-3849 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 2.0.0, 3.0.0 >Reporter: Nikhil Bonte >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3849.patch > > > New typeDefs: > * ozone_volume > * ozone_bucket > * ozone_key -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3849) UI: Create icons for new entity types for Apache ozone
[ https://issues.apache.org/jira/browse/ATLAS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3849: --- Attachment: ATLAS-3849.patch > UI: Create icons for new entity types for Apache ozone > -- > > Key: ATLAS-3849 > URL: https://issues.apache.org/jira/browse/ATLAS-3849 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3849.patch > > > New typeDefs: > * ozone_volume > * ozone_bucket > * ozone_key -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3858) [UI] Misaligment happened in Glossaries when added term with large name
[
https://issues.apache.org/jira/browse/ATLAS-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3858:
---
Fix Version/s: 3.0.0
2.1.0
> [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
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3858.patch, 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-3858) [UI] Misaligment happened in Glossaries when added term with large name
[
https://issues.apache.org/jira/browse/ATLAS-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3858:
---
Attachment: ATLAS-3858.patch
> [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: ATLAS-3858.patch, 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] [Resolved] (ATLAS-3862) [UI] When added term with large name validation msgs are misaligned. PFA snaps
[ https://issues.apache.org/jira/browse/ATLAS-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-3862. Resolution: Fixed > [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 > Fix For: 2.1.0, 3.0.0 > > 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] [Updated] (ATLAS-3862) [UI] When added term with large name validation msgs are misaligned. PFA snaps
[ https://issues.apache.org/jira/browse/ATLAS-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3862: --- Fix Version/s: 3.0.0 2.1.0 > [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 > Fix For: 2.1.0, 3.0.0 > > 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] [Assigned] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.
[ https://issues.apache.org/jira/browse/ATLAS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3857: -- Assignee: (was: 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 >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] [Resolved] (ATLAS-3859) [UI] In edit entity window shows calender with 'Invalid date'
[
https://issues.apache.org/jira/browse/ATLAS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt resolved ATLAS-3859.
Fix Version/s: 3.0.0
2.1.0
Resolution: Fixed
> [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
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3859.patch, 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-3156) UI:No loading animation while creating or deleting a Classification, Create Entity, View loading
[ https://issues.apache.org/jira/browse/ATLAS-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3156: --- Attachment: ATLAS-3156-4.patch > UI:No loading animation while creating or deleting a Classification, Create > Entity, View loading > > > Key: ATLAS-3156 > URL: https://issues.apache.org/jira/browse/ATLAS-3156 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup > Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3156-1.patch, ATLAS-3156-3.patch, > ATLAS-3156-4.patch, ATLAS-3156.patch > > > While creating a Classification, there is no loading animation or any > indication to the user that the creation process is underway. The user only > gets a notification that the creation process is complete. If for some reason > the creation process takes a long while, then this lack of indication might > confuse the user into thinking that nothing is happening on clicking the > 'Create' button. > > This same issue exists when trying to delete a classification. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3859) [UI] In edit entity window shows calender with 'Invalid date'
[
https://issues.apache.org/jira/browse/ATLAS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3859:
---
Attachment: ATLAS-3859.patch
> [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: ATLAS-3859.patch, 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] [Commented] (ATLAS-3857) [UI] When deleted term same term twice shows 'Something went wrong' msg.
[ https://issues.apache.org/jira/browse/ATLAS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144957#comment-17144957 ] Keval Bhatt commented on ATLAS-3857: UI issue if fixed by ATLAS-3156 > [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)
[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
[
https://issues.apache.org/jira/browse/ATLAS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt reassigned ATLAS-3860:
--
Assignee: (was: 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
>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] [Resolved] (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
[
https://issues.apache.org/jira/browse/ATLAS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt resolved ATLAS-3860.
Resolution: Fixed
> 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] [Assigned] (ATLAS-3862) [UI] When added term with large name validation msgs are misaligned. PFA snaps
[ 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] [Assigned] (ATLAS-3861) [UI] When Entity added with existing BusinessMetadata Attribute shows misalignment
[
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-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
[
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] [Assigned] (ATLAS-3859) [UI] In edit entity window shows calender with 'Invalid date'
[
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-3858) [UI] Misaligment happened in Glossaries when added term with large name
[
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.
[ 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: Navigating Atlas Documentation on Github
Hi Matthew,
Please find sample payload to create hive_table entity with replicatedTo
attribute:
{
"entity": {
"attributes": {
"db": {
"guid": "3cc0cb04-2d8e-4d39-9bb0-4aefaf950dcc",
"typeName": "hive_db"
},
"name": "temptable",
"owner": "owner",
"parameters": {},
"qualifiedName": "db_1.temptable@mycluster0",
"replicatedTo": [
{
"guid": "15aa1cab-b5e1-46bd-8077-9d00a72026ff",
"typeName": "AtlasServer"
}
],
"retention": 0,
"tableType": "MANAGED_TABLE",
"temporary": true
},
"typeName": "hive_table"
},
"referredEntities": {}
}
Thanks,
Keval
On Thu, Jun 18, 2020 at 2:39 AM Lynch, Matthew <
matthew.ly...@bankofthewest.com> wrote:
> Keval,
>
>
>
> My name is Matthew Lynch and I’m currently a data governance analyst with
> Bank of the West.
>
> I’ve been using a custom Python script for updating metadata attributes
> for entities (primarily hive_tables and hive_columns) through post requests
> in v2 REST API.
>
> However, I’ve encountered an interesting post error that states:
> “{"errorCode":"ATLAS-404-00-007","errorMessage":"Invalid instance
> creation/updation parameters passed : hive_column.replicatedTo=TestRep:
> invalid value for type array"}”.
>
> I’ve been looking all over the place for documentation on what primitive
> type values replicatedTo and replicatedFrom attributes can take but have
> been unable to find them so far.
>
> Can you point me in the right direction?
>
>
>
> *Matthew Lynch*
>
> Data Governance Analyst Intern
>
> _
>
>
>
> Bank of the West
>
> 1625 West Fountainhead Parkway
>
> Tempe, Arizona 85282
>
> C: 505.414.8353
>
> matthew.ly...@bankofthewest.com
>
>
>
> [image: BankPic]
>
>
> --
>
>
>
> * IMPORTANT NOTICE: This message is intended only for the addressee and
> may contain confidential, privileged information. If you are not the
> intended recipient, you may not use, copy or disclose any information
> contained in the message. If you have received this message in error,
> please notify the sender by reply e-mail and delete the message. *
>
[jira] [Updated] (ATLAS-3851) UI: Remove hourglass icon from in progress entity
[ https://issues.apache.org/jira/browse/ATLAS-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3851: --- Attachment: ATLAS-3851.patch > UI: Remove hourglass icon from in progress entity > - > > Key: ATLAS-3851 > URL: https://issues.apache.org/jira/browse/ATLAS-3851 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3851.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3851) UI: Remove hourglass icon from in progress entity
Keval Bhatt created ATLAS-3851: -- Summary: UI: Remove hourglass icon from in progress entity Key: ATLAS-3851 URL: https://issues.apache.org/jira/browse/ATLAS-3851 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Description: !image-2020-06-16-17-01-29-797.png|width=650,height=361! !image-2020-06-16-17-01-58-179.png|width=641,height=472! > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822.patch, > image-2020-06-16-17-01-29-797.png, image-2020-06-16-17-01-58-179.png > > > !image-2020-06-16-17-01-29-797.png|width=650,height=361! > > !image-2020-06-16-17-01-58-179.png|width=641,height=472! > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Attachment: Screen Shot 2020-06-16 at 5.00.53 PM.png > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822.patch, > image-2020-06-16-17-01-29-797.png, image-2020-06-16-17-01-58-179.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Attachment: image-2020-06-16-17-01-58-179.png > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822.patch, > image-2020-06-16-17-01-29-797.png, image-2020-06-16-17-01-58-179.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Attachment: image-2020-06-16-17-01-29-797.png > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822.patch, > image-2020-06-16-17-01-29-797.png, image-2020-06-16-17-01-58-179.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Attachment: (was: Screen Shot 2020-06-16 at 5.00.53 PM.png) > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822.patch, > image-2020-06-16-17-01-29-797.png, image-2020-06-16-17-01-58-179.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Attachment: ATLAS-3822-1.patch > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3822-1.patch, ATLAS-3822.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Seeking advice on Atlas XSS vulnerabilities
Hi Bolke, Thanks for the details on the UI issues in rendering entity name and incorrect value storied for user-defined attributes. I am working on updating UI to address these issues, will send a patch shortly. If you see further issues that require a server-side update, can you please add specific use case details? Thanks On Fri, Jun 12, 2020 at 2:15 PM Bolke de Bruin wrote: > Hi Madhan, > > A second order XSS (I.e. stored) can be executed against Atlas quite > easily. If you create an entity with a name like > > “> > > You will get an alert when clicking “edit” and you will get artifacts all > over the place stemming from the closing ‘“>’. And there are probably other > areas where I can do this. Given the fact I can almost store arbitrary > sizes into Atlas it does not take a lot of imagination to think of a rogue > service adding an entity (or something else) with a malicious payload and > then just wait for a user to pick it up. > > This is not an “XSS in the UI”. OWASP states that “ DOM Based XSS (or as > it is called in some texts, “type-0 XSS” or “CLIENT SIDE XSS”) is an XSS > attack wherein the attack payload is executed as a result of modifying the > DOM “environment” in the victim’s browser used by the original client side > script, so that the client side code runs in an “unexpected” manner. That > is, the page itself (the HTTP response that is) does not change, but the > client side code contained in the page executes differently due to the > malicious modifications that have occurred in the DOM environment. This is > in contrast to other XSS attacks (stored or reflected), wherein the attack > payload is placed in the response page (due to a server side flaw). > > As shown above I was able to make the server return malicious code by > storing data and have it returned at a different time. This makes it a > Stored XSS. OWASP ( > https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html) > states that to prevent stored XSS it should be addressed server side. > > Note also that the UI deals with escaping differently at different places. > For example the “user labels” are being escaped (but not properly > unescaped) on the client side. Entity definitions allow anything. Server > side validation is not done, so I can easily circumvent the UI and edit the > request. > > I assume that you agree with the fact that bare HTML and JavaScript do not > really have a place in Atlas definitions or a need? Why not escape data on > output and make that configurable if really needed? And lets improve the > CSP headers while we are at it (this is being looked at as you mentioned)? > > Cheers > Bolke > > Verstuurd vanaf mijn iPad > > >> Op 11 jun. 2020 om 02:30 heeft Madhan Neethiraj > het volgende geschreven: > > Melinda, > > > > As I said earlier, I don't agree on server side escaping HTML characters > in its input and output. Escaping must be handled by components that are > prone to issues in dealing with unescaped data. We are discussing potential > XSS in UI while dealing with data from user/server, which requires UI > updates to perform necessary escapes. As I said earlier, Keval is already > looking into this. > > > > And, I haven't heard yet (from you/Bolke/anyone else) on any server side > issues that require Atlas server to escape HTML characters in data it > receives/responds. I strongly suggest to not treat this as a release > blocker. If anyone thinks it is, please come out with clear use > cases/examples quickly. > > > > Regards, > > Madhan > > > > > > > > On 6/10/20, 3:22 PM, "Melinda Crane" wrote: > > > >Dear Madhan and Bolke, > > > > > >Are there any updates on this topic? The discussion so far has been > pretty > >exciting to see and hear - having the sanitization feature as an > optional > >config like Bolke mentioned would be real useful to us (since we know > our > >data should never contain html characters), and it seems like it > would be > >useful for other companies down the road who have stricter security > >requirements. Where the sanitization would happen is of course > completely > >up to you folks! > > > > > >Cheers, > > > >Melinda Crane > > > >>On Tue, Jun 9, 2020 at 10:46 AM Madhan Neethiraj > wrote: > >> > >> Bolke, > >> > >>>1. Filtering input on arrival where the user cannot manipulate it > >> anymore (i.e. server) > >> It's not clear what you expect the server to do here? Should HTML > >> characters be escaped in all inputs, before saving the data in its > store? > >> Can you give few examples of server-side manipulation due to unescaped > HTML > >> characters? > >> > >>>2. Encode data on output > >> I think asking the server side to escape all HTML characters in its > >> response is a very bad idea. Consider forcing such a requirement on a > RDBMS > >> - wouldn't this mandate every client to un-escape every column value > >> returned for queries? Can you add references to
Re: Seeking advice on Atlas XSS vulnerabilities
Hi Melinda, Thanks for the details on the XSS issue; it helped to investigate and verify the fix. This fix is now merged in master and branch-2.0 branches. About the concerns with eval in requires.js: Atlas UI uses handlebar templates to render HTML; requires.js gets the handlebar templates as a string and uses eval function to generate HTML for dynamic rendering. I added necessary escapes to avoid XSS issues for handlebar templates. Thanks On Thu, Jun 11, 2020 at 2:03 PM Bolke de Bruin wrote: > I'm working on a POC that shows the need for server side escaping due to > second order XSS (stored XSS). > > That's taking a bit of time. > > B. > > Sent from my iPhone > > > On 11 Jun 2020, at 02:30, Madhan Neethiraj wrote: > > > > Melinda, > > > > As I said earlier, I don't agree on server side escaping HTML characters > in its input and output. Escaping must be handled by components that are > prone to issues in dealing with unescaped data. We are discussing potential > XSS in UI while dealing with data from user/server, which requires UI > updates to perform necessary escapes. As I said earlier, Keval is already > looking into this. > > > > And, I haven't heard yet (from you/Bolke/anyone else) on any server side > issues that require Atlas server to escape HTML characters in data it > receives/responds. I strongly suggest to not treat this as a release > blocker. If anyone thinks it is, please come out with clear use > cases/examples quickly. > > > > Regards, > > Madhan > > > > > > > > On 6/10/20, 3:22 PM, "Melinda Crane" wrote: > > > >Dear Madhan and Bolke, > > > > > >Are there any updates on this topic? The discussion so far has been > pretty > >exciting to see and hear - having the sanitization feature as an > optional > >config like Bolke mentioned would be real useful to us (since we know > our > >data should never contain html characters), and it seems like it > would be > >useful for other companies down the road who have stricter security > >requirements. Where the sanitization would happen is of course > completely > >up to you folks! > > > > > >Cheers, > > > >Melinda Crane > > > >>On Tue, Jun 9, 2020 at 10:46 AM Madhan Neethiraj > wrote: > >> > >> Bolke, > >> > >>>1. Filtering input on arrival where the user cannot manipulate it > >> anymore (i.e. server) > >> It's not clear what you expect the server to do here? Should HTML > >> characters be escaped in all inputs, before saving the data in its > store? > >> Can you give few examples of server-side manipulation due to unescaped > HTML > >> characters? > >> > >>>2. Encode data on output > >> I think asking the server side to escape all HTML characters in its > >> response is a very bad idea. Consider forcing such a requirement on a > RDBMS > >> - wouldn't this mandate every client to un-escape every column value > >> returned for queries? Can you add references to applications that > perform > >> HTML escape of all its REST API responses?. > >> > >>>3. Set correct Http content headers (e.g. application/json) > >> This is already being done. Do you find this missing for any specific > >> usecases? > >> > >>>4. Set correct Content Security Policy. > >> This is being looked into. > >> > >> Regards, > >> Madhan > >> > >> > >> On 6/9/20, 12:49 AM, "Bolke de Bruin" wrote: > >> > >>Hi Madhan, > >> > >>I don’t think solving this on the front-end is sufficient and the > >> defense should be more in-depth. The front-end is after all client side > and > >> can be manipulated by the user. Typically one solves XSS > vulnerabilities by: > >> > >>1. Filtering input on arrival where the user cannot manipulate it > >> anymore (i.e. server) > >>2. Encode data on output > >>3. Set correct Http content headers (e.g. application/json) > >>4. Set correct Content Security Policy. > >> > >>Your proposed solution does not fit any of those criteria. If you are > >> worried about compatibility I suggest making it a server side > configuration > >> variable (e.g. atlas.server.insecure_escaping) which should default to > >> “false” imho and alternative could be to enable configurable escaping > but > >> that’s more complex. > >> > >>Note that in this case also #4 CSP headers seem to be very loose > >> (unsafe-inline, unsafe-eval) which add to the attack surface: > >> > >> > >> > https://github.com/apache/atlas/blob/master/webapp/src/main/java/org/apache/atlas/web/filters/HeadersUtil.java#L44 > >> > >>Regards, > >>Bolke > >> > >>Verstuurd vanaf mijn iPad > >> > >>> Op 9 jun. 2020 om 06:04 heeft Madhan Neethiraj > >> het volgende geschreven: > >>> > >>> Melinda, > >>> > >>> Thank you for adding details. I think the frontend must take steps > >> to prevent JavaScript execution while handling values in REST API > responses. > >>> > >>> Server side escaping all HTML characters in all responses wouldn’t > >> be the right approach, as browser is not the only consumer
[jira] [Updated] (ATLAS-3828) UI: Change 'Status' from Classification System Attributes to EntityStatus
[ https://issues.apache.org/jira/browse/ATLAS-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3828: --- Fix Version/s: 3.0.0 2.1.0 > UI: Change 'Status' from Classification System Attributes to EntityStatus > - > > Key: ATLAS-3828 > URL: https://issues.apache.org/jira/browse/ATLAS-3828 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3828.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3828) UI: Change 'Status' from Classification System Attributes to EntityStatus
[ https://issues.apache.org/jira/browse/ATLAS-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3828: --- Attachment: ATLAS-3828.patch > UI: Change 'Status' from Classification System Attributes to EntityStatus > - > > Key: ATLAS-3828 > URL: https://issues.apache.org/jira/browse/ATLAS-3828 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3828.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3830) UI: Business Metadata tab misalignment issue
[ https://issues.apache.org/jira/browse/ATLAS-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3830: --- Attachment: ATLAS-3830.patch > 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 > Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3830.patch, > 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) UI: Business Metadata tab misalignment issue
[ https://issues.apache.org/jira/browse/ATLAS-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3830: --- Fix Version/s: 3.0.0 2.1.0 > 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 > Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > 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-3769) UI: Changing page limit in Admin audits resets any filters applied on that page
[ https://issues.apache.org/jira/browse/ATLAS-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3769: --- Fix Version/s: 3.0.0 2.1.0 > UI: Changing page limit in Admin audits resets any filters applied on that > page > --- > > Key: ATLAS-3769 > URL: https://issues.apache.org/jira/browse/ATLAS-3769 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup > Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3769.patch > > > If any filters are set in the Audits Page in the Administration menu, > changing the page limit in Admin audits resets the filters applied on that > page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3769) UI: Changing page limit in Admin audits resets any filters applied on that page
[ https://issues.apache.org/jira/browse/ATLAS-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3769: --- Attachment: ATLAS-3769.patch > UI: Changing page limit in Admin audits resets any filters applied on that > page > --- > > Key: ATLAS-3769 > URL: https://issues.apache.org/jira/browse/ATLAS-3769 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup > Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-3769.patch > > > If any filters are set in the Audits Page in the Administration menu, > changing the page limit in Admin audits resets the filters applied on that > page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3829) UI: Clicking on meanings from relationship tab should redirect to terms details page.
[ https://issues.apache.org/jira/browse/ATLAS-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3829: --- Attachment: ATLAS-3829.patch > UI: Clicking on meanings from relationship tab should redirect to terms > details page. > - > > Key: ATLAS-3829 > URL: https://issues.apache.org/jira/browse/ATLAS-3829 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3829.patch, image-2020-06-09-17-14-17-856.png, > image-2020-06-09-17-14-17-989.png > > > * Assign term to Entity > * Go to relationship tab click on meanings link > * It should redirect to term detail page not entity detail page. > > !image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3831) UI: Add entity icon for spark
[ https://issues.apache.org/jira/browse/ATLAS-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3831: --- Attachment: ATLAS-3831.patch > UI: Add entity icon for spark > - > > Key: ATLAS-3831 > URL: https://issues.apache.org/jira/browse/ATLAS-3831 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3831.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3831) UI: Add entity icon for spark
[ https://issues.apache.org/jira/browse/ATLAS-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3831: --- Issue Type: Improvement (was: Bug) > UI: Add entity icon for spark > - > > Key: ATLAS-3831 > URL: https://issues.apache.org/jira/browse/ATLAS-3831 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3831) UI: Add entity icon for spark
Keval Bhatt created ATLAS-3831: -- Summary: UI: Add entity icon for spark Key: ATLAS-3831 URL: https://issues.apache.org/jira/browse/ATLAS-3831 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3830) UI: Business Metadata tab misalignment issue
[ https://issues.apache.org/jira/browse/ATLAS-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3830: -- Assignee: Keval Bhatt > 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 > Assignee: Keval Bhatt >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-3829) UI: Clicking on meanings from relationship tab should redirect to terms detail page.
[ https://issues.apache.org/jira/browse/ATLAS-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3829: --- Summary: UI: Clicking on meanings from relationship tab should redirect to terms detail page. (was: UI: Relationship tab clicking on meanings should redirect to terms detail page.) > UI: Clicking on meanings from relationship tab should redirect to terms > detail page. > > > Key: ATLAS-3829 > URL: https://issues.apache.org/jira/browse/ATLAS-3829 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-06-09-17-14-17-856.png, > image-2020-06-09-17-14-17-989.png > > > * Assign term to Entity > * Go to relationship tab click on meanings link > * It should redirect to term detail page not entity detail page. > > !image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3829) UI: Clicking on meanings from relationship tab should redirect to terms details page.
[ https://issues.apache.org/jira/browse/ATLAS-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3829: --- Summary: UI: Clicking on meanings from relationship tab should redirect to terms details page. (was: UI: Clicking on meanings from relationship tab should redirect to terms detail page.) > UI: Clicking on meanings from relationship tab should redirect to terms > details page. > - > > Key: ATLAS-3829 > URL: https://issues.apache.org/jira/browse/ATLAS-3829 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-06-09-17-14-17-856.png, > image-2020-06-09-17-14-17-989.png > > > * Assign term to Entity > * Go to relationship tab click on meanings link > * It should redirect to term detail page not entity detail page. > > !image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3829) UI: Relationship tab clicking on meanings should redirect to terms detail page.
Keval Bhatt created ATLAS-3829: -- Summary: UI: Relationship tab clicking on meanings should redirect to terms detail page. Key: ATLAS-3829 URL: https://issues.apache.org/jira/browse/ATLAS-3829 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 Attachments: image-2020-06-09-17-14-17-856.png, image-2020-06-09-17-14-17-989.png * Assign term to Entity * Go to relationship tab click on meanings link * It should redirect to term detail page not entity detail page. !image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.
[ https://issues.apache.org/jira/browse/ATLAS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3827: --- Summary: UI: Use moment date format instead of default date format. (was: UI: Insted of default date format it should be moment format.) > UI: Use moment date format instead of default date format. > -- > > Key: ATLAS-3827 > URL: https://issues.apache.org/jira/browse/ATLAS-3827 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > > Date Format should be > /MM/DD hh:mm:ss -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3827) UI: Insted of default date format it should be moment format.
[ https://issues.apache.org/jira/browse/ATLAS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3827: --- Fix Version/s: 3.0.0 > UI: Insted of default date format it should be moment format. > - > > Key: ATLAS-3827 > URL: https://issues.apache.org/jira/browse/ATLAS-3827 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > > Date Format should be > /MM/DD hh:mm:ss -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3828) UI: Change 'Status' from Classification System Attributes to EntityStatus
Keval Bhatt created ATLAS-3828: -- Summary: UI: Change 'Status' from Classification System Attributes to EntityStatus Key: ATLAS-3828 URL: https://issues.apache.org/jira/browse/ATLAS-3828 Project: Atlas Issue Type: Sub-task Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3827) UI: Insted of default date format it should be moment format.
[ https://issues.apache.org/jira/browse/ATLAS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3827: --- Summary: UI: Insted of default date format it should be moment format. (was: UI: Insted of default date format it should be defined.) > UI: Insted of default date format it should be moment format. > - > > Key: ATLAS-3827 > URL: https://issues.apache.org/jira/browse/ATLAS-3827 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > > Date Format should be > /MM/DD hh:mm:ss -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3827) UI: Insted of default date format it should be defined.
Keval Bhatt created ATLAS-3827: -- Summary: UI: Insted of default date format it should be defined. Key: ATLAS-3827 URL: https://issues.apache.org/jira/browse/ATLAS-3827 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt Date Format should be /MM/DD hh:mm:ss -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Seeking advice on Atlas XSS vulnerabilities
Thanks, Melinda, for the detailed explanation. I am able to reproduce the issue. wIll provide the patch for this. On Tue, Jun 9, 2020 at 9:34 AM Madhan Neethiraj wrote: > Melinda, > > Thank you for adding details. I think the frontend must take steps to > prevent JavaScript execution while handling values in REST API responses. > > Server side escaping all HTML characters in all responses wouldn’t be the > right approach, as browser is not the only consumer of the responses. > Consider applications that parse response from Atlas REST APIs; all such > applications must be updated to deal with escaped HTML characters in > responses. This will likely break existing Atlas integrations. > > Hope this helps. > > Regards, > Madhan > > On 6/8/20, 6:31 PM, "Melinda Crane" wrote: > > Apologies, looks like the second half of the email I just sent got > formatted weirdly (I was copying from a failed earlier email attempt > that > got rejected for attaching images). Just to make sure it doesn’t get > buried: > > Of course this specific case can be patched on the frontend, but doing > some > kind of HTML sanitization escaping into the > whatever-is-handling-the-ajax > (EntityREST or AtlasEntityStoreV2, maybe?) to blanket-catch HTML > characters > sounds safer. > > Hope this helps express my concerns. > From, Melinda Crane > > > On Mon, Jun 8, 2020 at 9:13 PM Melinda Crane wrote: > > > Dear Madhan, > > > > Thank you kindly for your response and for offering to look into > potential > > solutions. I've been trying to step through how the ajax calls are > handled, > > I don't really see the AtlasJsonProvider being used much at all > actually > > for that. My concern is that the data from the ajax calls aren't > being > > sanitized on the backend. I see there is a ton of sanitization > happening on > > the frontend (lots of calls to _.escape()), but they're not all > captured. > > For example. > > > > In CommonViewFunction, in the propertyTable > > < > https://github.sc-corp.net/Snapchat/keystone/blob/master/dashboardv2/public/js/utils/CommonViewFunction.js#L267> > function, > > URLs are not escaped. So I can create an entity that has a key value > of > > > > https://www.google.com/search?\;> width='\''1'\'' > > height='\''1'\'' onload='\''window.alert(\"boo\");'\''> > > > > and my script will successfully get successfully injected into my > browser > > when I try to view it. Looks like I can't attach images here but > here's the > > elements: > > > > > > > > > class="hide-empty-value"> > > > > newSchema > > > > > > N/A > > > > > > > > > > classField > > > > > > class="blue-link" > > href="https://www.google.com/search?;> > > > height="1" onload="window.alert(boo);"> > > " > https://www.google.com/search > > ?" > > > height="1" onload="window.alert(boo);"> > > ... > > > > ^You can see the iframe-script combo here. > > > > Of course this specific case can be patched on the frontend, but > doing > > some kind of HTML sanitization escaping on the > > whatever-is-handling-the-ajax (EntityREST or AtlasEntityStoreV2, > maybe?) to > > blanket-catch HTML characters sounds safer. > > > > Hope this helps express my concerns. > > From, Melinda Crane > > > > > > On Sat, Jun 6, 2020 at 2:48 PM Madhan Neethiraj > wrote: > > > >> Melinda, > >> > >> Thank you for reaching out to Apache Atlas community. > >> > >> As you noted, AtlasJsonProvider is used to deserialize/serialize > REST API > >> requests and responses. In addition, methods in AtlasJson are used > in to > >> convert to/from Json. It will help if you can add few examples of > potential > >> issues with the current implementation. > >> > >> Keval is looking into the frontend for potential issues and should > get > >> back early next week. > >> > >> Thanks, > >> Madhan > >> > >> > >> > >> > >> On 5/29/20, 6:50 PM, "Melinda Crane" > wrote: > >> > >> Dear Apache Atlas devs, > >> > >> I’m from Snapchat, we’re working on building a catalog on top of > >> Apache > >> Atlas. I noticed looking at the frontend for
Re: Running Apache Atlas on prefix path instead of /
Hi Chitender, I am not sure about the solution I think anyone from server side could help you. I am adding atlas dev email in this thread. Thanks On Fri, Jun 5, 2020, 17:54 Chitender Kumar wrote: > Hello Keval, > > Hope you are doing good. > > Got your from GitHub. > > We are working on Apache Atlas in production setup. Where we are > connecting it to Ranger and Keycloak for authentication and authorisation. > The issue which we are facing is we are not able to figure out how to run > Apache Atlas on prefix path like /atlas instead of /. > > If we configure /atlas in our K8s Nginx controller and when we hit > DNS/atlas its getting redirected to /. > > Can you please help us out here or if you can redirect us to some > reference who answer these query. > > Looking forward for your response. > > Thanks > Chitender
[jira] [Updated] (ATLAS-3770) UI(Classic): Active and Deleted hyperlinks for certain entities throwing error on click
[ https://issues.apache.org/jira/browse/ATLAS-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3770: --- Attachment: ATLAS-3770-1.patch > UI(Classic): Active and Deleted hyperlinks for certain entities throwing > error on click > --- > > Key: ATLAS-3770 > URL: https://issues.apache.org/jira/browse/ATLAS-3770 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3770-1.patch, ATLAS-3770.patch > > > In the Statistics menu under the Entities section, when I try to click the > Active or Deleted link for '__ExportImportAuditEntry' ,'AtlasGlossary' and > 'AtlasGlossaryTerm', I get an message "Invalid Expression or > Classification/Type has been deleted". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3770) UI(Classic): Active and Deleted hyperlinks for certain entities throwing error on click
[ https://issues.apache.org/jira/browse/ATLAS-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3770: --- Attachment: ATLAS-3770.patch > UI(Classic): Active and Deleted hyperlinks for certain entities throwing > error on click > --- > > Key: ATLAS-3770 > URL: https://issues.apache.org/jira/browse/ATLAS-3770 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3770.patch > > > In the Statistics menu under the Entities section, when I try to click the > Active or Deleted link for '__ExportImportAuditEntry' ,'AtlasGlossary' and > 'AtlasGlossaryTerm', I get an message "Invalid Expression or > Classification/Type has been deleted". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3766) Atlas Admin Audit UI pagination is not working
[ https://issues.apache.org/jira/browse/ATLAS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3766: --- Attachment: ATLAS-3766-branch-0.2.patch > Atlas Admin Audit UI pagination is not working > -- > > Key: ATLAS-3766 > URL: https://issues.apache.org/jira/browse/ATLAS-3766 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3766-1.patch, ATLAS-3766-branch-0.2.patch, > ATLAS-3766.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3156) UI:No loading animation while creating or deleting a Classification, Create Entity, View loading
[ https://issues.apache.org/jira/browse/ATLAS-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3156: --- Attachment: ATLAS-3156-3.patch > UI:No loading animation while creating or deleting a Classification, Create > Entity, View loading > > > Key: ATLAS-3156 > URL: https://issues.apache.org/jira/browse/ATLAS-3156 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup > Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3156-1.patch, ATLAS-3156-3.patch, ATLAS-3156.patch > > > While creating a Classification, there is no loading animation or any > indication to the user that the creation process is underway. The user only > gets a notification that the creation process is complete. If for some reason > the creation process takes a long while, then this lack of indication might > confuse the user into thinking that nothing is happening on clicking the > 'Create' button. > > This same issue exists when trying to delete a classification. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3583: --- Fix Version/s: 3.0.0 > Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and > DELETE > > > Key: ATLAS-3583 > URL: https://issues.apache.org/jira/browse/ATLAS-3583 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3822: --- Attachment: ATLAS-3822.patch > UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE > > > Key: ATLAS-3822 > URL: https://issues.apache.org/jira/browse/ATLAS-3822 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane > Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3822.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3814) UI: set classic UI as default for branch-2.0
[ https://issues.apache.org/jira/browse/ATLAS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3814: --- Attachment: ATLAS-3814.patch > UI: set classic UI as default for branch-2.0 > > > Key: ATLAS-3814 > URL: https://issues.apache.org/jira/browse/ATLAS-3814 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0 > > Attachments: ATLAS-3814.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3814) UI: set classic UI as default for branch-2.0
[ https://issues.apache.org/jira/browse/ATLAS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3814: --- Summary: UI: set classic UI as default for branch-2.0 (was: Classic UI: for branch-2.0 make default UI to classic UI) > UI: set classic UI as default for branch-2.0 > > > Key: ATLAS-3814 > URL: https://issues.apache.org/jira/browse/ATLAS-3814 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3814) Classic UI: for branch-2.0 make default UI to classic UI
Keval Bhatt created ATLAS-3814: -- Summary: Classic UI: for branch-2.0 make default UI to classic UI Key: ATLAS-3814 URL: https://issues.apache.org/jira/browse/ATLAS-3814 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3789) UI: Date format is not correct for classfication validity periods.
[ https://issues.apache.org/jira/browse/ATLAS-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3789: --- Attachment: ATLAS-3789.patch > UI: Date format is not correct for classfication validity periods. > -- > > Key: ATLAS-3789 > URL: https://issues.apache.org/jira/browse/ATLAS-3789 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3789.patch > > > While assigning a classification to the entity > 1. selected Add validity Periods. > 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> > 2020/04/15 10:11:57 > 3. End Time -> from datePicker : *2020/04/15 20:11:57* -> after Apply -> > *2020/04/15 08:11:57* > 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 > 10:11:57 must be before endTime 2020/04/15 08:11:57 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3805) UI:- Basic Search: System Attribute 'typeName' in classification filter, should list classification Names in drop down
[ https://issues.apache.org/jira/browse/ATLAS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3805: --- Attachment: ATLAS-3805.patch > UI:- Basic Search: System Attribute 'typeName' in classification filter, > should list classification Names in drop down > --- > > Key: ATLAS-3805 > URL: https://issues.apache.org/jira/browse/ATLAS-3805 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3805.patch, Screen Shot 2020-05-21 at 12.55.53 > PM.png > > > !Screen Shot 2020-05-21 at 12.55.53 PM.png|width=602,height=342! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3528) UI: Support basic search to search with System attributes only for entity
[ https://issues.apache.org/jira/browse/ATLAS-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17117558#comment-17117558 ] Keval Bhatt commented on ATLAS-3528: Commit id for UI: * master: e202e9e483e41b00dc5309395e5daaa710fb6765 * branch-2.0: 0730a506c93da7120fc3b8af665fda368d67034a > UI: Support basic search to search with System attributes only for entity > -- > > Key: ATLAS-3528 > URL: https://issues.apache.org/jira/browse/ATLAS-3528 > Project: Atlas > Issue Type: Improvement >Reporter: Sameer Shaikh >Assignee: Sameer Shaikh >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3528.patch > > > Support basic search to search with System attributes only for entity: > __guid, __historicalGuids, __labels, __customAttributes, > __classificationsText, > __classificationNames, __propagatedClassificationNames, __isIncomplete -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3482) Enhance basic search to enable search on entity system attributes
[
https://issues.apache.org/jira/browse/ATLAS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17117546#comment-17117546
]
Keval Bhatt commented on ATLAS-3482:
Commit id for UI:
* master: e202e9e483e41b00dc5309395e5daaa710fb6765
* branch-2.0: 0730a506c93da7120fc3b8af665fda368d67034a
> Enhance basic search to enable search on entity system attributes
> -
>
> Key: ATLAS-3482
> URL: https://issues.apache.org/jira/browse/ATLAS-3482
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
> Fix For: 2.1.0
>
>
> System attributes are enabled for entity search via basic search.
> System attributes for both entity and classification:
> __typeName, __state, __createdBy, __modifiedBy, __timestamp,
> __modificationTimestamp
>
> System attributes only for entity:
> __guid, __historicalGuids, __labels, __customAttributes,
> __classificationsText,
> __classificationNames, __propagatedClassificationNames, __isIncomplete
>
> Specific entity type (typeName) can either be present or not. These system
> attributes will work just like normal entity attributes, present in the
> entityFilters. System attributes can be used to search across entity
> types("__ALL_ENTITY_TYPES" should be the value of typeName), note, entity
> attributes should not be included in this case, otherwise, an exception will
> be thrown.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3805) UI:- Basic Search: System Attribute 'typeName' in classification filter, should list classification Names in drop down
[ https://issues.apache.org/jira/browse/ATLAS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3805: --- Description: !Screen Shot 2020-05-21 at 12.55.53 PM.png|width=602,height=342! > UI:- Basic Search: System Attribute 'typeName' in classification filter, > should list classification Names in drop down > --- > > Key: ATLAS-3805 > URL: https://issues.apache.org/jira/browse/ATLAS-3805 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: Screen Shot 2020-05-21 at 12.55.53 PM.png > > > !Screen Shot 2020-05-21 at 12.55.53 PM.png|width=602,height=342! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3805) UI:- Basic Search: System Attribute 'typeName' in classification filter, should list classification Names in drop down
Keval Bhatt created ATLAS-3805: -- Summary: UI:- Basic Search: System Attribute 'typeName' in classification filter, should list classification Names in drop down Key: ATLAS-3805 URL: https://issues.apache.org/jira/browse/ATLAS-3805 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 Attachments: Screen Shot 2020-05-21 at 12.55.53 PM.png -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3805) UI:- Basic Search: System Attribute 'typeName' in classification filter, should list classification Names in drop down
[ https://issues.apache.org/jira/browse/ATLAS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3805: --- Attachment: Screen Shot 2020-05-21 at 12.55.53 PM.png > UI:- Basic Search: System Attribute 'typeName' in classification filter, > should list classification Names in drop down > --- > > Key: ATLAS-3805 > URL: https://issues.apache.org/jira/browse/ATLAS-3805 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: Screen Shot 2020-05-21 at 12.55.53 PM.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3638) [dev-support] Script for updating atlas UI into distro folder
[ https://issues.apache.org/jira/browse/ATLAS-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3638: --- Fix Version/s: (was: 2.1.0) > [dev-support] Script for updating atlas UI into distro folder > - > > Key: ATLAS-3638 > URL: https://issues.apache.org/jira/browse/ATLAS-3638 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3792) New UI: makes it mandate to apply an attribute filter when "Filters" is selected even if the user just wants to select "Show Deleted Entities"
[ https://issues.apache.org/jira/browse/ATLAS-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3792: --- Attachment: ATLAS-3792.patch > New UI: makes it mandate to apply an attribute filter when "Filters" is > selected even if the user just wants to select "Show Deleted Entities" > --- > > Key: ATLAS-3792 > URL: https://issues.apache.org/jira/browse/ATLAS-3792 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3792.patch > > > New UI: makes it mandate to apply an attribute filter when "Filters" is > selected even if the user just wants to select "Show Deleted Entities" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3793) UI: Entity detail page improvement for label, user-define properties, BM panel
[ https://issues.apache.org/jira/browse/ATLAS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3793: --- Attachment: ATLAS-3793.patch > UI: Entity detail page improvement for label, user-define properties, BM panel > -- > > Key: ATLAS-3793 > URL: https://issues.apache.org/jira/browse/ATLAS-3793 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3793.patch > > > * The business metadata section border, sometimes, doesn't wrap the entire > section > * The business metadata accordion icon (arrow) is not collapsed by default, > its correct for labels and user-defined attributes > * When User-defined properties aren't there, then on click of the accordion > expands and shows nothing, we can show "No properties have been created yet. > To add a property, click here" they way its shown if we remove the last > attribute > * Initially, the user-defined properties are empty, if I try to add one, but > cancel it, the save button label doesn't change to "Add". On clicking on save > again changes it back to add, and the notification is shown that attribute > was removed > * While updating user-defined attributes and labels, need a way to cancel > the operation, currently, if a label or attribute is accidentally updated, to > undo the operation, user has to navigate away and come back to the entity, > its there for business metadata attribute section > * Label and BM section border is not uniform -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB
[ https://issues.apache.org/jira/browse/ATLAS-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3795: --- Attachment: ATLAS-3795-1.patch > UI: statistics Memory Section should have suffix like Bytes /KB /MB > --- > > Key: ATLAS-3795 > URL: https://issues.apache.org/jira/browse/ATLAS-3795 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3795-1.patch, ATLAS-3795.patch, > image-2020-05-12-13-20-36-236.png > > > !image-2020-05-12-13-20-36-236.png|width=611,height=391! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3728) UI: Show uploaded data details (status)
[ https://issues.apache.org/jira/browse/ATLAS-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3728: --- Attachment: ATLAS-3728.patch > UI: Show uploaded data details (status) > --- > > Key: ATLAS-3728 > URL: https://issues.apache.org/jira/browse/ATLAS-3728 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3728.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB
[ https://issues.apache.org/jira/browse/ATLAS-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3795: --- Attachment: ATLAS-3795.patch > UI: statistics Memory Section should have suffix like Bytes /KB /MB > --- > > Key: ATLAS-3795 > URL: https://issues.apache.org/jira/browse/ATLAS-3795 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3795.patch, image-2020-05-12-13-20-36-236.png > > > !image-2020-05-12-13-20-36-236.png|width=611,height=391! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3791) New UI: In valid option are visible For _CLASSIFIED , _NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES
[ https://issues.apache.org/jira/browse/ATLAS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3791: --- Attachment: ATLAS-3791.patch > New UI: In valid option are visible For _CLASSIFIED , _NOT_CLASSIFIED, > _ALL_CLASSIFICATION_TYPES > > > Key: ATLAS-3791 > URL: https://issues.apache.org/jira/browse/ATLAS-3791 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3791.patch > > > New UI shows the option to delete, edit, create sub-classification for > _CLASSIFIED , _NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3728) UI: Show uploaded data details (status)
[ https://issues.apache.org/jira/browse/ATLAS-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3728: --- Fix Version/s: 3.0.0 2.1.0 > UI: Show uploaded data details (status) > --- > > Key: ATLAS-3728 > URL: https://issues.apache.org/jira/browse/ATLAS-3728 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB
[ https://issues.apache.org/jira/browse/ATLAS-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3795: --- Attachment: Screen Shot 2020-05-12 at 12.14.38 PM.png > UI: statistics Memory Section should have suffix like Bytes /KB /MB > --- > > Key: ATLAS-3795 > URL: https://issues.apache.org/jira/browse/ATLAS-3795 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-05-12-13-20-36-236.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB
[ https://issues.apache.org/jira/browse/ATLAS-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3795: --- Attachment: (was: Screen Shot 2020-05-12 at 12.14.38 PM.png) > UI: statistics Memory Section should have suffix like Bytes /KB /MB > --- > > Key: ATLAS-3795 > URL: https://issues.apache.org/jira/browse/ATLAS-3795 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-05-12-13-20-36-236.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB
Keval Bhatt created ATLAS-3795: -- Summary: UI: statistics Memory Section should have suffix like Bytes /KB /MB Key: ATLAS-3795 URL: https://issues.apache.org/jira/browse/ATLAS-3795 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 Attachments: image-2020-05-12-13-20-36-236.png -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB
[ https://issues.apache.org/jira/browse/ATLAS-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3795: --- Description: !image-2020-05-12-13-20-36-236.png|width=611,height=391! > UI: statistics Memory Section should have suffix like Bytes /KB /MB > --- > > Key: ATLAS-3795 > URL: https://issues.apache.org/jira/browse/ATLAS-3795 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-05-12-13-20-36-236.png > > > !image-2020-05-12-13-20-36-236.png|width=611,height=391! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB
[ https://issues.apache.org/jira/browse/ATLAS-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3795: --- Attachment: image-2020-05-12-13-20-36-236.png > UI: statistics Memory Section should have suffix like Bytes /KB /MB > --- > > Key: ATLAS-3795 > URL: https://issues.apache.org/jira/browse/ATLAS-3795 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-05-12-13-20-36-236.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3794) New UI: Advance search usablity improvment
Keval Bhatt created ATLAS-3794: -- Summary: New UI: Advance search usablity improvment Key: ATLAS-3794 URL: https://issues.apache.org/jira/browse/ATLAS-3794 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3793) UI: Entity detail page improvement for label, user-define properties, BM panel
[ https://issues.apache.org/jira/browse/ATLAS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3793: --- Summary: UI: Entity detail page improvement for label, user-define properties, BM panel (was: UI: Entity detail page) > UI: Entity detail page improvement for label, user-define properties, BM panel > -- > > Key: ATLAS-3793 > URL: https://issues.apache.org/jira/browse/ATLAS-3793 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3793) UI: Entity detail page
Keval Bhatt created ATLAS-3793: -- Summary: UI: Entity detail page Key: ATLAS-3793 URL: https://issues.apache.org/jira/browse/ATLAS-3793 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3792) New UI: makes it mandate to apply an attribute filter when "Filters" is selected even if the user just wants to select "Show Deleted Entities"
Keval Bhatt created ATLAS-3792:
--
Summary: New UI: makes it mandate to apply an attribute filter
when "Filters" is selected even if the user just wants to select "Show Deleted
Entities"
Key: ATLAS-3792
URL: https://issues.apache.org/jira/browse/ATLAS-3792
Project: Atlas
Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
Fix For: 2.1.0, 3.0.0
New UI: makes it mandate to apply an attribute filter when "Filters" is
selected even if the user just wants to select "Show Deleted Entities"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3791) New UI: In valid option are visible For _CLASSIFIED , _NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES
Keval Bhatt created ATLAS-3791: -- Summary: New UI: In valid option are visible For _CLASSIFIED , _NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES Key: ATLAS-3791 URL: https://issues.apache.org/jira/browse/ATLAS-3791 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 New UI shows the option to delete, edit, create sub-classification for _CLASSIFIED , _NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3789) UI: Date format is not correct for classfication validity periods.
[ https://issues.apache.org/jira/browse/ATLAS-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3789: --- Description: While assigning a classification to the entity 1. selected Add validity Periods. 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 2020/04/15 10:11:57 3. End Time -> from datePicker : *2020/04/15 20:11:57* -> after Apply -> *2020/04/15 08:11:57* 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 10:11:57 must be before endTime 2020/04/15 08:11:57 was: While assigning classification to the entity 1. selected Add validity Periods. 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 2020/04/15 10:11:57 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 2020/04/15 08:11:57 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 10:11:57 must be before endTime 2020/04/15 08:11:57 > UI: Date format is not correct for classfication validity periods. > -- > > Key: ATLAS-3789 > URL: https://issues.apache.org/jira/browse/ATLAS-3789 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > > While assigning a classification to the entity > 1. selected Add validity Periods. > 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> > 2020/04/15 10:11:57 > 3. End Time -> from datePicker : *2020/04/15 20:11:57* -> after Apply -> > *2020/04/15 08:11:57* > 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 > 10:11:57 must be before endTime 2020/04/15 08:11:57 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3789) UI: Date format is not correct for classfication validity periods.
[ https://issues.apache.org/jira/browse/ATLAS-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3789: --- Summary: UI: Date format is not correct for classfication validity periods. (was: UI: Date formating is not correct for classfication validity periods.) > UI: Date format is not correct for classfication validity periods. > -- > > Key: ATLAS-3789 > URL: https://issues.apache.org/jira/browse/ATLAS-3789 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > > While attaching classification to the entity > 1. selected Add validity Periods. > 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> > 2020/04/15 10:11:57 > 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> > 2020/04/15 08:11:57 > 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 > 10:11:57 must be before endTime 2020/04/15 08:11:57 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3789) UI: Date format is not correct for classfication validity periods.
[ https://issues.apache.org/jira/browse/ATLAS-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3789: --- Description: While assigning classification to the entity 1. selected Add validity Periods. 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 2020/04/15 10:11:57 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 2020/04/15 08:11:57 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 10:11:57 must be before endTime 2020/04/15 08:11:57 was: While attaching classification to the entity 1. selected Add validity Periods. 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 2020/04/15 10:11:57 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 2020/04/15 08:11:57 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 10:11:57 must be before endTime 2020/04/15 08:11:57 > UI: Date format is not correct for classfication validity periods. > -- > > Key: ATLAS-3789 > URL: https://issues.apache.org/jira/browse/ATLAS-3789 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > > While assigning classification to the entity > 1. selected Add validity Periods. > 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> > 2020/04/15 10:11:57 > 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> > 2020/04/15 08:11:57 > 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 > 10:11:57 must be before endTime 2020/04/15 08:11:57 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3790) UI: Add Tooltip for Business metadata seachweight
[ https://issues.apache.org/jira/browse/ATLAS-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3790: --- Fix Version/s: 3.0.0 2.1.0 > UI: Add Tooltip for Business metadata seachweight > - > > Key: ATLAS-3790 > URL: https://issues.apache.org/jira/browse/ATLAS-3790 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3790) UI: Add Tooltip for Business metadata seachweight
Keval Bhatt created ATLAS-3790: -- Summary: UI: Add Tooltip for Business metadata seachweight Key: ATLAS-3790 URL: https://issues.apache.org/jira/browse/ATLAS-3790 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3790) UI: Add Tooltip for Business metadata seachweight
[ https://issues.apache.org/jira/browse/ATLAS-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3790: --- Issue Type: Improvement (was: Bug) > UI: Add Tooltip for Business metadata seachweight > - > > Key: ATLAS-3790 > URL: https://issues.apache.org/jira/browse/ATLAS-3790 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3789) UI: Date formating is not correct for classfication validity periods.
[ https://issues.apache.org/jira/browse/ATLAS-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3789: --- Fix Version/s: 3.0.0 2.1.0 > UI: Date formating is not correct for classfication validity periods. > - > > Key: ATLAS-3789 > URL: https://issues.apache.org/jira/browse/ATLAS-3789 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > > While attaching classification to the entity > 1. selected Add validity Periods. > 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> > 2020/04/15 10:11:57 > 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> > 2020/04/15 08:11:57 > 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 > 10:11:57 must be before endTime 2020/04/15 08:11:57 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3789) UI: Date formating is not correct for classfication validity periods.
Keval Bhatt created ATLAS-3789: -- Summary: UI: Date formating is not correct for classfication validity periods. Key: ATLAS-3789 URL: https://issues.apache.org/jira/browse/ATLAS-3789 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt While attaching classification to the entity 1. selected Add validity Periods. 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 2020/04/15 10:11:57 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 2020/04/15 08:11:57 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 10:11:57 must be before endTime 2020/04/15 08:11:57 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3366) UI: Quick Search dropdown entry icon does not match the fallback icon for that entry
[ https://issues.apache.org/jira/browse/ATLAS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3366: --- Attachment: ATLAS-3366.patch > UI: Quick Search dropdown entry icon does not match the fallback icon for > that entry > > > Key: ATLAS-3366 > URL: https://issues.apache.org/jira/browse/ATLAS-3366 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup > Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3366.patch, fallbackquicksearchissue.png > > > When the fallback icon is triggered for a particular entity type, the icon > does not change to that fallback icon for that entity in the quick search > dropdown. See below screenshot. > !fallbackquicksearchissue.png|height=250,width=550! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3774) Typo in authentication docs
[ https://issues.apache.org/jira/browse/ATLAS-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097859#comment-17097859 ] Keval Bhatt commented on ATLAS-3774: [~tartina] [~nixon] do we need this fix in 2.1.0 branch? > Typo in authentication docs > --- > > Key: ATLAS-3774 > URL: https://issues.apache.org/jira/browse/ATLAS-3774 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Guido Aulisi >Priority: Trivial > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Docs about LDAP authentication contain a closing ] instead of a closing}. > See pull request https://github.com/apache/atlas/pull/84 -- This message was sent by Atlassian Jira (v8.3.4#803005)
