[jira] [Updated] (ATLAS-4891) Classification, audits tabs in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4891: --- Issue Type: Task (was: New Feature) > Classification, audits tabs in entity detail page > - > > Key: ATLAS-4891 > URL: https://issues.apache.org/jira/browse/ATLAS-4891 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: > 0001-ATLAS-4891-Atlas-UI-Classification-audits-tabs-in-en.patch > > > Classification, audits in entity detail page > 1)Classification table > 2)Audit table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4891) Classification, audits tabs in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4891: --- Description: Classification, audits in entity detail page 1)Classification table 2)Audit table was: Classification, audits, schema and task tabs in entity detail page 1)Classification table > Classification, audits tabs in entity detail page > - > > Key: ATLAS-4891 > URL: https://issues.apache.org/jira/browse/ATLAS-4891 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Classification, audits in entity detail page > 1)Classification table > 2)Audit table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4891) Classification, audits tabs in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4891: --- Summary: Classification, audits tabs in entity detail page (was: Classification, audits, schema and task tabs in entity detail page) > Classification, audits tabs in entity detail page > - > > Key: ATLAS-4891 > URL: https://issues.apache.org/jira/browse/ATLAS-4891 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Classification, audits, schema and task tabs in entity detail page > 1)Classification table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4892) Export/Import APIs : Unable to import shell entities
[
https://issues.apache.org/jira/browse/ATLAS-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4892:
--
Description:
Exporting shell entities causes failure at Import.
For Hive tables created using spark, there is a chance of shell entities that
can be created in Atlas.
Before the entities could get resolved , if export zip has those entities,
import fails with
{code:java}
2024-04-29 17:12:16,981 ERROR - [etp640294829-283 -
84da4eb4-f1b8-4723-953c-6b86bcf60647:] ~ import(user=hrt_qa,
from=10.19.24.189): failed (ImportService:124)
org.apache.atlas.exception.AtlasBaseException: Invalid instance
creation/updation parameters passed : hive_table.name: mandatory attribute
value missing in type Asset {code}
> Export/Import APIs : Unable to import shell entities
>
>
> Key: ATLAS-4892
> URL: https://issues.apache.org/jira/browse/ATLAS-4892
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Priyanshi Shah
>Assignee: Priyanshi Shah
>Priority: Major
>
> Exporting shell entities causes failure at Import.
> For Hive tables created using spark, there is a chance of shell entities that
> can be created in Atlas.
> Before the entities could get resolved , if export zip has those entities,
> import fails with
> {code:java}
> 2024-04-29 17:12:16,981 ERROR - [etp640294829-283 -
> 84da4eb4-f1b8-4723-953c-6b86bcf60647:] ~ import(user=hrt_qa,
> from=10.19.24.189): failed (ImportService:124)
> org.apache.atlas.exception.AtlasBaseException: Invalid instance
> creation/updation parameters passed : hive_table.name: mandatory attribute
> value missing in type Asset {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4892) Export/Import APIs : Unable to import shell entities
Priyanshi Shah created ATLAS-4892: - Summary: Export/Import APIs : Unable to import shell entities Key: ATLAS-4892 URL: https://issues.apache.org/jira/browse/ATLAS-4892 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 2.3.0, 3.0.0 Reporter: Priyanshi Shah Assignee: Priyanshi Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4891) Classification, audits, schema and task tabs in entity detail page
Brijesh Bhalala created ATLAS-4891: -- Summary: Classification, audits, schema and task tabs in entity detail page Key: ATLAS-4891 URL: https://issues.apache.org/jira/browse/ATLAS-4891 Project: Atlas Issue Type: New Feature Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4887) Detail page module for entities
[ https://issues.apache.org/jira/browse/ATLAS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871058#comment-17871058 ] Brijesh Bhalala commented on ATLAS-4887: Properties & Relationship tabs, attribute listing part done > Detail page module for entities > > > Key: ATLAS-4887 > URL: https://issues.apache.org/jira/browse/ATLAS-4887 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > Detail page module for entities:- > 1)Add Classification Component :- > * Classification Form > * Add Validity Period Module > 2)Add validity Period Component. > 3)Tabs:- >1)Properties module >2)Relationship module. >3)Classification module. >4)Audit module >5)Lineage Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4891) Classification, audits, schema and task tabs in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4891: --- Description: Classification, audits, schema and task tabs in entity detail page 1)Classification table > Classification, audits, schema and task tabs in entity detail page > -- > > Key: ATLAS-4891 > URL: https://issues.apache.org/jira/browse/ATLAS-4891 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Classification, audits, schema and task tabs in entity detail page > 1)Classification table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4890) Properties and Relationship tabs in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4890: --- Attachment: 0001-ATLAS-4890-Atlas-UI-Properties-and-Relationship-tabs.patch > Properties and Relationship tabs in entity detail page > --- > > Key: ATLAS-4890 > URL: https://issues.apache.org/jira/browse/ATLAS-4890 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: > 0001-ATLAS-4890-Atlas-UI-Properties-and-Relationship-tabs.patch > > > Properties and Relationship tabs in entity detail page > 1)Properties tab -> listing attributes details > 2)Relationship tab -> graph and table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4890) Properties and Relationship tabs in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4890: --- Description: Properties and Relationship tabs in entity detail page 1)Properties tab -> listing attributes details 2)Relationship tab -> graph and table was: Properties and Relationship tabs fucntionality in entity detail page 1)Properties tab -> listing attributes details 2)Relationship tab -> graph and table > Properties and Relationship tabs in entity detail page > --- > > Key: ATLAS-4890 > URL: https://issues.apache.org/jira/browse/ATLAS-4890 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Properties and Relationship tabs in entity detail page > 1)Properties tab -> listing attributes details > 2)Relationship tab -> graph and table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4890) Properties and Relationship tabs in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4890: --- Summary: Properties and Relationship tabs in entity detail page (was: Properties and Relationship tabs functionality in entity detail page) > Properties and Relationship tabs in entity detail page > --- > > Key: ATLAS-4890 > URL: https://issues.apache.org/jira/browse/ATLAS-4890 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Properties and Relationship tabs fucntionality in entity detail page > 1)Properties tab -> listing attributes details > 2)Relationship tab -> graph and table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4890) Properties and Relationship tabs functionality in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4890: --- Summary: Properties and Relationship tabs functionality in entity detail page (was: Properties and Relationship tabs fucntionality in entity detail page) > Properties and Relationship tabs functionality in entity detail page > > > Key: ATLAS-4890 > URL: https://issues.apache.org/jira/browse/ATLAS-4890 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Properties and Relationship tabs fucntionality in entity detail page > 1)Properties tab -> listing attributes details > 2)Relationship tab -> graph and table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4890) Properties and Relationship tabs fucntionality in entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871052#comment-17871052 ] Brijesh Bhalala commented on ATLAS-4890: Relationship tabs graph part is pending > Properties and Relationship tabs fucntionality in entity detail page > > > Key: ATLAS-4890 > URL: https://issues.apache.org/jira/browse/ATLAS-4890 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Properties and Relationship tabs fucntionality in entity detail page > 1)Properties tab -> listing attributes details > 2)Relationship tab -> graph and table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4890) Properties and Relationship tabs fucntionality in entity detail page
Brijesh Bhalala created ATLAS-4890: -- Summary: Properties and Relationship tabs fucntionality in entity detail page Key: ATLAS-4890 URL: https://issues.apache.org/jira/browse/ATLAS-4890 Project: Atlas Issue Type: New Feature Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala Properties and Relationship tabs fucntionality in entity detail page 1)Properties tab -> listing attributes details 2)Relationship tab -> graph and table -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4859) NPE during Atlas Import
[
https://issues.apache.org/jira/browse/ATLAS-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4859:
--
Attachment: (was: ATLAS-4859.patch)
> NPE during Atlas Import
> ---
>
> Key: ATLAS-4859
> URL: https://issues.apache.org/jira/browse/ATLAS-4859
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Priyanshi Shah
>Assignee: Priyanshi Shah
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> While doing an incremental import with multiple classifications associated
> with entities it was giving NPE and import was getting failed.
> {code:java}
> 2024-07-23 15:40:31,244 ERROR - [etp370869802-217 -
> cd17f4b8-d164-4bd6-9458-97d3585ae093:] ~ import(user=admin, from=127.0.0.1):
> failed (ImportService:125)
> org.apache.atlas.exception.AtlasBaseException: java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.v2.bulkimport.RegularImport.run(RegularImport.java:137)
> at
> org.apache.atlas.repository.store.graph.v2.BulkImporterImpl.bulkImport(BulkImporterImpl.java:77)
> at
> org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:233)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:120)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:97)
> at
> org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:698)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4859) NPE during Atlas Import
[
https://issues.apache.org/jira/browse/ATLAS-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4859:
--
Attachment: ATLAS-4859.patch
> NPE during Atlas Import
> ---
>
> Key: ATLAS-4859
> URL: https://issues.apache.org/jira/browse/ATLAS-4859
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Priyanshi Shah
>Assignee: Priyanshi Shah
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: ATLAS-4859.patch
>
>
> While doing an incremental import with multiple classifications associated
> with entities it was giving NPE and import was getting failed.
> {code:java}
> 2024-07-23 15:40:31,244 ERROR - [etp370869802-217 -
> cd17f4b8-d164-4bd6-9458-97d3585ae093:] ~ import(user=admin, from=127.0.0.1):
> failed (ImportService:125)
> org.apache.atlas.exception.AtlasBaseException: java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.v2.bulkimport.RegularImport.run(RegularImport.java:137)
> at
> org.apache.atlas.repository.store.graph.v2.BulkImporterImpl.bulkImport(BulkImporterImpl.java:77)
> at
> org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:233)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:120)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:97)
> at
> org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:698)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4889) Incremental export : When an entity has tag propagated and is exported , the tag is not propagated to it in the export.
chaitali borole created ATLAS-4889: -- Summary: Incremental export : When an entity has tag propagated and is exported , the tag is not propagated to it in the export. Key: ATLAS-4889 URL: https://issues.apache.org/jira/browse/ATLAS-4889 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 3.0.0 Reporter: chaitali borole Assignee: chaitali borole STEPS TO REPRODUCE: Create table1 Create lineage CTAS tables of depth 10 ( t1 -> t2 -> t3 . t10) Associate tag tag1 to table1 Export table table10 Import the zip CURRENT BEHAVIOUR: table10 doesn't have the tag associated to the it since the "entityGUID" is of table1's and table1 is not exported EXPECTED BEHAVIOUR: table10 should have tag1 exported -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4851) Search Result table view on search page module
[ https://issues.apache.org/jira/browse/ATLAS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4851: > Search Result table view on search page module > --- > > Key: ATLAS-4851 > URL: https://issues.apache.org/jira/browse/ATLAS-4851 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4851-Atlas-UI-Search-Result-table-view-on-sear.patch > > > * Right Side Content body on landing page includes: - > # Search page Table view. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4874) Custom Filters in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4874: > Custom Filters in left sidebar > -- > > Key: ATLAS-4874 > URL: https://issues.apache.org/jira/browse/ATLAS-4874 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4874-Atlas-UI-Custom-Filters-in-left-sidebar.patch > > > Custom Filters in left sidebar > * Custom Filters tree structure in sidebar > * Filters:- > 1)Show all / type option > 2)Refresh option -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4870) Classification tree structure in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4870: > Classification tree structure in left sidebar > - > > Key: ATLAS-4870 > URL: https://issues.apache.org/jira/browse/ATLAS-4870 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4870-Atlas-UI-Classification-tree-structure-in.patch > > > Classification tree structure in left sidebar > * Classification Tree Structure > * Filters :- >1)Refresh option >2)Show / Hide unused classification >3)Show Flat / Group tree >4)Create Classification >5)Wildcard search -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4873) Relationship module in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4873: > Relationship module in left sidebar > --- > > Key: ATLAS-4873 > URL: https://issues.apache.org/jira/browse/ATLAS-4873 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: > 0001-ATLAS-4873-Atlas-UI-Relationship-module-in-left-side.patch > > > Relationship module in left sidebar > * Relationships in sidebar > * Filters:- >1)Refresh option -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4868) Common Table layout for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4868: > Common Table layout for Atlas New UI > - > > Key: ATLAS-4868 > URL: https://issues.apache.org/jira/browse/ATLAS-4868 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4868-Atlas-UI-Common-Table-layout-for-Atlas-Ne.patch > > > Common Table layout for Atlas New UI > Common Table layout with functionality includes :- > 1)Sorting > 2)Column Show/Hide Options > 3)Row Selection > 4)Column Drag & Drop. > 5)Pagination. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4869) Entities tree structure in Left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4869: > Entities tree structure in Left sidebar > --- > > Key: ATLAS-4869 > URL: https://issues.apache.org/jira/browse/ATLAS-4869 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Entities tree structure in Left sidebar > * Entities Tree Structure > * Filters:- > 1) Refresh option > 2) Show Empty/Non Empty Service type. > 3) Show Flat / Group tree. > 4) Download Import Template > 5) Import Business Metadata -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4872) Glossary in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4872: > Glossary in left sidebar > > > Key: ATLAS-4872 > URL: https://issues.apache.org/jira/browse/ATLAS-4872 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: 0001-ATLAS-4872-Atlas-UI-Glossary-in-left-sidebar.patch > > > Glossary in left sidebar > * Glossary tree structure > * Filters:- > 1)Refresh option > 2)Show Category / Term > 3)Create Glossary option > 4)Download Import Template > 5)Import GLossary Template -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4849) Initial React setup for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4849: > Initial React setup for Atlas New UI > > > Key: ATLAS-4849 > URL: https://issues.apache.org/jira/browse/ATLAS-4849 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > * Initial setup of react for atlas new UI which includes :- > # Dev and Prod env Configuration. > # Folder structure. > # Installation of Libraries in React. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ATLAS-4852) Global Search bar in Header
[ https://issues.apache.org/jira/browse/ATLAS-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reopened ATLAS-4852: > Global Search bar in Header > --- > > Key: ATLAS-4852 > URL: https://issues.apache.org/jira/browse/ATLAS-4852 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4852-Atlas-UI-Global-Search-bar-in-Header.patch > > > Global search at landing page in Header. > * Global search filter for searching Entities. > * Advance & Quick search -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4888) Code Refactor /api/atlas/admin/version
[ https://issues.apache.org/jira/browse/ATLAS-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] VINAYAK MARRAIYA updated ATLAS-4888: Summary: Code Refactor /api/atlas/admin/version (was: /api/atlas/admin/version works only once after atlas restart) > Code Refactor /api/atlas/admin/version > -- > > Key: ATLAS-4888 > URL: https://issues.apache.org/jira/browse/ATLAS-4888 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4888) /api/atlas/admin/version works only once after atlas restart
VINAYAK MARRAIYA created ATLAS-4888: --- Summary: /api/atlas/admin/version works only once after atlas restart Key: ATLAS-4888 URL: https://issues.apache.org/jira/browse/ATLAS-4888 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 2.3.0 Reporter: VINAYAK MARRAIYA -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4888) /api/atlas/admin/version works only once after atlas restart
[ https://issues.apache.org/jira/browse/ATLAS-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] VINAYAK MARRAIYA reassigned ATLAS-4888: --- Assignee: VINAYAK MARRAIYA > /api/atlas/admin/version works only once after atlas restart > > > Key: ATLAS-4888 > URL: https://issues.apache.org/jira/browse/ATLAS-4888 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4859) NPE during Atlas Import
[
https://issues.apache.org/jira/browse/ATLAS-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4859:
--
Attachment: ATLAS-4859.patch
> NPE during Atlas Import
> ---
>
> Key: ATLAS-4859
> URL: https://issues.apache.org/jira/browse/ATLAS-4859
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Priyanshi Shah
>Assignee: Priyanshi Shah
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: ATLAS-4859.patch
>
>
> While doing an incremental import with multiple classifications associated
> with entities it was giving NPE and import was getting failed.
> {code:java}
> 2024-07-23 15:40:31,244 ERROR - [etp370869802-217 -
> cd17f4b8-d164-4bd6-9458-97d3585ae093:] ~ import(user=admin, from=127.0.0.1):
> failed (ImportService:125)
> org.apache.atlas.exception.AtlasBaseException: java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.v2.bulkimport.RegularImport.run(RegularImport.java:137)
> at
> org.apache.atlas.repository.store.graph.v2.BulkImporterImpl.bulkImport(BulkImporterImpl.java:77)
> at
> org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:233)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:120)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:97)
> at
> org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:698)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4859) NPE during Atlas Import
[
https://issues.apache.org/jira/browse/ATLAS-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanshi Shah updated ATLAS-4859:
--
Description:
While doing an incremental import with multiple classifications associated with
entities it was giving NPE and import was getting failed.
{code:java}
2024-07-23 15:40:31,244 ERROR - [etp370869802-217 -
cd17f4b8-d164-4bd6-9458-97d3585ae093:] ~ import(user=admin, from=127.0.0.1):
failed (ImportService:125)
org.apache.atlas.exception.AtlasBaseException: java.lang.NullPointerException
at
org.apache.atlas.repository.store.graph.v2.bulkimport.RegularImport.run(RegularImport.java:137)
at
org.apache.atlas.repository.store.graph.v2.BulkImporterImpl.bulkImport(BulkImporterImpl.java:77)
at
org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:233)
at
org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:120)
at
org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:97)
at
org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:698)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
{code}
> NPE during Atlas Import
> ---
>
> Key: ATLAS-4859
> URL: https://issues.apache.org/jira/browse/ATLAS-4859
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Priyanshi Shah
>Assignee: Priyanshi Shah
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> While doing an incremental import with multiple classifications associated
> with entities it was giving NPE and import was getting failed.
> {code:java}
> 2024-07-23 15:40:31,244 ERROR - [etp370869802-217 -
> cd17f4b8-d164-4bd6-9458-97d3585ae093:] ~ import(user=admin, from=127.0.0.1):
> failed (ImportService:125)
> org.apache.atlas.exception.AtlasBaseException: java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.v2.bulkimport.RegularImport.run(RegularImport.java:137)
> at
> org.apache.atlas.repository.store.graph.v2.BulkImporterImpl.bulkImport(BulkImporterImpl.java:77)
> at
> org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:233)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:120)
> at
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:97)
> at
> org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:698)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- 1. Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. 6.Detail page module for entities:- 1)Add Classification Component :- Classification Form Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- 1. Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. 6.Detail page module for entities:- 1)Add Classification Component :- Classification Form Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Tasks :- > 1. Initial React Setup :- > * Dev and Prod env Configuration. > * Folder structure. > * Installation of Libraries in React. > 2. Left Sidebar Layout :- > * Tree Structure and Search Bar. > 3. Common Table Layout :- > * Common table layout. > * Table Functionalities :- > a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column > Show/Hide Functionalities > 4. Table View on search page :- > * Search page Table view. > * Query Builder. > 5. Global Search Bar on Header :- > * Global search bar for entities search. > * Advance & Quick Search. > 6.Detail page module for entities:- > 1)Add Classification Component :- > Classification Form > Add Validity Period Module > 2)Add validity Period Component. > 3)Tabs:- > 1)Properties module > 2)Relationship module. > 3)Classification module. > 4)Audit module > 5)Lineage Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- 1. Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. 6.Detail page module for entities:- 1)Add Classification Component :- Classification Form Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. 6.Detail page module for entities:- 1)Add Classification Component :- Classification Form Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Tasks :- > 1. Initial React Setup :- > * Dev and Prod env Configuration. > * Folder structure. > * Installation of Libraries in React. > 2. Left Sidebar Layout :- > * Tree Structure and Search Bar. > 3. Common Table Layout :- > * Common table layout. > * Table Functionalities :- > a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column > Show/Hide Functionalities > 4. Table View on search page :- > * Search page Table view. > * Query Builder. > 5. Global Search Bar on Header :- > * Global search bar for entities search. > * Advance & Quick Search. > 6.Detail page module for entities:- > 1)Add Classification Component :- > Classification Form > Add Validity Period Module > 2)Add validity Period Component. > 3)Tabs:- > 1)Properties module > 2)Relationship module. > 3)Classification module. > 4)Audit module > 5)Lineage Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. 6.Detail page module for entities:- 1)Add Classification Component :- Classification Form Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Tasks :- > # Initial React Setup :- > * Dev and Prod env Configuration. > * Folder structure. > * Installation of Libraries in React. > 2. Left Sidebar Layout :- > * Tree Structure and Search Bar. > 3. Common Table Layout :- > * Common table layout. > * Table Functionalities :- > a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, > e)Column Show/Hide Functionalities > 4. Table View on search page :- > * Search page Table view. > * Query Builder. > 5. Global Search Bar on Header :- > * Global search bar for entities search. > * Advance & Quick Search. > 6.Detail page module for entities:- > 1)Add Classification Component :- > Classification Form > Add Validity Period Module > 2)Add validity Period Component. > 3)Tabs:- > 1)Properties module > 2)Relationship module. > 3)Classification module. > 4)Audit module > 5)Lineage Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4887) Detail page module for entities
[ https://issues.apache.org/jira/browse/ATLAS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4887: --- Description: Detail page module for entities:- 1)Add Classification Component :- * Classification Form * Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module was: Detail page module for entities:- 1)Add Classification Component :- * Classification Form * Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module > Detail page module for entities > > > Key: ATLAS-4887 > URL: https://issues.apache.org/jira/browse/ATLAS-4887 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > Detail page module for entities:- > 1)Add Classification Component :- > * Classification Form > * Add Validity Period Module > 2)Add validity Period Component. > 3)Tabs:- >1)Properties module >2)Relationship module. >3)Classification module. >4)Audit module >5)Lineage Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. 6.Detail page module for entities:- 1)Add Classification Component :- Classification Form Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. 6.Detail page module for entities:- 1)Add Classification Component :- Classification Form Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Tasks :- > # Initial React Setup :- > * Dev and Prod env Configuration. > * Folder structure. > * Installation of Libraries in React. > 2. Left Sidebar Layout :- > * Tree Structure and Search Bar. >3. Common Table Layout :- > * Common table layout. > * Table Functionalities :- > a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, > e)Column Show/Hide Functionalities > 4. Table View on search page :- > * Search page Table view. > * Query Builder. > 5. Global Search Bar on Header :- > * Global search bar for entities search. > * Advance & Quick Search. > 6.Detail page module for entities:- > 1)Add Classification Component :- > Classification Form > Add Validity Period Module > 2)Add validity Period Component. > 3)Tabs:- > 1)Properties module > 2)Relationship module. > 3)Classification module. > 4)Audit module > 5)Lineage Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4887) Detail page module for entities
[ https://issues.apache.org/jira/browse/ATLAS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4887: --- Description: Detail page module for entities:- 1)Add Classification Component :- * Classification Form * Add Validity Period Module 2)Add validity Period Component. 3)Tabs:- 1)Properties module 2)Relationship module. 3)Classification module. 4)Audit module 5)Lineage Module was: 1)Add Classification :- 1)Classification Form 2)Add Vailidity Period Module > Detail page module for entities > > > Key: ATLAS-4887 > URL: https://issues.apache.org/jira/browse/ATLAS-4887 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > Detail page module for entities:- > 1)Add Classification Component :- > * Classification Form > * Add Validity Period Module > 2)Add validity Period Component. > 3)Tabs:- >1)Properties module >2)Relationship module. >3)Classification module. >4)Audit module >5)Lineage Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4887) Detail page module for entities
[ https://issues.apache.org/jira/browse/ATLAS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4887: --- Labels: atlas-react (was: ) > Detail page module for entities > > > Key: ATLAS-4887 > URL: https://issues.apache.org/jira/browse/ATLAS-4887 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4887) Detail page module for entities
[ https://issues.apache.org/jira/browse/ATLAS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4887: --- Description: 1)Add Classification :- 1)Classification Form 2)Add Vailidity Period Module > Detail page module for entities > > > Key: ATLAS-4887 > URL: https://issues.apache.org/jira/browse/ATLAS-4887 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > 1)Add Classification :- >1)Classification Form >2)Add Vailidity Period Module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4887) Detail page module for entities
[ https://issues.apache.org/jira/browse/ATLAS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reassigned ATLAS-4887: -- Assignee: Brijesh Bhalala > Detail page module for entities > > > Key: ATLAS-4887 > URL: https://issues.apache.org/jira/browse/ATLAS-4887 > Project: Atlas > Issue Type: Sub-task >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4887) Detail page module for entities
[ https://issues.apache.org/jira/browse/ATLAS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4887: --- Component/s: atlas-webui > Detail page module for entities > > > Key: ATLAS-4887 > URL: https://issues.apache.org/jira/browse/ATLAS-4887 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4887) Detail page module for entities
Brijesh Bhalala created ATLAS-4887: -- Summary: Detail page module for entities Key: ATLAS-4887 URL: https://issues.apache.org/jira/browse/ATLAS-4887 Project: Atlas Issue Type: Sub-task Reporter: Brijesh Bhalala -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4852) Global Search bar in Header
[ https://issues.apache.org/jira/browse/ATLAS-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4852: --- Attachment: 0001-ATLAS-4852-Atlas-UI-Global-Search-bar-in-Header.patch > Global Search bar in Header > --- > > Key: ATLAS-4852 > URL: https://issues.apache.org/jira/browse/ATLAS-4852 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4852-Atlas-UI-Global-Search-bar-in-Header.patch > > > Global search at landing page in Header. > * Global search filter for searching Entities. > * Advance & Quick search -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4886) Need to add fields to the response of utility to analyze hook notifications
[ https://issues.apache.org/jira/browse/ATLAS-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned ATLAS-4886: - Assignee: Prashant Satam > Need to add fields to the response of utility to analyze hook notifications > --- > > Key: ATLAS-4886 > URL: https://issues.apache.org/jira/browse/ATLAS-4886 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4886-Need-to-add-fields-to-the-response-of-uti.patch > > > Need to add time related fields to the response of utility like > startTime,endTime,duration > startTime = It is message creation time of the first message received from > the hook > endTime = It is message creation time of the last message received from the > hook > duration = It is the difference between the startTime and endTime -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ATLAS-4886) Need to add fields to the response of utility to analyze hook notifications
[ https://issues.apache.org/jira/browse/ATLAS-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866685#comment-17866685 ] Prashant Satam edited comment on ATLAS-4886 at 7/17/24 10:29 AM: - Review Request > [https://reviews.apache.org/r/75092/|https://reviews.apache.org/r/75092/diff/1#index_header] was (Author: JIRAUSER300185): Review Request > https://reviews.apache.org/r/75092/diff/1#index_header > Need to add fields to the response of utility to analyze hook notifications > --- > > Key: ATLAS-4886 > URL: https://issues.apache.org/jira/browse/ATLAS-4886 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Prashant Satam >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4886-Need-to-add-fields-to-the-response-of-uti.patch > > > Need to add time related fields to the response of utility like > startTime,endTime,duration > startTime = It is message creation time of the first message received from > the hook > endTime = It is message creation time of the last message received from the > hook > duration = It is the difference between the startTime and endTime -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4886) Need to add fields to the response of utility to analyze hook notifications
[ https://issues.apache.org/jira/browse/ATLAS-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated ATLAS-4886: -- Attachment: (was: 0001-ATLAS-4886-Need-to-add-fields-to-the-response-of-uti.patch) > Need to add fields to the response of utility to analyze hook notifications > --- > > Key: ATLAS-4886 > URL: https://issues.apache.org/jira/browse/ATLAS-4886 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Prashant Satam >Priority: Major > Fix For: 3.0.0 > > > Need to add time related fields to the response of utility like > startTime,endTime,duration > startTime = It is message creation time of the first message received from > the hook > endTime = It is message creation time of the last message received from the > hook > duration = It is the difference between the startTime and endTime -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4886) Need to add fields to the response of utility to analyze hook notifications
[ https://issues.apache.org/jira/browse/ATLAS-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated ATLAS-4886: -- Attachment: 0001-ATLAS-4886-Need-to-add-fields-to-the-response-of-uti.patch > Need to add fields to the response of utility to analyze hook notifications > --- > > Key: ATLAS-4886 > URL: https://issues.apache.org/jira/browse/ATLAS-4886 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Prashant Satam >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4886-Need-to-add-fields-to-the-response-of-uti.patch > > > Need to add time related fields to the response of utility like > startTime,endTime,duration > startTime = It is message creation time of the first message received from > the hook > endTime = It is message creation time of the last message received from the > hook > duration = It is the difference between the startTime and endTime -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4886) Need to add fields to the response of utility to analyze hook notifications
[ https://issues.apache.org/jira/browse/ATLAS-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated ATLAS-4886: -- Description: Need to add time related fields to the response of utility like startTime,endTime,duration startTime = It is message creation time of the first message received from the hook endTime = It is message creation time of the last message received from the hook duration = It is the difference between the startTime and endTime > Need to add fields to the response of utility to analyze hook notifications > --- > > Key: ATLAS-4886 > URL: https://issues.apache.org/jira/browse/ATLAS-4886 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Prashant Satam >Priority: Major > Fix For: 3.0.0 > > > Need to add time related fields to the response of utility like > startTime,endTime,duration > startTime = It is message creation time of the first message received from > the hook > endTime = It is message creation time of the last message received from the > hook > duration = It is the difference between the startTime and endTime -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4886) Need to add fields to the response of utility to analyze hook notifications
Prashant Satam created ATLAS-4886: - Summary: Need to add fields to the response of utility to analyze hook notifications Key: ATLAS-4886 URL: https://issues.apache.org/jira/browse/ATLAS-4886 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Prashant Satam Fix For: 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4874) Custom Filters in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4874: --- Attachment: 0001-ATLAS-4874-Atlas-UI-Custom-Filters-in-left-sidebar.patch > Custom Filters in left sidebar > -- > > Key: ATLAS-4874 > URL: https://issues.apache.org/jira/browse/ATLAS-4874 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4874-Atlas-UI-Custom-Filters-in-left-sidebar.patch > > > Custom Filters in left sidebar > * Custom Filters tree structure in sidebar > * Filters:- > 1)Show all / type option > 2)Refresh option -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4873) Relationship module in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4873: --- Attachment: 0001-ATLAS-4873-Atlas-UI-Relationship-module-in-left-side.patch > Relationship module in left sidebar > --- > > Key: ATLAS-4873 > URL: https://issues.apache.org/jira/browse/ATLAS-4873 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: > 0001-ATLAS-4873-Atlas-UI-Relationship-module-in-left-side.patch > > > Relationship module in left sidebar > * Relationships in sidebar > * Filters:- >1)Refresh option -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4872) Glossary in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864913#comment-17864913 ] Brijesh Bhalala commented on ATLAS-4872: Create Glossary option will be handling in another JIRA > Glossary in left sidebar > > > Key: ATLAS-4872 > URL: https://issues.apache.org/jira/browse/ATLAS-4872 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: 0001-ATLAS-4872-Atlas-UI-Glossary-in-left-sidebar.patch > > > Glossary in left sidebar > * Glossary tree structure > * Filters:- > 1)Refresh option > 2)Show Category / Term > 3)Create Glossary option > 4)Download Import Template > 5)Import GLossary Template -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4872) Glossary in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4872: --- Attachment: 0001-ATLAS-4872-Atlas-UI-Glossary-in-left-sidebar.patch > Glossary in left sidebar > > > Key: ATLAS-4872 > URL: https://issues.apache.org/jira/browse/ATLAS-4872 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: 0001-ATLAS-4872-Atlas-UI-Glossary-in-left-sidebar.patch > > > Glossary in left sidebar > * Glossary tree structure > * Filters:- > 1)Refresh option > 2)Show Category / Term > 3)Create Glossary option > 4)Download Import Template > 5)Import GLossary Template -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4871) Business Metadata in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4871: --- Attachment: 0001-ATLAS-4871-Atlas-UI-Business-Metadata-in-left-sideba.patch > Business Metadata in left sidebar > - > > Key: ATLAS-4871 > URL: https://issues.apache.org/jira/browse/ATLAS-4871 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: > 0001-ATLAS-4871-Atlas-UI-Business-Metadata-in-left-sideba.patch > > > Business Metadata in left sidebar > * Business metadata tree structrue > * Filters:- > 1)Refresh option > 2)Business metadata page link -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4870) Classification tree structure in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863733#comment-17863733 ] Brijesh Bhalala commented on ATLAS-4870: Create Classification will be handle in another jira > Classification tree structure in left sidebar > - > > Key: ATLAS-4870 > URL: https://issues.apache.org/jira/browse/ATLAS-4870 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4870-Atlas-UI-Classification-tree-structure-in.patch > > > Classification tree structure in left sidebar > * Classification Tree Structure > * Filters :- >1)Refresh option >2)Show / Hide unused classification >3)Show Flat / Group tree >4)Create Classification >5)Wildcard search -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4870) Classification tree structure in left sidebar
[ https://issues.apache.org/jira/browse/ATLAS-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4870: --- Attachment: 0001-ATLAS-4870-Atlas-UI-Classification-tree-structure-in.patch > Classification tree structure in left sidebar > - > > Key: ATLAS-4870 > URL: https://issues.apache.org/jira/browse/ATLAS-4870 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4870-Atlas-UI-Classification-tree-structure-in.patch > > > Classification tree structure in left sidebar > * Classification Tree Structure > * Filters :- >1)Refresh option >2)Show / Hide unused classification >3)Show Flat / Group tree >4)Create Classification >5)Wildcard search -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4884) approximateCount confused
[
https://issues.apache.org/jira/browse/ATLAS-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863122#comment-17863122
]
Pinal Shah commented on ATLAS-4884:
---
[~zhangminguang]
# While using `__customAttribute` in basic search filter, approximateCount is
incorrect, it is a bug, i have created ticket ATLAS-4885, will fix in a day
# For your usecase regarding custom entity type and filtering it with its
attribute, it is possible to search through DSL. but filtering through
`__customAttributes`(UserDefined Attributes) is not supported in DSL
> approximateCount confused
> -
>
> Key: ATLAS-4884
> URL: https://issues.apache.org/jira/browse/ATLAS-4884
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: MinGuang Zhang
>Priority: Major
> Attachments: image-2024-06-26-11-58-18-440.png,
> image-2024-06-26-11-58-50-435.png
>
>
> atlas should return search result total exactly when user post some search
> Conditions, like query string and filter. Is using approximateCount as
> total? but approximateCount make me confused.
> a general scene： i want the total of search result for page i one request.
> but now i should recall api to add limit (eg: 10+) .
> the bad way: to reduce paramaters for get all and return hurge data for
> calculate.
>
> {*}Problem 1{*}:
> the response of post "/search/basic" api.
> see picture1 , i'm not add filter and set search text to find the hive_table
> contains my custom attributes, the approximateCount is correct。 by the way,
> is DSL support find __customAttribute?? how to do?
> picture 1:
> !image-2024-06-26-11-58-18-440.png!
>
> see picture2, i'm add filter and not set search text, the approximateCount
> is incorrect。 i see the correct total is 11 one by one.
> picture2
> !image-2024-06-26-11-58-50-435.png!
> also i can't using the entities size for work when the limit paramters
> changed.
> so how to search use defined attribute for work? use filter or fullText
> search? and is a bug? or need some total variable？
>
> {*}Problem 2{*}:
> Use-defined propertiies can help business . can support dsl search it ? any
> discuss will help me.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ATLAS-4884) approximateCount confused
[
https://issues.apache.org/jira/browse/ATLAS-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862981#comment-17862981
]
MinGuang Zhang edited comment on ATLAS-4884 at 7/4/24 9:33 AM:
---
[~madhan] - In my understanding, atlas works as a type system. User can use
atlas to build their system as metadata store, define new type and entity
convenient for their their business system Bill Management、Staff Management ...
and finally metadata stored in atlas.
For those use case, user will be more concern their user defined properties.
like bill_total, paid_tax, staff_working_years ...
So an convenient and brief user defined properties search in DSL will be very
useful.
Maybe like this or some tips:
{code:java}
>From Bill where _cust_bill_total > 20 and _cust_paid_tax < 3 {code}
was (Author: JIRAUSER305972):
[~madhan] - In my understanding, atlas works as a type system. User can use
atlas to build their system as metadata store, define new type and entity
convenient for their their business system Bill Management、Staff Management ...
and finally metadata stored in atlas.
For those use case, user will be more concern their user defined properties.
like bill_total, paid_tax, staff_working_years ...
So an convenient and brief user defined properties search in DSL will be very
useful.
Maybe like this or some tips:
{code:java}
>From Bill where __bill_total > 20 and __paid_tax < 3 {code}
> approximateCount confused
> -
>
> Key: ATLAS-4884
> URL: https://issues.apache.org/jira/browse/ATLAS-4884
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: MinGuang Zhang
>Priority: Major
> Attachments: image-2024-06-26-11-58-18-440.png,
> image-2024-06-26-11-58-50-435.png
>
>
> atlas should return search result total exactly when user post some search
> Conditions, like query string and filter. Is using approximateCount as
> total? but approximateCount make me confused.
> a general scene： i want the total of search result for page i one request.
> but now i should recall api to add limit (eg: 10+) .
> the bad way: to reduce paramaters for get all and return hurge data for
> calculate.
>
> {*}Problem 1{*}:
> the response of post "/search/basic" api.
> see picture1 , i'm not add filter and set search text to find the hive_table
> contains my custom attributes, the approximateCount is correct。 by the way,
> is DSL support find __customAttribute?? how to do?
> picture 1:
> !image-2024-06-26-11-58-18-440.png!
>
> see picture2, i'm add filter and not set search text, the approximateCount
> is incorrect。 i see the correct total is 11 one by one.
> picture2
> !image-2024-06-26-11-58-50-435.png!
> also i can't using the entities size for work when the limit paramters
> changed.
> so how to search use defined attribute for work? use filter or fullText
> search? and is a bug? or need some total variable？
>
> {*}Problem 2{*}:
> Use-defined propertiies can help business . can support dsl search it ? any
> discuss will help me.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4884) approximateCount confused
[
https://issues.apache.org/jira/browse/ATLAS-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862981#comment-17862981
]
MinGuang Zhang commented on ATLAS-4884:
---
[~madhan] - In my understanding, atlas works as a type system. User can use
atlas to build their system as metadata store, define new type and entity
convenient for their their business system Bill Management、Staff Management ...
and finally metadata stored in atlas.
For those use case, user will be more concern their user defined properties.
like bill_total, paid_tax, staff_working_years ...
So an convenient and brief user defined properties search in DSL will be very
useful.
Maybe like this or some tips:
{code:java}
>From Bill where __bill_total > 20 and __paid_tax < 3 {code}
> approximateCount confused
> -
>
> Key: ATLAS-4884
> URL: https://issues.apache.org/jira/browse/ATLAS-4884
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: MinGuang Zhang
>Priority: Major
> Attachments: image-2024-06-26-11-58-18-440.png,
> image-2024-06-26-11-58-50-435.png
>
>
> atlas should return search result total exactly when user post some search
> Conditions, like query string and filter. Is using approximateCount as
> total? but approximateCount make me confused.
> a general scene： i want the total of search result for page i one request.
> but now i should recall api to add limit (eg: 10+) .
> the bad way: to reduce paramaters for get all and return hurge data for
> calculate.
>
> {*}Problem 1{*}:
> the response of post "/search/basic" api.
> see picture1 , i'm not add filter and set search text to find the hive_table
> contains my custom attributes, the approximateCount is correct。 by the way,
> is DSL support find __customAttribute?? how to do?
> picture 1:
> !image-2024-06-26-11-58-18-440.png!
>
> see picture2, i'm add filter and not set search text, the approximateCount
> is incorrect。 i see the correct total is 11 one by one.
> picture2
> !image-2024-06-26-11-58-50-435.png!
> also i can't using the entities size for work when the limit paramters
> changed.
> so how to search use defined attribute for work? use filter or fullText
> search? and is a bug? or need some total variable？
>
> {*}Problem 2{*}:
> Use-defined propertiies can help business . can support dsl search it ? any
> discuss will help me.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4885) Basic Search : not using index-search for Userdefined attributes
Pinal Shah created ATLAS-4885:
-
Summary: Basic Search : not using index-search for Userdefined
attributes
Key: ATLAS-4885
URL: https://issues.apache.org/jira/browse/ATLAS-4885
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
While searching through basic search having filter for userdefined attribute,
getting below warning log
{code:java}
not using index-search for attribute '__customAttributes'; might cause poor
performance (SearchProcessor:337)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4884) approximateCount confused
[
https://issues.apache.org/jira/browse/ATLAS-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17861337#comment-17861337
]
Madhan Neethiraj commented on ATLAS-4884:
-
[~zhangminguang] - {{approximateCount}} is not a good name; I think
{{estimatedCount}} would have been a better name. Per pic2, the result only
contains 11 entries, so approximateCount shouldn't be 22. [~pinal] - can you
please help here?
Support for business metadata in DSL - should be a straightforward enhancement.
Can you please add couple of use cases?
> approximateCount confused
> -
>
> Key: ATLAS-4884
> URL: https://issues.apache.org/jira/browse/ATLAS-4884
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: MinGuang Zhang
>Priority: Major
> Attachments: image-2024-06-26-11-58-18-440.png,
> image-2024-06-26-11-58-50-435.png
>
>
> atlas should return search result total exactly when user post some search
> Conditions, like query string and filter. Is using approximateCount as
> total? but approximateCount make me confused.
> a general scene： i want the total of search result for page i one request.
> but now i should recall api to add limit (eg: 10+) .
> the bad way: to reduce paramaters for get all and return hurge data for
> calculate.
>
> {*}Problem 1{*}:
> the response of post "/search/basic" api.
> see picture1 , i'm not add filter and set search text to find the hive_table
> contains my custom attributes, the approximateCount is correct。 by the way,
> is DSL support find __customAttribute?? how to do?
> picture 1:
> !image-2024-06-26-11-58-18-440.png!
>
> see picture2, i'm add filter and not set search text, the approximateCount
> is incorrect。 i see the correct total is 11 one by one.
> picture2
> !image-2024-06-26-11-58-50-435.png!
> also i can't using the entities size for work when the limit paramters
> changed.
> so how to search use defined attribute for work? use filter or fullText
> search? and is a bug? or need some total variable？
>
> {*}Problem 2{*}:
> Use-defined propertiies can help business . can support dsl search it ? any
> discuss will help me.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4851) Search Result table view on search page module
[ https://issues.apache.org/jira/browse/ATLAS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4851: --- Attachment: 0001-ATLAS-4851-Atlas-UI-Search-Result-table-view-on-sear.patch > Search Result table view on search page module > --- > > Key: ATLAS-4851 > URL: https://issues.apache.org/jira/browse/ATLAS-4851 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4851-Atlas-UI-Search-Result-table-view-on-sear.patch > > > * Right Side Content body on landing page includes: - > # Search page Table view. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4851) Search Result table view on search page module
[ https://issues.apache.org/jira/browse/ATLAS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala resolved ATLAS-4851. Resolution: Fixed > Search Result table view on search page module > --- > > Key: ATLAS-4851 > URL: https://issues.apache.org/jira/browse/ATLAS-4851 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4851-Atlas-UI-Search-Result-table-view-on-sear.patch > > > * Right Side Content body on landing page includes: - > # Search page Table view. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4884) approximateCount confused
MinGuang Zhang created ATLAS-4884:
-
Summary: approximateCount confused
Key: ATLAS-4884
URL: https://issues.apache.org/jira/browse/ATLAS-4884
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.1.0
Reporter: MinGuang Zhang
Attachments: image-2024-06-26-11-58-18-440.png,
image-2024-06-26-11-58-50-435.png
atlas should return search result total exactly when user post some search
Conditions, like query string and filter. Is using approximateCount as total?
but approximateCount make me confused.
a general scene： i want the total of search result for page i one request. but
now i should recall api to add limit (eg: 10+) .
the bad way: to reduce paramaters for get all and return hurge data for
calculate.
{*}Problem 1{*}:
the response of post "/search/basic" api.
see picture1 , i'm not add filter and set search text to find the hive_table
contains my custom attributes, the approximateCount is correct。 by the way, is
DSL support find __customAttribute?? how to do?
picture 1:
!image-2024-06-26-11-58-18-440.png!
see picture2, i'm add filter and not set search text, the approximateCount is
incorrect。 i see the correct total is 11 one by one.
picture2
!image-2024-06-26-11-58-50-435.png!
also i can't using the entities size for work when the limit paramters changed.
so how to search use defined attribute for work? use filter or fullText search?
and is a bug? or need some total variable？
{*}Problem 2{*}:
Use-defined propertiies can help business . can support dsl search it ? any
discuss will help me.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4883) Atlas UI CSRF token error
Paresh Devalia created ATLAS-4883: - Summary: Atlas UI CSRF token error Key: ATLAS-4883 URL: https://issues.apache.org/jira/browse/ATLAS-4883 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Assignee: Paresh Devalia Attachments: 1-_Atlas_webUI_with_error.png, 2-_Atlas_webUI_with_error.png => Customer is facing issues , as sometimes the basic search is not working and the error: + Missing header or invalid Header value for CSRF Vulnerability Protection + is coming up intermittently on the right corner of the WebUI. Please refer to the screenshots attached to the Jira - Dev analysis steps to reproduce # Set the session-timeout to 1 min in web.xml file. # Wait for 1 min after Atlas login. # Do basic search and response will get as 400 error code with Missing header or invalid Header value for CSRF Vulnerability Protection. # Also while doing metric API (Statistics) call we get the 409 error code and it redirect to login page. Which should be a correct way. As the sever-side session get timed-out and user was in-active. so it get 400 error code. Fix will provide redirection to login-page or any other solution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4883) Atlas UI CSRF token error
[ https://issues.apache.org/jira/browse/ATLAS-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4883: -- Attachment: 1-_Atlas_webUI_with_error.png 2-_Atlas_webUI_with_error.png > Atlas UI CSRF token error > - > > Key: ATLAS-4883 > URL: https://issues.apache.org/jira/browse/ATLAS-4883 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > Attachments: 1-_Atlas_webUI_with_error.png, > 2-_Atlas_webUI_with_error.png > > > => Customer is facing issues , as sometimes the basic search is not working > and the error: > + > Missing header or invalid Header value for CSRF Vulnerability Protection > + > is coming up intermittently on the right corner of the WebUI. > Please refer to the screenshots attached to the Jira > > - > Dev analysis > steps to reproduce > # Set the session-timeout to 1 min in web.xml file. > # Wait for 1 min after Atlas login. > # Do basic search and response will get as 400 error code with Missing > header or invalid Header value for CSRF Vulnerability Protection. > # Also while doing metric API (Statistics) call we get the 409 error code > and it redirect to login page. Which should be a correct way. > As the sever-side session get timed-out and user was in-active. so it get 400 > error code. > Fix will provide redirection to login-page or any other solution. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859551#comment-17859551
]
ASF subversion and git services commented on ATLAS-4882:
Commit c0858a883f87b87fc57a9160234286e35b0f16ec in atlas's branch
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c0858a883 ]
ATLAS-4882: Export/Import: Export exits with 'Found 0 entities'
Signed-off-by: Pinal Shah
> Export/Import: Export exits with "Found 0 entities"
>
>
> Key: ATLAS-4882
> URL: https://issues.apache.org/jira/browse/ATLAS-4882
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> *Issue:*
> Export during ingestion fails giving Found 0 entities in the logs
> Ingestion meaning Atlas is consuming messages
> *Steps to Repro:*
> * Make sure backend has above 1M entities
> * Start creating tables under `db1@cm`
> * Start export for `db1@cm`
> *
> {code:java}
> curl -v -X POST -u admin:admin -H "Content-Type: application/json"
> "http://<>/api/atlas/admin/export" -d
> '{"itemsToExport":[{"typeName":"hive_db","uniqueAttributes": {
> "qualifiedName": "db1@cm"
> }}],"options":{"fetchType":"full","replicatedTo":"cm"}} > export1.zip{code}
> * It fails after sometime.
> *When is the issue seen?*
> It occurs when there is huge amount of data in backend and Atlas is consuming
> messages linked to entity of which export is running
> *Analysis to find Root cause:*
> * when there is huge amount of data in backend, export FAILS
> * when there is huge amount of data in backend but less tables under it,
> then also export FAILS
> * if background consumption stops, export PASS
> * if consumption is of different entities then requested in export, export
> PASS
> * export query to find starting object uses below query, where has clause to
> check property is expensive
> {code:java}
> g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
> - has('__guid') queries solr [(35x_t <> null)]:vertex_index
> - below is the timetaken in the solr logs
> {code:java}
> 2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1681928 status=0 QTime=4227
> 2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1682086 status=0 QTime=787
> 2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1682216 status=0 QTime=1962
> 2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1682363 status=0 QTime=4465 {code}
> - ran same query through gremlin shell while ingestion is happening it
> doesn't fail
> - time taken for above gremlin query in code when ingestion
> : 214825ms
> - time takem for above gremlin query in gremlin shell when ingestion :
> 104641ms
> - time taken for above gremlin query when no ingestion
> : 181682ms
> Still Root cause is unknown
> *WorkAround:*
> - Remove .has('__guid') clause from below, it is very quick and issue is not
> reproducible.
> {code:java}
> g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
> *Tests:*
> * upgrded tinkerpop and janusgraph version but didn't help
> * invalid property doesn't throw any exception or not existence of property
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859550#comment-17859550
]
ASF subversion and git services commented on ATLAS-4882:
Commit e9a36e75bc220d7957dd0c1963d74e25d002812d in atlas's branch
refs/heads/master from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e9a36e75b ]
ATLAS-4882: Export/Import: Export exits with 'Found 0 entities'
Signed-off-by: Pinal Shah
> Export/Import: Export exits with "Found 0 entities"
>
>
> Key: ATLAS-4882
> URL: https://issues.apache.org/jira/browse/ATLAS-4882
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> *Issue:*
> Export during ingestion fails giving Found 0 entities in the logs
> Ingestion meaning Atlas is consuming messages
> *Steps to Repro:*
> * Make sure backend has above 1M entities
> * Start creating tables under `db1@cm`
> * Start export for `db1@cm`
> *
> {code:java}
> curl -v -X POST -u admin:admin -H "Content-Type: application/json"
> "http://<>/api/atlas/admin/export" -d
> '{"itemsToExport":[{"typeName":"hive_db","uniqueAttributes": {
> "qualifiedName": "db1@cm"
> }}],"options":{"fetchType":"full","replicatedTo":"cm"}} > export1.zip{code}
> * It fails after sometime.
> *When is the issue seen?*
> It occurs when there is huge amount of data in backend and Atlas is consuming
> messages linked to entity of which export is running
> *Analysis to find Root cause:*
> * when there is huge amount of data in backend, export FAILS
> * when there is huge amount of data in backend but less tables under it,
> then also export FAILS
> * if background consumption stops, export PASS
> * if consumption is of different entities then requested in export, export
> PASS
> * export query to find starting object uses below query, where has clause to
> check property is expensive
> {code:java}
> g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
> - has('__guid') queries solr [(35x_t <> null)]:vertex_index
> - below is the timetaken in the solr logs
> {code:java}
> 2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1681928 status=0 QTime=4227
> 2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1682086 status=0 QTime=787
> 2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1682216 status=0 QTime=1962
> 2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
> r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
> [vertex_index_shard1_replica_n1] webapp=/solr path=/select
> params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
> hits=1682363 status=0 QTime=4465 {code}
> - ran same query through gremlin shell while ingestion is happening it
> doesn't fail
> - time taken for above gremlin query in code when ingestion
> : 214825ms
> - time takem for above gremlin query in gremlin shell when ingestion :
> 104641ms
> - time taken for above gremlin query when no ingestion
> : 181682ms
> Still Root cause is unknown
> *WorkAround:*
> - Remove .has('__guid') clause from below, it is very quick and issue is not
> reproducible.
> {code:java}
> g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
> *Tests:*
> * upgrded tinkerpop and janusgraph version but didn't help
> * invalid property doesn't throw any exception or not existence of property
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*Steps to Repro:*
* Make sure backend has above 1M entities
* Start creating tables under `db1@cm`
* Start export for `db1@cm`
*
{code:java}
curl -v -X POST -u admin:admin -H "Content-Type: application/json"
"http://<>/api/atlas/admin/export" -d
'{"itemsToExport":[{"typeName":"hive_db","uniqueAttributes": { "qualifiedName":
"db1@cm" }}],"options":{"fetchType":"full","replicatedTo":"cm"}} >
export1.zip{code}
* It fails after sometime.
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick and issue is not
reproducible.
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
*Tests:*
* upgrded tinkerpop and janusgraph version but didn't help
* invalid property doesn't throw any exception or not existence of property
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').h
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick and issue is not
reproducible.
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
g.V().has('__typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid')
- has('__guid') queries [(35x_t <> null)]:vertex_index , checked timetaken in
the solr logs
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&sta
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick and issue is not
reproducible.
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
*Tests:*
* upgrded tinkerpop and janusgraph version but didn't help
* invalid property doesn't throw any exception or not existence of property
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16
[jira] [Created] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
Pinal Shah created ATLAS-4882:
-
Summary: Export/Import: Export exits with "Found 0 entities"
Key: ATLAS-4882
URL: https://issues.apache.org/jira/browse/ATLAS-4882
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
g.V().has('__typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid')
- has('__guid') queries [(35x_t <> null)]:vertex_index , checked timetaken in
the solr logs
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465
- ran same query through gremlin shell while ingestion is happening it doesnt
fail
- time taken for above gremlin query in code when ingestion : 214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion : 181682ms
WorkAround
- Remove .has('__guid') clause from below, it is very quick
g.V().has('__typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid')
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4881) Reduce logs printed during notification processing
Madhan Neethiraj created ATLAS-4881:
---
Summary: Reduce logs printed during notification processing
Key: ATLAS-4881
URL: https://issues.apache.org/jira/browse/ATLAS-4881
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
While processing notifications from Hive hook, Atlas server can print several
info level logs about its internal performance improvements, like the following:
{noformat}
INFO - [NotificationHookConsumer thread-0:] ~ setting
hive_column_lineage.name=QUERY:db1.tbl1@cl1:1559003302000->:INSERT:db1.tbl1@cl1:1544966827000:col1.
topic-offset=170, partition=0 (HivePreprocessor$HiveProcessPreprocessor:176)
INFO - [NotificationHookConsumer thread-0:] ~ moved 269 referred-entities to
end of entities-list (firstEntity:typeName=hive_table,
qualifiedName=db1.tbl2@cl1). topic-offset=2143, partition=0
(PreprocessorContext:369){noformat}
To avoid unnecessary overhead and the noise in the log file, these messages
should be logged at debug level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4878) utility to analyze hook notifications
[
https://issues.apache.org/jira/browse/ATLAS-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855802#comment-17855802
]
ASF subversion and git services commented on ATLAS-4878:
Commit 978087a882348f1fc1b6002a0aeb29192d8cc00a in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=978087a88 ]
ATLAS-4878: utility to analyze hook notifications
> utility to analyze hook notifications
> -
>
> Key: ATLAS-4878
> URL: https://issues.apache.org/jira/browse/ATLAS-4878
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4878.patch
>
>
> A utility to analyze notifications received from hooks to gather following
> details will be useful in troubleshooting:
> # number of notifications per notification type (CREATE, UPDATE,
> PARTIAL_UPDATE, DELETE, ..)
> # number of entities referenced in notifications per entity type
> # number of entity operations performed while processing the notifications
> (create/update/delete)
>
> For example, following details by analyzing 114k notifications from Hive hook
> show that 94% of entities processed are of type hive_column and
> hive_column_lineage :
> {noformat}
> {
> "notifications": 114755,
> "entities": 598435,
> "notificationEntities": 2575347,
> "notificationByType": {
> "ENTITY_CREATE_V2": 49428,
> "ENTITY_FULL_UPDATE_V2": 1597,
> "ENTITY_PARTIAL_UPDATE_V2": 36561,
> "ENTITY_DELETE_V2": 27169
> },
> "notificationEntityByType": {
> "hdfs_path": 16417,
> "hive_db": 20471,
> "hive_table":57143,
> "hive_storagedesc": 30018,
> "hive_column": 685384,
> "hive_process": 41512
> "hive_column_lineage": 1724402,
> },
> "entityOperations": {
> "CREATE": 598435,
> "UPDATE":1913182
> "PARTIAL_UPDATE": 36561,
> "DELETE": 27169
> },
> "entityOperationsByType": {
> "CREATE": {
> "hdfs_path":10940,
> "hive_db":224,
> "hive_table": 22154,
> "hive_storagedesc": 15280,
> "hive_column": 332332,
> "hive_process": 23462,
> "hive_column_lineage": 194043
> },
> "UPDATE" {
> "hdfs_path": 5477,
> "hive_column": 319559,
> "hive_column_lineage": 1530359,
> "hive_db": 20203,
> "hive_process": 18050,
> "hive_storagedesc": 13204,
> "hive_table": 6330
> },
>"PARTIAL_UPDATE": {
> "hive_column": 33493,
> "hive_storagedesc": 1534,
> "hive_table":1534
> },
> "DELETE": {
> "hive_db": 44,
> "hive_table": 27125
> }
> }
> } {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855563#comment-17855563 ] Brijesh Bhalala commented on ATLAS-4880: commited to [Apache master|https://github.com/apache/atlas/commit/70817c27c13dc30c25656e48cd40f35eab1a8d98] branch > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0004-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > *Problem Statement:-* > Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all > tasks that are active in Atlas, even those related to the currently viewed > entity. Ideally, it should show only those tasks which are related to the > entity whose detail page has been loaded. > *Temporary Fix:-* > Atlas UI show 'Something went wrong'. > We need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions > *Note:-* > Will come up with a follow up patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855480#comment-17855480 ] ASF subversion and git services commented on ATLAS-4880: Commit fda0a4d0324b1eafe082e6065960940ce2cf5f41 in atlas's branch refs/heads/branch-2.0 from Brijesh Bhalala [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fda0a4d03 ] ATLAS-4880: Temporarily disable the tasks tab on Entity Detail page on Atlas UI Signed-off-by: Pinal Shah > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0004-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > *Problem Statement:-* > Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all > tasks that are active in Atlas, even those related to the currently viewed > entity. Ideally, it should show only those tasks which are related to the > entity whose detail page has been loaded. > *Temporary Fix:-* > Atlas UI show 'Something went wrong'. > We need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions > *Note:-* > Will come up with a follow up patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855479#comment-17855479 ] ASF subversion and git services commented on ATLAS-4880: Commit 70817c27c13dc30c25656e48cd40f35eab1a8d98 in atlas's branch refs/heads/master from Brijesh Bhalala [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=70817c27c ] ATLAS-4880: Temporarily disable the tasks tab on Entity Detail page on Atlas UI Signed-off-by: Pinal Shah > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0004-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > *Problem Statement:-* > Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all > tasks that are active in Atlas, even those related to the currently viewed > entity. Ideally, it should show only those tasks which are related to the > entity whose detail page has been loaded. > *Temporary Fix:-* > Atlas UI show 'Something went wrong'. > We need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions > *Note:-* > Will come up with a follow up patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Description: *Problem Statement:-* Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all tasks that are active in Atlas, even those related to the currently viewed entity. Ideally, it should show only those tasks which are related to the entity whose detail page has been loaded. *Temporary Fix:-* Atlas UI show 'Something went wrong'. We need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions *Note:-* Will come up with a follow up patch for this. was: *Problem Statement:-* Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all tasks that are active in Atlas, even those related to the currently viewed entity. Ideally, it should show only those tasks which are related to the entity whose detail page has been loaded. *Feature:-* Atlas UI show 'Something went wrong'. We need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0004-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > *Problem Statement:-* > Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all > tasks that are active in Atlas, even those related to the currently viewed > entity. Ideally, it should show only those tasks which are related to the > entity whose detail page has been loaded. > *Temporary Fix:-* > Atlas UI show 'Something went wrong'. > We need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions > *Note:-* > Will come up with a follow up patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Description: *Problem Statement:-* Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all tasks that are active in Atlas, even those related to the currently viewed entity. Ideally, it should show only those tasks which are related to the entity whose detail page has been loaded. *Feature:-* Atlas UI show 'Something went wrong'. We need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions was: Atlas UI show 'Something went wrong'. we need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. We need to: Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0004-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > *Problem Statement:-* > Currently, the Tasks Tab in Enity Details page of the Atlas UI displays all > tasks that are active in Atlas, even those related to the currently viewed > entity. Ideally, it should show only those tasks which are related to the > entity whose detail page has been loaded. > *Feature:-* > Atlas UI show 'Something went wrong'. > We need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Attachment: 0004-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0004-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > Atlas UI show 'Something went wrong'. > we need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > We need to: > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Attachment: 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0003-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > Atlas UI show 'Something went wrong'. > we need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > We need to: > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Attachment: 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch, > 0002-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > Atlas UI show 'Something went wrong'. > we need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > We need to: > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Fix Version/s: 3.0.0 > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > Atlas UI show 'Something went wrong'. > we need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > We need to: > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Description: Atlas UI show 'Something went wrong'. we need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. We need to: Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions was: Atlas UI always show 'Something went wrong'. we need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. We need to: Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > Atlas UI show 'Something went wrong'. > we need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > We need to: > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Attachment: 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Attachments: > 0001-ATLAS-4880-Atlas-UI-Temporarily-disable-the-tasks-ta.patch > > > Atlas UI always show 'Something went wrong'. > we need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > We need to: > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
[ https://issues.apache.org/jira/browse/ATLAS-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4880: --- Description: Atlas UI always show 'Something went wrong'. we need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. We need to: Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions was: we need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. We need to: Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions > Temporarily disable the tasks tab on Entity Detail page > --- > > Key: ATLAS-4880 > URL: https://issues.apache.org/jira/browse/ATLAS-4880 > Project: Atlas > Issue Type: Task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > > Atlas UI always show 'Something went wrong'. > we need to temporarily disable tasks API call made from UI and don't show the > tasks tab on Entity Detail page. > We need to: > Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by > default > Make use of the above property on UI side to show the tasks tab on the entity > detail page. This will be in addition to the atlas.tasks.enabled property > which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4880) Temporarily disable the tasks tab on Entity Detail page
Brijesh Bhalala created ATLAS-4880: -- Summary: Temporarily disable the tasks tab on Entity Detail page Key: ATLAS-4880 URL: https://issues.apache.org/jira/browse/ATLAS-4880 Project: Atlas Issue Type: Task Components: atlas-webui Reporter: Brijesh Bhalala Assignee: Brijesh Bhalala we need to temporarily disable tasks API call made from UI and don't show the tasks tab on Entity Detail page. We need to: Add a server side property atlas.tasks.ui.tab.enabled, which is disabled by default Make use of the above property on UI side to show the tasks tab on the entity detail page. This will be in addition to the atlas.tasks.enabled property which is used to enable/disable deferred actions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4879) Delete classification API request circumvents classification disassociation limitation that is present in UI
Rahul Kurup created ATLAS-4879:
--
Summary: Delete classification API request circumvents
classification disassociation limitation that is present in UI
Key: ATLAS-4879
URL: https://issues.apache.org/jira/browse/ATLAS-4879
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
In Atlas UI, if a classification has been applied on an entity, and if that
entity has been soft-deleted, Atlas doesn't allow users to remove the
classification from that entity.
However it is possible to use this DELETE API request (
/{color:#212121}api/atlas/v2/entity/guid/)
{color}to circumvent this restriction.
Behaviour should be consistent with API as well as UI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4876) Docker setup fix to address HBase failure in docker
[ https://issues.apache.org/jira/browse/ATLAS-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853779#comment-17853779 ] ASF subversion and git services commented on ATLAS-4876: Commit 5bb9d8d58f6b0936ff79ace1297060678443e3c8 in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5bb9d8d58 ] ATLAS-4876: Docker setup fix to address HBase failure > Docker setup fix to address HBase failure in docker > --- > > Key: ATLAS-4876 > URL: https://issues.apache.org/jira/browse/ATLAS-4876 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-4876.patch > > > In docker setup, Atlas fails to startup due to HBase failure in creating > table with snappy compression type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4877) update JanusGraph version to 0.6.4
[ https://issues.apache.org/jira/browse/ATLAS-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853780#comment-17853780 ] ASF subversion and git services commented on ATLAS-4877: Commit 445e4b820b4365f60b8a16dfd72ae32df384b57d in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=445e4b820 ] ATLAS-4877: updated version of JanusGraph and Tinkerpop > update JanusGraph version to 0.6.4 > -- > > Key: ATLAS-4877 > URL: https://issues.apache.org/jira/browse/ATLAS-4877 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-4877.patch > > > Atlas currently uses JanusGraph version 0.6.3. JanusGraph 0.6.4 was released > late last year, Atlas should be updated to use this later version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4877) update JanusGraph version to 0.6.4
[ https://issues.apache.org/jira/browse/ATLAS-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853719#comment-17853719 ] Radhika Kundam commented on ATLAS-4877: --- +"Ship it" for the attached patch. > update JanusGraph version to 0.6.4 > -- > > Key: ATLAS-4877 > URL: https://issues.apache.org/jira/browse/ATLAS-4877 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-4877.patch > > > Atlas currently uses JanusGraph version 0.6.3. JanusGraph 0.6.4 was released > late last year, Atlas should be updated to use this later version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4876) Docker setup fix to address HBase failure in docker
[ https://issues.apache.org/jira/browse/ATLAS-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853714#comment-17853714 ] Radhika Kundam commented on ATLAS-4876: --- +"Ship it" for the attached patch. > Docker setup fix to address HBase failure in docker > --- > > Key: ATLAS-4876 > URL: https://issues.apache.org/jira/browse/ATLAS-4876 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-4876.patch > > > In docker setup, Atlas fails to startup due to HBase failure in creating > table with snappy compression type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4878) utility to analyze hook notifications
Madhan Neethiraj created ATLAS-4878:
---
Summary: utility to analyze hook notifications
Key: ATLAS-4878
URL: https://issues.apache.org/jira/browse/ATLAS-4878
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
A utility to analyze notifications received from hooks to gather following
details will be useful in troubleshooting:
# number of notifications per notification type (CREATE, UPDATE,
PARTIAL_UPDATE, DELETE, ..)
# number of entities referenced in notifications per entity type
# number of entity operations performed while processing the notifications
(create/update/delete)
For example, following details by analyzing 114k notifications from Hive hook
show that 94% of entities processed are of type hive_column and
hive_column_lineage :
{noformat}
{
"notifications": 114755,
"entities": 598435,
"notificationEntities": 2575347,
"notificationByType": {
"ENTITY_CREATE_V2": 49428,
"ENTITY_FULL_UPDATE_V2": 1597,
"ENTITY_PARTIAL_UPDATE_V2": 36561,
"ENTITY_DELETE_V2": 27169
},
"notificationEntityByType": {
"hdfs_path": 16417,
"hive_db": 20471,
"hive_table":57143,
"hive_storagedesc": 30018,
"hive_column": 685384,
"hive_process": 41512
"hive_column_lineage": 1724402,
},
"entityOperations": {
"CREATE": 598435,
"UPDATE":1913182
"PARTIAL_UPDATE": 36561,
"DELETE": 27169
},
"entityOperationsByType": {
"CREATE": {
"hdfs_path":10940,
"hive_db":224,
"hive_table": 22154,
"hive_storagedesc": 15280,
"hive_column": 332332,
"hive_process": 23462,
"hive_column_lineage": 194043
},
"UPDATE" {
"hdfs_path": 5477,
"hive_column": 319559,
"hive_column_lineage": 1530359,
"hive_db": 20203,
"hive_process": 18050,
"hive_storagedesc": 13204,
"hive_table": 6330
},
"PARTIAL_UPDATE": {
"hive_column": 33493,
"hive_storagedesc": 1534,
"hive_table":1534
},
"DELETE": {
"hive_db": 44,
"hive_table": 27125
}
}
} {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4877) update JanusGraph version to 0.6.4
Madhan Neethiraj created ATLAS-4877: --- Summary: update JanusGraph version to 0.6.4 Key: ATLAS-4877 URL: https://issues.apache.org/jira/browse/ATLAS-4877 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Atlas currently uses JanusGraph version 0.6.3. JanusGraph 0.6.4 was released late last year, Atlas should be updated to use this later version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
[ https://issues.apache.org/jira/browse/ATLAS-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia resolved ATLAS-4846. --- Resolution: Fixed > Source the atlas-env file in ATLAS import script to get all the argument > > > Key: ATLAS-4846 > URL: https://issues.apache.org/jira/browse/ATLAS-4846 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > User has to run manually export command to get all the argument which are > set, to run the Atlas import script. > The problem is not with the Atlas service itself but with these scripts: > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh > > Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
[ https://issues.apache.org/jira/browse/ATLAS-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853126#comment-17853126 ] ASF subversion and git services commented on ATLAS-4846: Commit 5c99420033e49ef237c8aa873b3fecec8cbeac8d in atlas's branch refs/heads/branch-2.0 from pareshD [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5c9942003 ] ATLAS-4846-Source-the-atlas-env-file-in-ATLAS-import.patch Signed-off-by: Mandar Ambawane > Source the atlas-env file in ATLAS import script to get all the argument > > > Key: ATLAS-4846 > URL: https://issues.apache.org/jira/browse/ATLAS-4846 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > User has to run manually export command to get all the argument which are > set, to run the Atlas import script. > The problem is not with the Atlas service itself but with these scripts: > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh > > Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
[ https://issues.apache.org/jira/browse/ATLAS-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853125#comment-17853125 ] ASF subversion and git services commented on ATLAS-4846: Commit 42bf77ba59ec8bc619fbd5635397a89ff4a6fedf in atlas's branch refs/heads/master from pareshD [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=42bf77ba5 ] ATLAS-4846-Source-the-atlas-env-file-in-ATLAS-import.patch Signed-off-by: Mandar Ambawane > Source the atlas-env file in ATLAS import script to get all the argument > > > Key: ATLAS-4846 > URL: https://issues.apache.org/jira/browse/ATLAS-4846 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > User has to run manually export command to get all the argument which are > set, to run the Atlas import script. > The problem is not with the Atlas service itself but with these scripts: > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh > > Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4597) Find a viable replacement of Backbone JS for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4597: --- Description: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Common Table Layout :- * Common table layout. * Table Functionalities :- a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, e)Column Show/Hide Functionalities 4. Table View on search page :- * Search page Table view. * Query Builder. 5. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. was: As backbone JS is an old library and backbone js related library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 5 years, we need to move to the latest and stable UI framework for Atlas UI. This is critical for security reasons. Research for a viable replacement of Backbone JS for Atlas UI. So we are planning to move Atlas UI code base to React js. Sub Tasks :- # Initial React Setup :- * Dev and Prod env Configuration. * Folder structure. * Installation of Libraries in React. 2. Left Sidebar Layout :- * Tree Structure and Search Bar. 3. Table View on search page :- * Search page Table view. * Query Builder. 4. Global Search Bar on Header :- * Global search bar for entities search. * Advance & Quick Search. > Find a viable replacement of Backbone JS for Atlas UI. > -- > > Key: ATLAS-4597 > URL: https://issues.apache.org/jira/browse/ATLAS-4597 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > > As backbone JS is an old library and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Atlas UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Atlas UI. > So we are planning to move Atlas UI code base to React js. > Sub Tasks :- > # Initial React Setup :- > * Dev and Prod env Configuration. > * Folder structure. > * Installation of Libraries in React. > 2. Left Sidebar Layout :- > * Tree Structure and Search Bar. > 3. Common Table Layout :- > * Common table layout. > * Table Functionalities :- > a)Sorting, b)Row Selection, c)Pagination, d)Drag and Drop Column, > e)Column Show/Hide Functionalities > 4. Table View on search page :- > * Search page Table view. > * Query Builder. > 5. Global Search Bar on Header :- > * Global search bar for entities search. > * Advance & Quick Search. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4868) Common Table layout for Atlas New UI
[ https://issues.apache.org/jira/browse/ATLAS-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated ATLAS-4868: --- Attachment: 0001-ATLAS-4868-Atlas-UI-Common-Table-layout-for-Atlas-Ne.patch > Common Table layout for Atlas New UI > - > > Key: ATLAS-4868 > URL: https://issues.apache.org/jira/browse/ATLAS-4868 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: atlas-react > Attachments: > 0001-ATLAS-4868-Atlas-UI-Common-Table-layout-for-Atlas-Ne.patch > > > Common Table layout for Atlas New UI > Common Table layout with functionality includes :- > 1)Sorting > 2)Column Show/Hide Options > 3)Row Selection > 4)Column Drag & Drop. > 5)Pagination. -- This message was sent by Atlassian Jira (v8.20.10#820010)
