[jira] [Commented] (ATLAS-4773) Can Apache Atlas Display get the delays in the lineage
[
https://issues.apache.org/jira/browse/ATLAS-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744298#comment-17744298
]
Umesh Padashetty commented on ATLAS-4773:
-
Hi [~jagadesh.kiran] The ask is unclear. Can you please clarify what you mean
by below?
{quote}can we have a feature which display getting the delays in the lineage.
{quote}
Also, the difference between the lineage of what?
{quote}Having a heat map to showcase the difference between lineage
{quote}
Thanks
> Can Apache Atlas Display get the delays in the lineage
> ---
>
> Key: ATLAS-4773
> URL: https://issues.apache.org/jira/browse/ATLAS-4773
> Project: Atlas
> Issue Type: New Feature
>Reporter: Jagadesh Kiran N
>Priority: Major
>
> Atlas shows lineage , can we have a feature which display getting the delays
> in the lineage.
> Ex :Having a heat map to showcase the difference between lineage
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4747) ddlQueries and ALTERTABLE_* lineage missing for spark tables created via spark3-shell
[
https://issues.apache.org/jira/browse/ATLAS-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4747:
Affects Version/s: 2.3.0
(was: 2.1.0)
> ddlQueries and ALTERTABLE_* lineage missing for spark tables created via
> spark3-shell
> -
>
> Key: ATLAS-4747
> URL: https://issues.apache.org/jira/browse/ATLAS-4747
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2023-04-26 at 1.00.11 AM.png, Screenshot
> 2023-04-26 at 1.00.17 AM.png, Screenshot 2023-04-26 at 1.00.45 AM.png,
> Screenshot 2023-04-26 at 1.00.50 AM.png
>
>
> Ran the below queries via spark3-shell
> {code:java}
> spark.sql("create table testing_iceberg_spark_alters_1(name string, address
> string)");
> spark.sql("alter table testing_iceberg_spark_alters_1 add column(address2
> string)");{code}
> ddlQueries and outputFromProcesses (lineage) is missing for the alter queries
> !Screenshot 2023-04-26 at 1.00.11 AM.png!
>
> !Screenshot 2023-04-26 at 1.00.17 AM.png!
> Running similar queries via beeline, it generates ddlQueries and
> outputFromProcesses (lineage) for the alter queries
> !Screenshot 2023-04-26 at 1.00.45 AM.png!
> !Screenshot 2023-04-26 at 1.00.50 AM.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4746) hive_process and hive_process_execution (lineage) being generated for simple DML UPDATE queries run via hive
[
https://issues.apache.org/jira/browse/ATLAS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4746:
Affects Version/s: 2.3.0
(was: 2.1.0)
> hive_process and hive_process_execution (lineage) being generated for simple
> DML UPDATE queries run via hive
>
>
> Key: ATLAS-4746
> URL: https://issues.apache.org/jira/browse/ATLAS-4746
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
>Reporter: Umesh Padashetty
>Priority: Critical
> Attachments: Screenshot 2023-05-02 at 6.28.18 PM.png, Screenshot
> 2023-05-02 at 6.28.34 PM.png, Screenshot 2023-05-02 at 6.29.05 PM.png,
> Screenshot 2023-05-02 at 6.29.10 PM.png, Screenshot 2023-05-02 at 6.47.19
> PM.png, Screenshot 2023-05-02 at 6.50.16 PM.png
>
>
> Queries ran:
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc;
> insert into test_hive_lineage_4 values ('qwer', '2');
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> As you can see, these are simple DML queries, and not DDL
> We should NOT be tracking lineage for any of the DML ({*}SELECT, INSERT,
> DELETE, and UPDATE){*} queries NOR should we be tracking the audits.
> Jiras via which DML operations audits were skipped:
> * https://issues.apache.org/jira/browse/ATLAS-3188
> * https://issues.apache.org/jira/browse/ATLAS-3198
> But all the issues were related to audits and not the lineage. In all these
> cases, lineage was not generated for the DML UPDATE query
> But observing that we are now capturing lineage for simple DML Update query
> Relationship after running
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc; {code}
> !Screenshot 2023-05-02 at 6.28.18 PM.png!
> !Screenshot 2023-05-02 at 6.28.34 PM.png!
> As seen, there is no lineage generated. Good so far
> Then I ran
> {code:java}
> insert into test_hive_lineage_4 values ('qwer', '2'); {code}
> No lineage was generated. Good so far
> !Screenshot 2023-05-02 at 6.47.19 PM.png!
> Then I ran
> {code:java}
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> This immediately generated a hive_process and a hive_process_execution
> Interestingly, hive_process with the following name was generated. As you can
> see, it has DELETE in the process name, when in reality this was an UPDATE
> DML. Another cause of concern?
> {code:java}
> QUERY:default.test_hive_lineage_4@cm:1683032252000->:DELETE:default.test_hive_lineage_4@cm:1683032252000
> {code}
> !Screenshot 2023-05-02 at 6.29.05 PM.png!
> !Screenshot 2023-05-02 at 6.29.10 PM.png!
> I then ran the same update query 100+ times, it created 100+ UNIQUE
> (timestamp delimited) hive_process_executions
> !Screenshot 2023-05-02 at 6.50.16 PM.png!
> This is a disaster since every UPDATE query now generates a
> process_execution.
> Customers can run 1000s of update queries, which are mostly of no use for
> atlas, but this issue is now leading to the generation of 1000s of
> process_executions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4747) ddlQueries and ALTERTABLE_* lineage missing for spark tables created via spark3-shell
[
https://issues.apache.org/jira/browse/ATLAS-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4747:
Affects Version/s: 2.1.0
(was: 2.3.0)
> ddlQueries and ALTERTABLE_* lineage missing for spark tables created via
> spark3-shell
> -
>
> Key: ATLAS-4747
> URL: https://issues.apache.org/jira/browse/ATLAS-4747
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2023-04-26 at 1.00.11 AM.png, Screenshot
> 2023-04-26 at 1.00.17 AM.png, Screenshot 2023-04-26 at 1.00.45 AM.png,
> Screenshot 2023-04-26 at 1.00.50 AM.png
>
>
> Ran the below queries via spark3-shell
> {code:java}
> spark.sql("create table testing_iceberg_spark_alters_1(name string, address
> string)");
> spark.sql("alter table testing_iceberg_spark_alters_1 add column(address2
> string)");{code}
> ddlQueries and outputFromProcesses (lineage) is missing for the alter queries
> !Screenshot 2023-04-26 at 1.00.11 AM.png!
>
> !Screenshot 2023-04-26 at 1.00.17 AM.png!
> Running similar queries via beeline, it generates ddlQueries and
> outputFromProcesses (lineage) for the alter queries
> !Screenshot 2023-04-26 at 1.00.45 AM.png!
> !Screenshot 2023-04-26 at 1.00.50 AM.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4746) hive_process and hive_process_execution (lineage) being generated for simple DML UPDATE queries run via hive
[
https://issues.apache.org/jira/browse/ATLAS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4746:
Affects Version/s: 2.1.0
(was: 2.3.0)
> hive_process and hive_process_execution (lineage) being generated for simple
> DML UPDATE queries run via hive
>
>
> Key: ATLAS-4746
> URL: https://issues.apache.org/jira/browse/ATLAS-4746
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Critical
> Attachments: Screenshot 2023-05-02 at 6.28.18 PM.png, Screenshot
> 2023-05-02 at 6.28.34 PM.png, Screenshot 2023-05-02 at 6.29.05 PM.png,
> Screenshot 2023-05-02 at 6.29.10 PM.png, Screenshot 2023-05-02 at 6.47.19
> PM.png, Screenshot 2023-05-02 at 6.50.16 PM.png
>
>
> Queries ran:
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc;
> insert into test_hive_lineage_4 values ('qwer', '2');
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> As you can see, these are simple DML queries, and not DDL
> We should NOT be tracking lineage for any of the DML ({*}SELECT, INSERT,
> DELETE, and UPDATE){*} queries NOR should we be tracking the audits.
> Jiras via which DML operations audits were skipped:
> * https://issues.apache.org/jira/browse/ATLAS-3188
> * https://issues.apache.org/jira/browse/ATLAS-3198
> But all the issues were related to audits and not the lineage. In all these
> cases, lineage was not generated for the DML UPDATE query
> But observing that we are now capturing lineage for simple DML Update query
> Relationship after running
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc; {code}
> !Screenshot 2023-05-02 at 6.28.18 PM.png!
> !Screenshot 2023-05-02 at 6.28.34 PM.png!
> As seen, there is no lineage generated. Good so far
> Then I ran
> {code:java}
> insert into test_hive_lineage_4 values ('qwer', '2'); {code}
> No lineage was generated. Good so far
> !Screenshot 2023-05-02 at 6.47.19 PM.png!
> Then I ran
> {code:java}
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> This immediately generated a hive_process and a hive_process_execution
> Interestingly, hive_process with the following name was generated. As you can
> see, it has DELETE in the process name, when in reality this was an UPDATE
> DML. Another cause of concern?
> {code:java}
> QUERY:default.test_hive_lineage_4@cm:1683032252000->:DELETE:default.test_hive_lineage_4@cm:1683032252000
> {code}
> !Screenshot 2023-05-02 at 6.29.05 PM.png!
> !Screenshot 2023-05-02 at 6.29.10 PM.png!
> I then ran the same update query 100+ times, it created 100+ UNIQUE
> (timestamp delimited) hive_process_executions
> !Screenshot 2023-05-02 at 6.50.16 PM.png!
> This is a disaster since every UPDATE query now generates a
> process_execution.
> Customers can run 1000s of update queries, which are mostly of no use for
> atlas, but this issue is now leading to the generation of 1000s of
> process_executions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4746) hive_process and hive_process_execution (lineage) being generated for simple DML UPDATE queries run via hive
[
https://issues.apache.org/jira/browse/ATLAS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4746:
Component/s: atlas-core
> hive_process and hive_process_execution (lineage) being generated for simple
> DML UPDATE queries run via hive
>
>
> Key: ATLAS-4746
> URL: https://issues.apache.org/jira/browse/ATLAS-4746
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
>Reporter: Umesh Padashetty
>Priority: Critical
> Attachments: Screenshot 2023-05-02 at 6.28.18 PM.png, Screenshot
> 2023-05-02 at 6.28.34 PM.png, Screenshot 2023-05-02 at 6.29.05 PM.png,
> Screenshot 2023-05-02 at 6.29.10 PM.png, Screenshot 2023-05-02 at 6.47.19
> PM.png, Screenshot 2023-05-02 at 6.50.16 PM.png
>
>
> Queries ran:
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc;
> insert into test_hive_lineage_4 values ('qwer', '2');
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> As you can see, these are simple DML queries, and not DDL
> We should NOT be tracking lineage for any of the DML ({*}SELECT, INSERT,
> DELETE, and UPDATE){*} queries NOR should we be tracking the audits.
> Jiras via which DML operations audits were skipped:
> * https://issues.apache.org/jira/browse/ATLAS-3188
> * https://issues.apache.org/jira/browse/ATLAS-3198
> But all the issues were related to audits and not the lineage. In all these
> cases, lineage was not generated for the DML UPDATE query
> But observing that we are now capturing lineage for simple DML Update query
> Relationship after running
> {code:java}
> create table test_hive_lineage_4 (name string, id int) stored as orc; {code}
> !Screenshot 2023-05-02 at 6.28.18 PM.png!
> !Screenshot 2023-05-02 at 6.28.34 PM.png!
> As seen, there is no lineage generated. Good so far
> Then I ran
> {code:java}
> insert into test_hive_lineage_4 values ('qwer', '2'); {code}
> No lineage was generated. Good so far
> !Screenshot 2023-05-02 at 6.47.19 PM.png!
> Then I ran
> {code:java}
> update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
> This immediately generated a hive_process and a hive_process_execution
> Interestingly, hive_process with the following name was generated. As you can
> see, it has DELETE in the process name, when in reality this was an UPDATE
> DML. Another cause of concern?
> {code:java}
> QUERY:default.test_hive_lineage_4@cm:1683032252000->:DELETE:default.test_hive_lineage_4@cm:1683032252000
> {code}
> !Screenshot 2023-05-02 at 6.29.05 PM.png!
> !Screenshot 2023-05-02 at 6.29.10 PM.png!
> I then ran the same update query 100+ times, it created 100+ UNIQUE
> (timestamp delimited) hive_process_executions
> !Screenshot 2023-05-02 at 6.50.16 PM.png!
> This is a disaster since every UPDATE query now generates a
> process_execution.
> Customers can run 1000s of update queries, which are mostly of no use for
> atlas, but this issue is now leading to the generation of 1000s of
> process_executions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4747) ddlQueries and ALTERTABLE_* lineage missing for spark tables created via spark3-shell
Umesh Padashetty created ATLAS-4747:
---
Summary: ddlQueries and ALTERTABLE_* lineage missing for spark
tables created via spark3-shell
Key: ATLAS-4747
URL: https://issues.apache.org/jira/browse/ATLAS-4747
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.3.0
Reporter: Umesh Padashetty
Attachments: Screenshot 2023-04-26 at 1.00.11 AM.png, Screenshot
2023-04-26 at 1.00.17 AM.png, Screenshot 2023-04-26 at 1.00.45 AM.png,
Screenshot 2023-04-26 at 1.00.50 AM.png
Ran the below queries via spark3-shell
{code:java}
spark.sql("create table testing_iceberg_spark_alters_1(name string, address
string)");
spark.sql("alter table testing_iceberg_spark_alters_1 add column(address2
string)");{code}
ddlQueries and outputFromProcesses (lineage) is missing for the alter queries
!Screenshot 2023-04-26 at 1.00.11 AM.png!
!Screenshot 2023-04-26 at 1.00.17 AM.png!
Running similar queries via beeline, it generates ddlQueries and
outputFromProcesses (lineage) for the alter queries
!Screenshot 2023-04-26 at 1.00.45 AM.png!
!Screenshot 2023-04-26 at 1.00.50 AM.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4746) hive_process and hive_process_execution (lineage) being generated for simple DML UPDATE queries run via hive
Umesh Padashetty created ATLAS-4746:
---
Summary: hive_process and hive_process_execution (lineage) being
generated for simple DML UPDATE queries run via hive
Key: ATLAS-4746
URL: https://issues.apache.org/jira/browse/ATLAS-4746
Project: Atlas
Issue Type: Bug
Affects Versions: 2.3.0
Reporter: Umesh Padashetty
Attachments: Screenshot 2023-05-02 at 6.28.18 PM.png, Screenshot
2023-05-02 at 6.28.34 PM.png, Screenshot 2023-05-02 at 6.29.05 PM.png,
Screenshot 2023-05-02 at 6.29.10 PM.png, Screenshot 2023-05-02 at 6.47.19
PM.png, Screenshot 2023-05-02 at 6.50.16 PM.png
Queries ran:
{code:java}
create table test_hive_lineage_4 (name string, id int) stored as orc;
insert into test_hive_lineage_4 values ('qwer', '2');
update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
As you can see, these are simple DML queries, and not DDL
We should NOT be tracking lineage for any of the DML ({*}SELECT, INSERT,
DELETE, and UPDATE){*} queries NOR should we be tracking the audits.
Jiras via which DML operations audits were skipped:
* https://issues.apache.org/jira/browse/ATLAS-3188
* https://issues.apache.org/jira/browse/ATLAS-3198
But all the issues were related to audits and not the lineage. In all these
cases, lineage was not generated for the DML UPDATE query
But observing that we are now capturing lineage for simple DML Update query
Relationship after running
{code:java}
create table test_hive_lineage_4 (name string, id int) stored as orc; {code}
!Screenshot 2023-05-02 at 6.28.18 PM.png!
!Screenshot 2023-05-02 at 6.28.34 PM.png!
As seen, there is no lineage generated. Good so far
Then I ran
{code:java}
insert into test_hive_lineage_4 values ('qwer', '2'); {code}
No lineage was generated. Good so far
!Screenshot 2023-05-02 at 6.47.19 PM.png!
Then I ran
{code:java}
update test_hive_lineage_4 set name = 'vwxy' where id = 2; {code}
This immediately generated a hive_process and a hive_process_execution
Interestingly, hive_process with the following name was generated. As you can
see, it has DELETE in the process name, when in reality this was an UPDATE DML.
Another cause of concern?
{code:java}
QUERY:default.test_hive_lineage_4@cm:1683032252000->:DELETE:default.test_hive_lineage_4@cm:1683032252000
{code}
!Screenshot 2023-05-02 at 6.29.05 PM.png!
!Screenshot 2023-05-02 at 6.29.10 PM.png!
I then ran the same update query 100+ times, it created 100+ UNIQUE (timestamp
delimited) hive_process_executions
!Screenshot 2023-05-02 at 6.50.16 PM.png!
This is a disaster since every UPDATE query now generates a process_execution.
Customers can run 1000s of update queries, which are mostly of no use for
atlas, but this issue is now leading to the generation of 1000s of
process_executions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4657) Atlas Python client is messing up with logs
[
https://issues.apache.org/jira/browse/ATLAS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694614#comment-17694614
]
Umesh Padashetty commented on ATLAS-4657:
-
I have tested the changes, and it works fine. Logging issue is now fixed
> Atlas Python client is messing up with logs
> ---
>
> Key: ATLAS-4657
> URL: https://issues.apache.org/jira/browse/ATLAS-4657
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After importing {{atlas-client}} Python library, I got all my loggers
> disabled.
> This is caused by this code block:
> [https://github.com/apache/atlas/blob/c1daaa44c3833be31c006753a2cf2f6f2e476cdc/intg/src/main/python/apache_atlas/__init__.py]
> Unlike applications, libraries should not setup logging by themselves. It
> should be done explicitly by code which uses this client. Or there should be
> a function to set up desired logging, which also should be explicitly called
> by application or user.
>
> I've created a pull request to fix this issue:
> [https://github.com/apache/atlas/pull/157]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4726) Irregular "Error Details" format when there is an Error in Bulk Import Business Metadata
Umesh Padashetty created ATLAS-4726:
---
Summary: Irregular "Error Details" format when there is an Error
in Bulk Import Business Metadata
Key: ATLAS-4726
URL: https://issues.apache.org/jira/browse/ATLAS-4726
Project: Atlas
Issue Type: Bug
Reporter: Umesh Padashetty
Attachments: Screenshot 2023-01-17 at 10.30.22 PM.png, Screenshot
2023-01-17 at 10.31.13 PM.png
Attached screenshots, you can see that we are printing Error details in
different formats
In some cases we print
* Provided value PURGE is Enumeration of Long type at line #20
In other cases we print
* Line #2: invalid business-metadata 'BM2.A1' for entity type 'hive_table'
I think it is a good idea to maintain the following format to increase the
readability of error
: Error like below
{code:java}
Line #2: invalid business-metadata 'BM2.A1' for entity type 'hive_table'
Line #3: invalid business-metadata 'BM2.A3' for entity type 'hive_table'
Line #4: invalid business-metadata 'BM2.A5' for entity type 'hive_table'
Line #5: invalid business-metadata 'BM2.A7' for entity type 'hive_table'
Line #6: invalid business-metadata 'BM2.A9' for entity type 'hive_table'
Line #7: invalid business-metadata 'BM2.A11' for entity type 'hive_table'
Line #8: invalid business-metadata 'BM2.A13' for entity type 'hive_table'
Line #9: invalid business-metadata 'BM2.A15' for entity type 'hive_table'
Line #10: invalid business-metadata 'BM2.A17' for entity type 'hive_table'
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4633) Multiple typos in official Apache Atlas Docs
[ https://issues.apache.org/jira/browse/ATLAS-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566229#comment-17566229 ] Umesh Padashetty commented on ATLAS-4633: - Review board request: https://reviews.apache.org/r/74055/ > Multiple typos in official Apache Atlas Docs > > > Key: ATLAS-4633 > URL: https://issues.apache.org/jira/browse/ATLAS-4633 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Critical > Attachments: ATLAS-4633.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4633) Multiple typos in official Apache Atlas Docs
[ https://issues.apache.org/jira/browse/ATLAS-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4633: Attachment: (was: ATLAS-4633) > Multiple typos in official Apache Atlas Docs > > > Key: ATLAS-4633 > URL: https://issues.apache.org/jira/browse/ATLAS-4633 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Critical > Attachments: ATLAS-4633.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4633) Multiple typos in official Apache Atlas Docs
[ https://issues.apache.org/jira/browse/ATLAS-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4633: Attachment: ATLAS-4633.patch > Multiple typos in official Apache Atlas Docs > > > Key: ATLAS-4633 > URL: https://issues.apache.org/jira/browse/ATLAS-4633 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Critical > Attachments: ATLAS-4633.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4633) Multiple typos in official Apache Atlas Docs
[ https://issues.apache.org/jira/browse/ATLAS-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4633: Attachment: ATLAS-4633 > Multiple typos in official Apache Atlas Docs > > > Key: ATLAS-4633 > URL: https://issues.apache.org/jira/browse/ATLAS-4633 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Critical > Attachments: ATLAS-4633.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4633) Multiple typos in official Apache Atlas Docs
Umesh Padashetty created ATLAS-4633: --- Summary: Multiple typos in official Apache Atlas Docs Key: ATLAS-4633 URL: https://issues.apache.org/jira/browse/ATLAS-4633 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Assignee: Umesh Padashetty -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4603) Apache Atlas - Unable to edit an entity by User Interface
[ https://issues.apache.org/jira/browse/ATLAS-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536131#comment-17536131 ] Umesh Padashetty commented on ATLAS-4603: - You need to add the type in "atlas.ui.editable.entity.types" atlas property. > Apache Atlas - Unable to edit an entity by User Interface > - > > Key: ATLAS-4603 > URL: https://issues.apache.org/jira/browse/ATLAS-4603 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: gianluca >Priority: Major > Labels: atlas > Attachments: edit entity.png > > > Hi > I created a new entity by a custom type but, when I want to update it using > 'Edit entity' from UI, the command do not generate anything; in other words: > I see always the following screen. How can I solve this? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ATLAS-4490) docz node dev server is not working
[ https://issues.apache.org/jira/browse/ATLAS-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516645#comment-17516645 ] Umesh Padashetty commented on ATLAS-4490: - Hi [~kevalbhatt] any luck with this? > docz node dev server is not working > --- > > Key: ATLAS-4490 > URL: https://issues.apache.org/jira/browse/ATLAS-4490 > Project: Atlas > Issue Type: Task >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4567) atlas/api/atlas/admin/tasks API returns partial data intermittently
Umesh Padashetty created ATLAS-4567:
---
Summary: atlas/api/atlas/admin/tasks API returns partial data
intermittently
Key: ATLAS-4567
URL: https://issues.apache.org/jira/browse/ATLAS-4567
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.2.0
Reporter: Umesh Padashetty
Generally, call to atlas/api/atlas/admin/tasks returns something like below
when there are some pending tasks. When there are no pending tasks, it returns
[]
{code:java}
[
{
"type": "CLASSIFICATION_PROPAGATION_ADD",
"guid": "154050a4-f593-4c11-8a94-111d8c6d5947",
"createdBy": "hrt_qa",
"createdTime": 1646830384858,
"updatedTime": 1646830384858,
"parameters": {
"relationshipGuid": null,
"entityGuid": "19b0ef2a-d645-4c29-ac67-37b9697bac96",
"classificationVertexId": "163905752"
},
"attemptCount": 0,
"status": "PENDING"
}
] {code}
But observed that in one of the case, atlas responded with just below
{code:java}
[
{
"attemptCount": 0
}
] {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4367) UI: Spelling mistake in error message that comes when attempting to delete assigned term
[ https://issues.apache.org/jira/browse/ATLAS-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456160#comment-17456160 ] Umesh Padashetty commented on ATLAS-4367: - Pre commits: https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/999/ > UI: Spelling mistake in error message that comes when attempting to delete > assigned term > > > Key: ATLAS-4367 > URL: https://issues.apache.org/jira/browse/ATLAS-4367 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4367.patch, image-2021-07-22-17-57-55-410.png > > > !image-2021-07-22-17-57-55-410.png|width=450,height=250! > > As you can see in the above screenshot, 'can't' is misspelled as 'cant'. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4450) [UI] Misalignment when the logged in user's name is greater than a certain length
Umesh Padashetty created ATLAS-4450: --- Summary: [UI] Misalignment when the logged in user's name is greater than a certain length Key: ATLAS-4450 URL: https://issues.apache.org/jira/browse/ATLAS-4450 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2021-10-11 at 5.15.53 PM.png !Screenshot 2021-10-11 at 5.15.53 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4420) [Atlas: Hive Import] The hive import logs are not generated
[
https://issues.apache.org/jira/browse/ATLAS-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17412638#comment-17412638
]
Umesh Padashetty commented on ATLAS-4420:
-
This is a duplicate of ATLAS-4369
> [Atlas: Hive Import] The hive import logs are not generated
> ---
>
> Key: ATLAS-4420
> URL: https://issues.apache.org/jira/browse/ATLAS-4420
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
>
> {code:java}
> [root@quasar-cxwzxp-3 bin]#
> /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh -f /tmp/file2.txt
> Using Hive configuration directory [/etc/hive/conf]
> ...
> Log file for import is /var/log/atlas/import-hive.log
> SLF4J: Class path contains multiple SLF4J bindings.
> ...
> Hive Meta Data imported successfully!!! {code}
> As seen above, the import command says that import log file will be generated
> in */var/log/atlas/import-hive.log* location
> But no such file is created
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4367) UI: Spelling mistake in error message that comes when attempting to delete assigned term
[ https://issues.apache.org/jira/browse/ATLAS-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386336#comment-17386336 ] Umesh Padashetty commented on ATLAS-4367: - Review board request: https://reviews.apache.org/r/73475/ > UI: Spelling mistake in error message that comes when attempting to delete > assigned term > > > Key: ATLAS-4367 > URL: https://issues.apache.org/jira/browse/ATLAS-4367 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4367.patch, image-2021-07-22-17-57-55-410.png > > > !image-2021-07-22-17-57-55-410.png|width=450,height=250! > > As you can see in the above screenshot, 'can't' is misspelled as 'cant'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4367) UI: Spelling mistake in error message that comes when attempting to delete assigned term
[ https://issues.apache.org/jira/browse/ATLAS-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty reassigned ATLAS-4367: --- Assignee: Umesh Padashetty > UI: Spelling mistake in error message that comes when attempting to delete > assigned term > > > Key: ATLAS-4367 > URL: https://issues.apache.org/jira/browse/ATLAS-4367 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Umesh Padashetty >Priority: Minor > Attachments: image-2021-07-22-17-57-55-410.png > > > !image-2021-07-22-17-57-55-410.png|width=450,height=250! > > As you can see in the above screenshot, 'can't' is misspelled as 'cant'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4369) import-hive.sh does not write logs to /var/log/atlas/import-hive.log file, instead write into ${atlas.log.file} under the directory "${atlas.log.dir}"
[
https://issues.apache.org/jira/browse/ATLAS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4369:
Summary: import-hive.sh does not write logs to
/var/log/atlas/import-hive.log file, instead write into ${atlas.log.file} under
the directory "${atlas.log.dir}" (was: import-hive.sh does not write logs to
/var/log/atlas/import-hive.log file, instead write into ${atlas.log.file} under
the directory "${atlas.log.dir}" in
/opt/cloudera/parcels/CDH/lib/atlas/hook-bin )
> import-hive.sh does not write logs to /var/log/atlas/import-hive.log file,
> instead write into ${atlas.log.file} under the directory "${atlas.log.dir}"
> ---
>
> Key: ATLAS-4369
> URL: https://issues.apache.org/jira/browse/ATLAS-4369
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Major
>
> When the import scripts like
> * import-kafka.sh
> * import-hive.sh
> * import-hbase.sh
> are run, the corresponding logs are written into
> * /var/log/atlas/import-kafka.log
> * /var/log/atlas/import-hive.log
> * /var/log/atlas/import-hbase.log
> /var/log/atlas/import-kafka.log and /var/log/atlas/import-hbase.log logs are
> correctly written. But when import-hive.sh is ran,
> /var/log/atlas/import-hive.log is not created or written to
> {code:java}
> [root@ccycloud-1 atlas]# ls -ltr
> total 10988
> drwxr-xr-x 2 cstm_atlas cstm_atlas 4096 Jul 16 06:55 jstacks
> drwxr-xr-x 4 root root 4096 Jul 16 06:55 audit
> -rw-r--r-- 1 cstm_atlas cstm_atlas0 Jul 16 06:55 metric.log
> -rw-r--r-- 1 cstm_atlas cstm_atlas0 Jul 16 06:55 failed.log
> drwxr-xr-x 2 cstm_atlas cstm_atlas 4096 Jul 18 03:52 support-bundle
> -rw-r--r-- 1 root root 21573 Jul 22 09:56 import-kafka.log
> -rw-r--r-- 1 root root 159459 Jul 22 09:58 import-hbase.log
> -rw-r--r-- 1 cstm_atlas cstm_atlas19429 Jul 22 10:12
> gc-worker.log.0.current
> -rw-r--r-- 1 cstm_atlas cstm_atlas 179081 Jul 22 10:22 audit.log
> -rw-r--r-- 1 cstm_atlas cstm_atlas 10840903 Jul 22 10:23 application.log
> {code}
> whereas it creates a directory with the name ${atlas.log.dir} and a file with
> the name ${atlas.log.file} under it
> {code:java}
> [root@ccycloud-1 hook-bin]# ls -ltr
> total 44
> -rwxr-xr-x 1 root root 3892 Jul 14 13:09 import-kafka.sh
> -rwxr-xr-x 1 root root 4547 Jul 14 13:09 import-hive.sh
> -rwxr-xr-x 1 root root 4341 Jul 14 13:09 import-hbase.sh
> drwxr-sr-x 2 root root 4096 Jul 22 10:23 ${atlas.log.dir}
> -rw-r--r-- 1 root root 20094 Jul 22 10:23 derby.log {code}
> The import-hive.sh logs are written into ${atlas.log.file}
> {code:java}
> [root@ccycloud-1 ${atlas.log.dir}]# ls -ltra
> total 48
> drwxr-sr-x 3 root root 4096 Jul 22 10:23 ..
> drwxr-sr-x 2 root root 4096 Jul 22 10:23 .
> -rw-r--r-- 1 root root 40960 Jul 22 10:23 ${atlas.log.file} {code}
> The import-hive.sh logs should be written into /var/log/atlas/import-hive.log
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4369) import-hive.sh does not write logs to /var/log/atlas/import-hive.log file, instead write into ${atlas.log.file} under the directory "${atlas.log.dir}" in /opt/cloudera/pa
Umesh Padashetty created ATLAS-4369:
---
Summary: import-hive.sh does not write logs to
/var/log/atlas/import-hive.log file, instead write into ${atlas.log.file} under
the directory "${atlas.log.dir}" in
/opt/cloudera/parcels/CDH/lib/atlas/hook-bin
Key: ATLAS-4369
URL: https://issues.apache.org/jira/browse/ATLAS-4369
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
When the import scripts like
* import-kafka.sh
* import-hive.sh
* import-hbase.sh
are run, the corresponding logs are written into
* /var/log/atlas/import-kafka.log
* /var/log/atlas/import-hive.log
* /var/log/atlas/import-hbase.log
/var/log/atlas/import-kafka.log and /var/log/atlas/import-hbase.log logs are
correctly written. But when import-hive.sh is ran,
/var/log/atlas/import-hive.log is not created or written to
{code:java}
[root@ccycloud-1 atlas]# ls -ltr
total 10988
drwxr-xr-x 2 cstm_atlas cstm_atlas 4096 Jul 16 06:55 jstacks
drwxr-xr-x 4 root root 4096 Jul 16 06:55 audit
-rw-r--r-- 1 cstm_atlas cstm_atlas0 Jul 16 06:55 metric.log
-rw-r--r-- 1 cstm_atlas cstm_atlas0 Jul 16 06:55 failed.log
drwxr-xr-x 2 cstm_atlas cstm_atlas 4096 Jul 18 03:52 support-bundle
-rw-r--r-- 1 root root 21573 Jul 22 09:56 import-kafka.log
-rw-r--r-- 1 root root 159459 Jul 22 09:58 import-hbase.log
-rw-r--r-- 1 cstm_atlas cstm_atlas19429 Jul 22 10:12 gc-worker.log.0.current
-rw-r--r-- 1 cstm_atlas cstm_atlas 179081 Jul 22 10:22 audit.log
-rw-r--r-- 1 cstm_atlas cstm_atlas 10840903 Jul 22 10:23 application.log {code}
whereas it creates a directory with the name ${atlas.log.dir} and a file with
the name ${atlas.log.file} under it
{code:java}
[root@ccycloud-1 hook-bin]# ls -ltr
total 44
-rwxr-xr-x 1 root root 3892 Jul 14 13:09 import-kafka.sh
-rwxr-xr-x 1 root root 4547 Jul 14 13:09 import-hive.sh
-rwxr-xr-x 1 root root 4341 Jul 14 13:09 import-hbase.sh
drwxr-sr-x 2 root root 4096 Jul 22 10:23 ${atlas.log.dir}
-rw-r--r-- 1 root root 20094 Jul 22 10:23 derby.log {code}
The import-hive.sh logs are written into ${atlas.log.file}
{code:java}
[root@ccycloud-1 ${atlas.log.dir}]# ls -ltra
total 48
drwxr-sr-x 3 root root 4096 Jul 22 10:23 ..
drwxr-sr-x 2 root root 4096 Jul 22 10:23 .
-rw-r--r-- 1 root root 40960 Jul 22 10:23 ${atlas.log.file} {code}
The import-hive.sh logs should be written into /var/log/atlas/import-hive.log
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4354) atlas import-hive.sh fails with java.lang.AbstractMethodError: Receiver class com.sun.jersey.api.uri.UriBuilderImpl does not define or inherit an implementation of the
[ https://issues.apache.org/jira/browse/ATLAS-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17380257#comment-17380257 ] Umesh Padashetty commented on ATLAS-4354: - Thanks for the patch, verified. > atlas import-hive.sh fails with java.lang.AbstractMethodError: Receiver class > com.sun.jersey.api.uri.UriBuilderImpl does not define or inherit an > implementation of the resolved method abstract uri > > > Key: ATLAS-4354 > URL: https://issues.apache.org/jira/browse/ATLAS-4354 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > While importing hive getting below error. > atlas import-hive.sh fails with java.lang.AbstractMethodError: Receiver class > com.sun.jersey.api.uri.UriBuilderImpl does not define or inherit an > implementation of the resolved method abstract uri > 2021-07-09 23:28:51,803|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:119) > 2021-07-09 23:28:51,803|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.AtlasBaseClient.getAddressIfActive(AtlasBaseClient.java:633) > 2021-07-09 23:28:51,803|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.AtlasBaseClient.selectActiveServerAddress(AtlasBaseClient.java:617) > 2021-07-09 23:28:51,803|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.AtlasBaseClient.determineActiveServiceURL(AtlasBaseClient.java:323) > 2021-07-09 23:28:51,804|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.AtlasBaseClient.initializeState(AtlasBaseClient.java:480) > 2021-07-09 23:28:51,804|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.AtlasBaseClient.initializeState(AtlasBaseClient.java:468) > 2021-07-09 23:28:51,804|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.AtlasBaseClient.(AtlasBaseClient.java:143) > 2021-07-09 23:28:51,804|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.AtlasClientV2.(AtlasClientV2.java:146) > 2021-07-09 23:28:51,804|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f|at > org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:158) > 2021-07-09 23:28:51,841|INFO|MainThread|machine.py:186 - > run()||GUID=78391325-5071-4406-99bd-99c1947a742f| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4355) UI: Spelling mistake in message after editing Busines Metadata value
[ https://issues.apache.org/jira/browse/ATLAS-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379663#comment-17379663 ] Umesh Padashetty commented on ATLAS-4355: - Review board request: https://reviews.apache.org/r/73456/ > UI: Spelling mistake in message after editing Busines Metadata value > > > Key: ATLAS-4355 > URL: https://issues.apache.org/jira/browse/ATLAS-4355 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4355.patch, Screenshot 2021-07-13 at 11-28-24 > Atlas.png > > > As per atttached screenshot, > "One or more Business Metadada attributess were updated successfully" > should be > "One or more Business Metadata attributes were updated successfully" > !Screenshot 2021-07-13 at 11-28-24 Atlas.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4355) UI: Spelling mistake in message after editing Busines Metadata value
[ https://issues.apache.org/jira/browse/ATLAS-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty reassigned ATLAS-4355: --- Assignee: Umesh Padashetty (was: Prasad P. Pawar) > UI: Spelling mistake in message after editing Busines Metadata value > > > Key: ATLAS-4355 > URL: https://issues.apache.org/jira/browse/ATLAS-4355 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Umesh Padashetty >Priority: Minor > Attachments: Screenshot 2021-07-13 at 11-28-24 Atlas.png > > > As per atttached screenshot, > "One or more Business Metadada attributess were updated successfully" > should be > "One or more Business Metadata attributes were updated successfully" > !Screenshot 2021-07-13 at 11-28-24 Atlas.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4343) [Entity Audits] 'Propagated Classification Added' Timestamp is < 'Entity Created' Timestamp
Umesh Padashetty created ATLAS-4343: --- Summary: [Entity Audits] 'Propagated Classification Added' Timestamp is < 'Entity Created' Timestamp Key: ATLAS-4343 URL: https://issues.apache.org/jira/browse/ATLAS-4343 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty The 'Propagated Classification Added' Timestamp is < 'Entity Created' Timestamp. This is invalid since the classificiation is propagated once the entity is created For instance # Created an external table with ozone path location # This creates ozone_key and hive_table entity # Entity Created TImestamp is shown correctly for both the entities # Applied a tag to ozone_key with propagate classification set to true # Classification propagates to hive_table entity, but the Timestamp shown is in past # For ozone_key: ## Entity created: 06/24/2021 08:44:33 PM (IST) ## Classification added: 06/24/2021 08:44:51 PM (IST) # Whereas hive_table: ## Entity created: 06/24/2021 08:44:33 PM (IST) ## Propagated Classification Added: 06/24/2021 *08:37:06 PM* (IST) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4334) Creating an external table/database, overrides the qualfiedName of an already existing aws_s3_v2_directory type
Umesh Padashetty created ATLAS-4334: --- Summary: Creating an external table/database, overrides the qualfiedName of an already existing aws_s3_v2_directory type Key: ATLAS-4334 URL: https://issues.apache.org/jira/browse/ATLAS-4334 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty The expectation is that every time an EXTERNAL Table is created in Hive, Atlas creates an entity of type hive_process connecting the aws_s3_v2_directory and the hive_table A new unique entity of the type aws_s3_v2_directory and hive_table is created in atlas for every new external table created. For instance, if I create an external table with the name test_ext_1, then there is an aws_s3_v2_directory and hive_table entity created with a similar name test_ext_1 But observing a strange behaviour where whenever a new external table is created, even though a new hive_table entity is created, the previously created aws_s3_v2_directory entity itself is getting overridden with the new qualifiedName For instance, I ran the below queries * create external table test_ext_1(name string); * create external table test_ext_2(name string); * create external table test_ext_3(name string); * create database net1; The expectation is that the above 4 queries will create * 3 hive_table entities * 1 hive_db entity * 3 aws_s3_v2_directory entities But it is actually creating * 3 hive_table entities * 1 hive_db entity * 1 aws_s3_v2_directory entity The same aws_s3_v2_directory gets updated with a new qualifiedName every time I create a new external table or a database -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4313) [Business Metadata Bulk Import] Importing multi values for Business Metadata Attribute of date type fails with Error "Provided value is not of Date type at line #"
[
https://issues.apache.org/jira/browse/ATLAS-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4313:
Description:
Content in the template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A17,1621932602000
hive_table,hive_table_kcsup@cm,BM3.BM3A18,1621932602000 {code}
Here, BM3.BM3A17 is multi value disabled and BM3.BM3A18 is multi value enabled
BM3A17 definition
!Screenshot 2021-05-26 at 11.30.49 PM.png!
BM3A18
!Screenshot 2021-05-26 at 11.30.40 PM.png!
Imported Data
!Screenshot 2021-05-26 at 11.32.19 PM.png!
Atlas api/atlas/v2/entity/businessmetadata/import returns
{code:java}
{"failedImportInfoList": [{"parentObjectName": "",
"childObjectName": "","importStatus": "FAILED",
"remarks": "Provided value 1621932602000 is not of Date type at line #2"
}],"successImportInfoList": [{"parentObjectName":
"b91f9726-4020-4005-9ee4-f79215f85c38","childObjectName":
"{BM4={BM4A1=stringy}, BM3={BM3A20=[PURGE, EXPORT], BM3A9=1234, BM3A15=123456,
BM3A14=[12345.67, 23456.7], BM3A17=1621932602000, BM3A16=[123456, 234567],
BM3A11=123.45, BM3A10=[1234, 2345], BM3A13=12345.67, BM3A12=[123.45, 234.56],
BM3A19=RAM_DISK, BM3A18=[], BM3A6=[1, 2], BM3A5=1, BM3A8=[12, 23], BM3A7=12,
BM3A2=[stringval1, stringval2], BM3A1=stringval, BM3A4=[true, false],
BM3A3=true}}","importStatus": "SUCCESS","remarks": ""
}]} {code}
It is important to note that, Importing single value for single valued Business
Metadata Attribute of date type works fine
was:
Content in the template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A17,1621932602000
hive_table,hive_table_kcsup@cm,BM3.BM3A18,1621932602000 {code}
Here, BM3.BM3A17 is multi value disabled and BM3.BM3A18 is multi value enabled
BM3A17 definition
!Screenshot 2021-05-26 at 11.30.49 PM.png!
BM3A18
!Screenshot 2021-05-26 at 11.30.40 PM.png!
Imported Data
!Screenshot 2021-05-26 at 11.32.19 PM.png!
Atlas api/atlas/v2/entity/businessmetadata/import returns
{code:java}
{"failedImportInfoList": [{"parentObjectName": "",
"childObjectName": "","importStatus": "FAILED",
"remarks": "Provided value 1621932602000 is not of Date type at line #2"
}],"successImportInfoList": [{"parentObjectName":
"b91f9726-4020-4005-9ee4-f79215f85c38","childObjectName":
"{BM4={BM4A1=stringy}, BM3={BM3A20=[PURGE, EXPORT], BM3A9=1234, BM3A15=123456,
BM3A14=[12345.67, 23456.7], BM3A17=1621932602000, BM3A16=[123456, 234567],
BM3A11=123.45, BM3A10=[1234, 2345], BM3A13=12345.67, BM3A12=[123.45, 234.56],
BM3A19=RAM_DISK, BM3A18=[], BM3A6=[1, 2], BM3A5=1, BM3A8=[12, 23], BM3A7=12,
BM3A2=[stringval1, stringval2], BM3A1=stringval, BM3A4=[true, false],
BM3A3=true}}","importStatus": "SUCCESS","remarks": ""
}]} {code}
It is important to note that,
> [Business Metadata Bulk Import] Importing multi values for Business Metadata
> Attribute of date type fails with Error "Provided value is not of Date type
> at line #"
>
>
> Key: ATLAS-4313
> URL: https://issues.apache.org/jira/browse/ATLAS-4313
> Project: Atlas
> Issue Type: Bug
>Reporter: Umesh Padashetty
>Priority: Critical
> Attachments: Screenshot 2021-05-26 at 11.30.40 PM.png, Screenshot
> 2021-05-26 at 11.30.49 PM.png, Screenshot 2021-05-26 at 11.32.19 PM.png
>
>
> Content in the template file
> {code:java}
> EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
> hive_table,hive_table_kcsup@cm,BM3.BM3A17,1621932602000
> hive_table,hive_table_kcsup@cm,BM3.BM3A18,1621932602000 {code}
> Here, BM3.BM3A17 is multi value disabled and BM3.BM3A18 is multi value enabled
> BM3A17 definition
> !Screenshot 2021-05-26 at 11.30.49 PM.png!
> BM3A18
> !Screenshot 2021-05-26 at 11.30.40 PM.png!
> Imported Data
> !Screenshot 2021-05-26 at 11.32.19 PM.png!
> Atlas api/atlas/v2/entity/businessmetadata/import returns
> {code:java}
> {"failedImportInfoList": [{"parentObjectName": "",
> "childObjectName": "","importStatus": "FAILED",
> "remarks": "Provided value 1621932602000 is not of Date type at line #2"
>}],"successImportInfoList": [{
[jira] [Updated] (ATLAS-4313) [Business Metadata Bulk Import] Importing multi values for Business Metadata Attribute of date type fails with Error "Provided value is not of Date type at line #"
[
https://issues.apache.org/jira/browse/ATLAS-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4313:
Description:
Content in the template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A17,1621932602000
hive_table,hive_table_kcsup@cm,BM3.BM3A18,1621932602000 {code}
Here, BM3.BM3A17 is multi value disabled and BM3.BM3A18 is multi value enabled
BM3A17 definition
!Screenshot 2021-05-26 at 11.30.49 PM.png!
BM3A18
!Screenshot 2021-05-26 at 11.30.40 PM.png!
Imported Data
!Screenshot 2021-05-26 at 11.32.19 PM.png!
Atlas api/atlas/v2/entity/businessmetadata/import returns
{code:java}
{"failedImportInfoList": [{"parentObjectName": "",
"childObjectName": "","importStatus": "FAILED",
"remarks": "Provided value 1621932602000 is not of Date type at line #2"
}],"successImportInfoList": [{"parentObjectName":
"b91f9726-4020-4005-9ee4-f79215f85c38","childObjectName":
"{BM4={BM4A1=stringy}, BM3={BM3A20=[PURGE, EXPORT], BM3A9=1234, BM3A15=123456,
BM3A14=[12345.67, 23456.7], BM3A17=1621932602000, BM3A16=[123456, 234567],
BM3A11=123.45, BM3A10=[1234, 2345], BM3A13=12345.67, BM3A12=[123.45, 234.56],
BM3A19=RAM_DISK, BM3A18=[], BM3A6=[1, 2], BM3A5=1, BM3A8=[12, 23], BM3A7=12,
BM3A2=[stringval1, stringval2], BM3A1=stringval, BM3A4=[true, false],
BM3A3=true}}","importStatus": "SUCCESS","remarks": ""
}]} {code}
It is important to note that,
was:
Content in the template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A17,1621932602000
hive_table,hive_table_kcsup@cm,BM3.BM3A18,1621932602000 {code}
Here, BM3.BM3A17 is multi value disabled and BM3.BM3A18 is multi value enabled
BM3A17 definition
!Screenshot 2021-05-26 at 11.30.49 PM.png!
BM3A18
!Screenshot 2021-05-26 at 11.30.40 PM.png!
Imported Data
!Screenshot 2021-05-26 at 11.32.19 PM.png!
Atlas api/atlas/v2/entity/businessmetadata/import returns
{code:java}
{"failedImportInfoList": [{"parentObjectName": "",
"childObjectName": "","importStatus": "FAILED",
"remarks": "Provided value 1621932602000 is not of Date type at line #2"
}],"successImportInfoList": [{"parentObjectName":
"b91f9726-4020-4005-9ee4-f79215f85c38","childObjectName":
"{BM4={BM4A1=stringy}, BM3={BM3A20=[PURGE, EXPORT], BM3A9=1234, BM3A15=123456,
BM3A14=[12345.67, 23456.7], BM3A17=1621932602000, BM3A16=[123456, 234567],
BM3A11=123.45, BM3A10=[1234, 2345], BM3A13=12345.67, BM3A12=[123.45, 234.56],
BM3A19=RAM_DISK, BM3A18=[], BM3A6=[1, 2], BM3A5=1, BM3A8=[12, 23], BM3A7=12,
BM3A2=[stringval1, stringval2], BM3A1=stringval, BM3A4=[true, false],
BM3A3=true}}","importStatus": "SUCCESS","remarks": ""
}]} {code}
> [Business Metadata Bulk Import] Importing multi values for Business Metadata
> Attribute of date type fails with Error "Provided value is not of Date type
> at line #"
>
>
> Key: ATLAS-4313
> URL: https://issues.apache.org/jira/browse/ATLAS-4313
> Project: Atlas
> Issue Type: Bug
>Reporter: Umesh Padashetty
>Priority: Critical
> Attachments: Screenshot 2021-05-26 at 11.30.40 PM.png, Screenshot
> 2021-05-26 at 11.30.49 PM.png, Screenshot 2021-05-26 at 11.32.19 PM.png
>
>
> Content in the template file
> {code:java}
> EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
> hive_table,hive_table_kcsup@cm,BM3.BM3A17,1621932602000
> hive_table,hive_table_kcsup@cm,BM3.BM3A18,1621932602000 {code}
> Here, BM3.BM3A17 is multi value disabled and BM3.BM3A18 is multi value enabled
> BM3A17 definition
> !Screenshot 2021-05-26 at 11.30.49 PM.png!
> BM3A18
> !Screenshot 2021-05-26 at 11.30.40 PM.png!
> Imported Data
> !Screenshot 2021-05-26 at 11.32.19 PM.png!
> Atlas api/atlas/v2/entity/businessmetadata/import returns
> {code:java}
> {"failedImportInfoList": [{"parentObjectName": "",
> "childObjectName": "","importStatus": "FAILED",
> "remarks": "Provided value 1621932602000 is not of Date type at line #2"
>}],"successImportInfoList": [{
> "parentObjectName": "b91f9726-4020-4005-9ee4-f79215f85c38",
> "childObjectName": "{BM4={BM4A1=stringy},
[jira] [Created] (ATLAS-4313) [Business Metadata Bulk Import] Importing multi values for Business Metadata Attribute of date type fails with Error "Provided value is not of Date type at line #"
Umesh Padashetty created ATLAS-4313:
---
Summary: [Business Metadata Bulk Import] Importing multi values
for Business Metadata Attribute of date type fails with Error "Provided value
is not of Date type at line #"
Key: ATLAS-4313
URL: https://issues.apache.org/jira/browse/ATLAS-4313
Project: Atlas
Issue Type: Bug
Reporter: Umesh Padashetty
Attachments: Screenshot 2021-05-26 at 11.30.40 PM.png, Screenshot
2021-05-26 at 11.30.49 PM.png, Screenshot 2021-05-26 at 11.32.19 PM.png
Content in the template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A17,1621932602000
hive_table,hive_table_kcsup@cm,BM3.BM3A18,1621932602000 {code}
Here, BM3.BM3A17 is multi value disabled and BM3.BM3A18 is multi value enabled
BM3A17 definition
!Screenshot 2021-05-26 at 11.30.49 PM.png!
BM3A18
!Screenshot 2021-05-26 at 11.30.40 PM.png!
Imported Data
!Screenshot 2021-05-26 at 11.32.19 PM.png!
Atlas api/atlas/v2/entity/businessmetadata/import returns
{code:java}
{"failedImportInfoList": [{"parentObjectName": "",
"childObjectName": "","importStatus": "FAILED",
"remarks": "Provided value 1621932602000 is not of Date type at line #2"
}],"successImportInfoList": [{"parentObjectName":
"b91f9726-4020-4005-9ee4-f79215f85c38","childObjectName":
"{BM4={BM4A1=stringy}, BM3={BM3A20=[PURGE, EXPORT], BM3A9=1234, BM3A15=123456,
BM3A14=[12345.67, 23456.7], BM3A17=1621932602000, BM3A16=[123456, 234567],
BM3A11=123.45, BM3A10=[1234, 2345], BM3A13=12345.67, BM3A12=[123.45, 234.56],
BM3A19=RAM_DISK, BM3A18=[], BM3A6=[1, 2], BM3A5=1, BM3A8=[12, 23], BM3A7=12,
BM3A2=[stringval1, stringval2], BM3A1=stringval, BM3A4=[true, false],
BM3A3=true}}","importStatus": "SUCCESS","remarks": ""
}]} {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4311) [Business Metadata Bulk Import] Wrong Line Number returned in failedImportInfoList
[
https://issues.apache.org/jira/browse/ATLAS-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4311:
Description:
The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line
Number
For instance, following is the data in template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval
hive_table,invalid_table@cm,BM3.BM3A1,stringval {code}
As seen above, on line #3, we have entity name as invalid_table@cm, this entity
is not existing in atlas.
But the businessmetadata/import API returns
{code:java}
{ "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "",
"importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found with
qualifiedName=invalid_table@cm" } ] } {code}
As seen above, Line number should have been returned as 3, but it is returned
as 2.
This probably is happening because we intrinsically ignore the first line in
the template file
was:
The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line
Number
For instance, following is the data in template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval
hive_table,invalid_table@cm,BM3.BM3A1,stringval {code}
As seen above, on line #3, we have entity name as invalid_table@cm, this entity
is not existing in atlas.
But the businessmetadata/import API returns
{code:java}
{ "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "",
"importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found with
qualifiedName=invalid_table@cm" } ] } {code}
As seen above, Line number should have been returned as 3, but it is returned
as 2.
This probably is happening because we intrinsically ignore the first line in
the template file
> [Business Metadata Bulk Import] Wrong Line Number returned in
> failedImportInfoList
> ---
>
> Key: ATLAS-4311
> URL: https://issues.apache.org/jira/browse/ATLAS-4311
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Minor
>
> The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line
> Number
> For instance, following is the data in template file
> {code:java}
> EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
>
> hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval
> hive_table,invalid_table@cm,BM3.BM3A1,stringval {code}
> As seen above, on line #3, we have entity name as invalid_table@cm, this
> entity is not existing in atlas.
> But the businessmetadata/import API returns
> {code:java}
> { "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "",
> "importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found
> with qualifiedName=invalid_table@cm" } ] } {code}
> As seen above, Line number should have been returned as 3, but it is returned
> as 2.
> This probably is happening because we intrinsically ignore the first line in
> the template file
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4311) [Business Metadata Bulk Import] Wrong Line Number returned in failedImportInfoList
Umesh Padashetty created ATLAS-4311:
---
Summary: [Business Metadata Bulk Import] Wrong Line Number
returned in failedImportInfoList
Key: ATLAS-4311
URL: https://issues.apache.org/jira/browse/ATLAS-4311
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line
Number
For instance, following is the data in template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval
hive_table,invalid_table@cm,BM3.BM3A1,stringval {code}
As seen above, on line #3, we have entity name as invalid_table@cm, this entity
is not existing in atlas.
But the businessmetadata/import API returns
{code:java}
{ "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "",
"importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found with
qualifiedName=invalid_table@cm" } ] } {code}
As seen above, Line number should have been returned as 3, but it is returned
as 2.
This probably is happening because we intrinsically ignore the first line in
the template file
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4305) [Glossary Bulk Import] Rename template file name from "template" to "template_glossary" to maintain parity with Business Metadata Bulk Import
[ https://issues.apache.org/jira/browse/ATLAS-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty reassigned ATLAS-4305: --- Assignee: Umesh Padashetty > [Glossary Bulk Import] Rename template file name from "template" to > "template_glossary" to maintain parity with Business Metadata Bulk Import > -- > > Key: ATLAS-4305 > URL: https://issues.apache.org/jira/browse/ATLAS-4305 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Minor > Attachments: Screenshot 2021-05-24 at 11.31.32 PM.png, Screenshot > 2021-05-24 at 11.31.48 PM.png > > > Atlas provides support to Bulk Import Business Metadata and Glossary. THe > user can download the template file and then bulk upload the data to atlas. > While the Business Metadata template file is named as > "template_business_metadata", Glossary Bulk Import template file is just > named as "template". This leads to confusion when the user downloads both the > template files and he/she has to open the file to confirm the template type > Proposal: Rename the template file to template_glossary > > !Screenshot 2021-05-24 at 11.31.32 PM.png! > > !Screenshot 2021-05-24 at 11.31.48 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4305) [Glossary Bulk Import] Rename template file name from "template" to "template_glossary" to maintain parity with Business Metadata Bulk Import
Umesh Padashetty created ATLAS-4305: --- Summary: [Glossary Bulk Import] Rename template file name from "template" to "template_glossary" to maintain parity with Business Metadata Bulk Import Key: ATLAS-4305 URL: https://issues.apache.org/jira/browse/ATLAS-4305 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: Screenshot 2021-05-24 at 11.31.32 PM.png, Screenshot 2021-05-24 at 11.31.48 PM.png Atlas provides support to Bulk Import Business Metadata and Glossary. THe user can download the template file and then bulk upload the data to atlas. While the Business Metadata template file is named as "template_business_metadata", Glossary Bulk Import template file is just named as "template". This leads to confusion when the user downloads both the template files and he/she has to open the file to confirm the template type Proposal: Rename the template file to template_glossary !Screenshot 2021-05-24 at 11.31.32 PM.png! !Screenshot 2021-05-24 at 11.31.48 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4304) [Business Metadata Bulk Import] [Beta UI] Bulk Import Business Metadata/Glossary options overlap
Umesh Padashetty created ATLAS-4304: --- Summary: [Business Metadata Bulk Import] [Beta UI] Bulk Import Business Metadata/Glossary options overlap Key: ATLAS-4304 URL: https://issues.apache.org/jira/browse/ATLAS-4304 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2021-05-24 at 11.31.32 PM.png, Screenshot 2021-05-24 at 11.31.48 PM.png As seen in the screenshot below, the sub drop downs overlap and the Business Metadata/Glossary in almost 50% hidden !Screenshot 2021-05-24 at 11.31.32 PM.png! !Screenshot 2021-05-24 at 11.31.48 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4303) [Business Metadata Bulk Import] Incorrect Error "invalid business attribute name" thrown while trying to assign BM attribute to non-applicable type
Umesh Padashetty created ATLAS-4303:
---
Summary: [Business Metadata Bulk Import] Incorrect Error "invalid
business attribute name" thrown while trying to assign BM attribute to
non-applicable type
Key: ATLAS-4303
URL: https://issues.apache.org/jira/browse/ATLAS-4303
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
While trying to Bulk Import Business Metadata, a row in the file where we try
to assign Business Metadata attribute to a non-applicable entity type, BM
import throws "invalid business attribute name"
This Error message is misleading since the BM attribute name is correct, but it
is just that it is not applicable to the type which the user has specified.
On similar lines, we have handled this case in 2 ways in the Entity > Business
Metadata attribute association
# We only show the applicable Business Metadata attributes types in the
drop-down
# And via the API, if the user tries to assign a Business Metadata attribute
to a non-applicable type, the API throws the ERROR
##
{code:java}
Invalid instance creation/updation parameters passed : Test BM 2: invalid
business-metadata for entity type hive_table {code}
We need to throw a similar error in the Business Metadata Bulk Import too, else
the error message for sure leads to confusion
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4247) "Advanced Search" is spelt as "Advance Search" in Atlas Beta UI
Umesh Padashetty created ATLAS-4247: --- Summary: "Advanced Search" is spelt as "Advance Search" in Atlas Beta UI Key: ATLAS-4247 URL: https://issues.apache.org/jira/browse/ATLAS-4247 Project: Atlas Issue Type: Bug Reporter: Umesh Padashetty Assignee: Umesh Padashetty Attachments: Screenshot 2021-04-16 at 6.58.02 PM.png, Screenshot 2021-04-16 at 6.58.20 PM.png !Screenshot 2021-04-16 at 6.58.02 PM.png! !Screenshot 2021-04-16 at 6.58.20 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4229) [Regression] [DSL-Advanced search] If the search query does not match any results, then Atlas UI keep loading forever
Umesh Padashetty created ATLAS-4229:
---
Summary: [Regression] [DSL-Advanced search] If the search query
does not match any results, then Atlas UI keep loading forever
Key: ATLAS-4229
URL: https://issues.apache.org/jira/browse/ATLAS-4229
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Reporter: Umesh Padashetty
Observing an issue in DSL (Advanced search), if the search query does not match
any results, then Atlas UI takes forever to return the results. It just wont
stop loading.
Whereas if there is a match, the results are returned almost immediately and
displayed on the UI.
On further checking, observed the below error in Console tab when the UI keeps
loading (when there is no match)
{code:java}
Uncaught TypeError: Cannot convert undefined or null to object
at Function.keys ()
at N.d.tableRender (SearchResultLayoutView.js?bust=1615290982036:332)
at SearchResultLayoutView.js?bust=1615290982036:365
at Object.execCb (require.js?bust=1615290982036:1)
at t.check (require.js?bust=1615290982036:1)
at t. (require.js?bust=1615290982036:1)
at require.js?bust=1615290982036:1
at require.js?bust=1615290982036:1
at each (require.js?bust=1615290982036:1)
at t.emit (require.js?bust=1615290982036:1) {code}
Checked the CURL call directly (case where there are no match)
Response:
{code:java}
{
"queryType": "DSL",
"queryText": "`hive_db` where name=\"some_invalid_db\"",
"approximateCount": -1
} {code}
Hence the issue is in UI alone and seems like a regression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4204) Hive Hook: Improve HS2 Message Sending
[ https://issues.apache.org/jira/browse/ATLAS-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17302286#comment-17302286 ] Umesh Padashetty commented on ATLAS-4204: - +1. This is an excellent improvement, will solve many issues w.r.t. audits too. > Hive Hook: Improve HS2 Message Sending > -- > > Key: ATLAS-4204 > URL: https://issues.apache.org/jira/browse/ATLAS-4204 > Project: Atlas > Issue Type: Improvement > Components: hive-integration >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > > *Background* > HiveServer2 hook for Atlas sends notification message for both metadata (DDL > operations) and lineage (DML operations). > Hive Metastore (HMS) hook already sends metadata information to Atlas. These > messages are all DDL operations. > So duplicate messages about object updates are sent to Atlas. > Atlas processes these messages like any other. > This is additional processing time and increased volume. There is also a > potential of incorrect data being updated within Atlas if the sequence of > messages from HMS and HS2 gets changed. > *Solution* > This improvement will send only lineage messages from HS2 hook. All the DDL > (schema definition) messages will continue be sent from HMS hook (no change > here). > This will also reduce the volume of messages sent to Atlas from hive server2 > and will help improve performance by avoiding processing duplicate messages. > The improvement can be used via a configuration parameter. That way existing > behavior continues as is. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4207) Typo in dhasboardv2/v3 Enum.js Enums.serverAudits.SERVER_STATE_PASSIVE value
[ https://issues.apache.org/jira/browse/ATLAS-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17302277#comment-17302277 ] Umesh Padashetty commented on ATLAS-4207: - Review board link: https://reviews.apache.org/r/73231/ > Typo in dhasboardv2/v3 Enum.js Enums.serverAudits.SERVER_STATE_PASSIVE value > > > Key: ATLAS-4207 > URL: https://issues.apache.org/jira/browse/ATLAS-4207 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4207.patch > > > SERVER_STATE_PASSIVE is defined as "Server Statae Passive". State is spelt as > Statae -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4207) Typo in dhasboardv2/v3 Enum.js Enums.serverAudits.SERVER_STATE_PASSIVE value
Umesh Padashetty created ATLAS-4207: --- Summary: Typo in dhasboardv2/v3 Enum.js Enums.serverAudits.SERVER_STATE_PASSIVE value Key: ATLAS-4207 URL: https://issues.apache.org/jira/browse/ATLAS-4207 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Assignee: Umesh Padashetty SERVER_STATE_PASSIVE is defined as "Server Statae Passive". State is spelt as Statae -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4203) [Business Metadata] Issue with saving floating point numbers in case of attributes of 'float' type
Umesh Padashetty created ATLAS-4203: --- Summary: [Business Metadata] Issue with saving floating point numbers in case of attributes of 'float' type Key: ATLAS-4203 URL: https://issues.apache.org/jira/browse/ATLAS-4203 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: After save.png, Before save.png A value entered as -234567890123456.12 gets saved as -23456789400 A value entered as 234567890123456.12 gets saved as 23456789400 Screenshots attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities
[
https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4171:
Description:
Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
entities when the list of authorised and unauthorised entities list is passed.
Curl:
{code:java}
curl --location --request DELETE
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
\--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
We need to implement one of the flag ignoreUnauthorisedGuids,
isSkipFailedEntities, skipFailedEntities similar to Bulk DELETE API
was:
Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
entities when the list of authorised and unauthorised entities list is passed.
Curl:
{code:java}
curl --location --request DELETE
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
\--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
We need to implement one of the flag ignoreUnauthorisedGuids,
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
POST API
> Authorisation : Bulk entity DELETE API doesn't delete authorised entities
> -
>
> Key: ATLAS-4171
> URL: https://issues.apache.org/jira/browse/ATLAS-4171
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Assignee: chaitali borole
>Priority: Major
>
> Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
> entities when the list of authorised and unauthorised entities list is passed.
> Curl:
> {code:java}
> curl --location --request DELETE
> 'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
> \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
> 'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
> We need to implement one of the flag ignoreUnauthorisedGuids,
> isSkipFailedEntities, skipFailedEntities similar to Bulk DELETE API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities
[
https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4171:
Description:
Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
entities when the list of authorised and unauthorised entities list is passed.
Curl:
{code:java}
curl --location --request DELETE
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
\--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
We need to implement one of the flag ignoreUnauthorisedGuids,
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
POST API
was:
Bulk entity DELETE API doesn't delete authorised entities when the list of
authorised and unauthorised entities list is passed.
Curl:
{code:java}
curl --location --request DELETE
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
\--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
We need to implement one of the flag ignoreUnauthorisedGuids,
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
POST API
> Authorisation : Bulk entity DELETE API doesn't delete authorised entities
> -
>
> Key: ATLAS-4171
> URL: https://issues.apache.org/jira/browse/ATLAS-4171
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Major
>
> Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised
> entities when the list of authorised and unauthorised entities list is passed.
> Curl:
> {code:java}
> curl --location --request DELETE
> 'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
> \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
> 'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
> We need to implement one of the flag ignoreUnauthorisedGuids,
> isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
> POST API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4172) Authorisation : Bulk create/update entity POST API doesn't create/update authorised entities
Umesh Padashetty created ATLAS-4172:
---
Summary: Authorisation : Bulk create/update entity POST API
doesn't create/update authorised entities
Key: ATLAS-4172
URL: https://issues.apache.org/jira/browse/ATLAS-4172
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
API : /api/atlas/v2/entity/bulk
Body :
{code:java}
{ "entities":[ {"authorised_1"}, {"unauthorised_1"}, {"authorised_2"} ] } {code}
Consider a user posts the body which contains
entity1 of type1 he is authorised ,
entity2 of type2 he is not authorised ,
entity3 of type3 he is authorised
The request returns 403 since of the entities is unauthorized.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities
[
https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4171:
Description:
Bulk entity DELETE API doesn't delete authorised entities when the list of
authorised and unauthorised entities list is passed.
Curl:
{code:java}
curl --location --request DELETE
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
\--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
We need to implement one of the flag ignoreUnauthorisedGuids,
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
POST API
was:
Similar to [CDPD-13466|https://jira.cloudera.com/browse/CDPD-13466], Bulk
entity DELETE API doesn't delete authorised entities when the list of
authorised and unauthorised entities list is passed.
Curl:
{code:java}
curl --location --request DELETE
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
\--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
We need to implement one of the flag ignoreUnauthorisedGuids,
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
POST API
> Authorisation : Bulk entity DELETE API doesn't delete authorised entities
> -
>
> Key: ATLAS-4171
> URL: https://issues.apache.org/jira/browse/ATLAS-4171
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Major
>
> Bulk entity DELETE API doesn't delete authorised entities when the list of
> authorised and unauthorised entities list is passed.
> Curl:
> {code:java}
> curl --location --request DELETE
> 'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
> \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
> 'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
> We need to implement one of the flag ignoreUnauthorisedGuids,
> isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
> POST API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities
Umesh Padashetty created ATLAS-4171:
---
Summary: Authorisation : Bulk entity DELETE API doesn't delete
authorised entities
Key: ATLAS-4171
URL: https://issues.apache.org/jira/browse/ATLAS-4171
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
Similar to [CDPD-13466|https://jira.cloudera.com/browse/CDPD-13466], Bulk
entity DELETE API doesn't delete authorised entities when the list of
authorised and unauthorised entities list is passed.
Curl:
{code:java}
curl --location --request DELETE
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
\--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0' {code}
We need to implement one of the flag ignoreUnauthorisedGuids,
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity
POST API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4161) basic/quick search on system attribute Classification(s) is_null returns few entities with classification too
Umesh Padashetty created ATLAS-4161: --- Summary: basic/quick search on system attribute Classification(s) is_null returns few entities with classification too Key: ATLAS-4161 URL: https://issues.apache.org/jira/browse/ATLAS-4161 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: (Type _ALL_ENTITY_TYPES (AND (Classification(s) is_null )) ) AND ( Query table_wtotg).png, (hive_table (AND (Classification(s) is_null )) ) AND (Query table_wtotg).png Results for: ( Type: hive_table (AND (Classification(s) is_null )) ) AND ( Query: table_wtotg ) !(hive_table (AND (Classification(s) is_null )) ) AND (Query table_wtotg).png|width=1067,height=392! Results for: ( Type: _ALL_ENTITY_TYPES (AND (Classification(s) is_null )) ) AND ( Query: table_wtotg ) !(Type _ALL_ENTITY_TYPES (AND (Classification(s) is_null )) ) AND ( Query table_wtotg).png|width=925,height=345! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4156) aggregationMetrics is missing in quick_search GET/POST API when “typeName”: “_ALL_ENTITY_TYPES”
Umesh Padashetty created ATLAS-4156:
---
Summary: aggregationMetrics is missing in quick_search GET/POST
API when “typeName”: “_ALL_ENTITY_TYPES”
Key: ATLAS-4156
URL: https://issues.apache.org/jira/browse/ATLAS-4156
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
curl
{code:java}
curl --location --request POST 'https://host:port/api/atlas/v2/search/quick'
\--header 'Content-Type: application/json' \--header 'X-XSRF-HEADER: ""'
\--header 'Authorization: Basic aHJ0X3FhOlBhc3N3b3JkQDEyMw==' \--header
'Cookie: ATLASSESSIONID=node012fu7y9lgt9ad1wli0q8s5v5yo70333.node0' \--data-raw
'{"excludeDeletedEntities": false,"includeSubClassifications":
true,"includeSubTypes": true,"tagFilters": null,
"attributes": [],"query": "*mrugd","typeName":
"_ALL_ENTITY_TYPES","entityFilters": {"condition":
"OR","criterion": []},"classification": null,
"childClassification": null,"limit": 100,"offset": 0}'
{code}
aggregation_metrics returned is
{code:java}
"aggregationMetrics": {
"__typeName": [],
"__state": [],
"Asset.owner": []
} {code}
currently "_ALL_ENTITY_TYPES" is not handled in freetextsearch. Hence this is
the reason why aggregationMetrics is missing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4119) Atlas REST API Documentation has links leading to 404
[ https://issues.apache.org/jira/browse/ATLAS-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4119: Attachment: Screenshot 2021-02-01 at 6.32.46 PM.png > Atlas REST API Documentation has links leading to 404 > - > > Key: ATLAS-4119 > URL: https://issues.apache.org/jira/browse/ATLAS-4119 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2021-02-01 at 6.27.30 PM.png, Screenshot > 2021-02-01 at 6.32.46 PM.png > > > On clicking the links on REST API Documentation page, for instance, > [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] > it leads to "Not Found The requested URL was not found on this server." > > On click of the hyperlink below > !Screenshot 2021-02-01 at 6.27.30 PM.png! > - > The following error throws > !Screenshot 2021-02-01 at 6.27.43 PM.png! > The same applies for links found in the below pages too > * [https://atlas.apache.org/api/v2/resource_EntityREST.html] > * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] > * [https://atlas.apache.org/api/v2/resource_LineageREST.html] > * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] > * [https://atlas.apache.org/api/v2/resource_TypesREST.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4119) Atlas REST API Documentation has links leading to 404
[ https://issues.apache.org/jira/browse/ATLAS-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4119: Description: On clicking the links on REST API Documentation page, for instance, [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] it leads to "Not Found The requested URL was not found on this server." On click of the hyperlink below !Screenshot 2021-02-01 at 6.27.30 PM.png! - The following error throws !Screenshot 2021-02-01 at 6.32.46 PM.png! The same applies for links found in the below pages too * [https://atlas.apache.org/api/v2/resource_EntityREST.html] * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] * [https://atlas.apache.org/api/v2/resource_LineageREST.html] * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] * [https://atlas.apache.org/api/v2/resource_TypesREST.html] was: On clicking the links on REST API Documentation page, for instance, [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] it leads to "Not Found The requested URL was not found on this server." On click of the hyperlink below !Screenshot 2021-02-01 at 6.27.30 PM.png! - The following error throws !Screenshot 2021-02-01 at 6.27.43 PM.png! The same applies for links found in the below pages too * [https://atlas.apache.org/api/v2/resource_EntityREST.html] * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] * [https://atlas.apache.org/api/v2/resource_LineageREST.html] * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] * [https://atlas.apache.org/api/v2/resource_TypesREST.html] > Atlas REST API Documentation has links leading to 404 > - > > Key: ATLAS-4119 > URL: https://issues.apache.org/jira/browse/ATLAS-4119 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2021-02-01 at 6.27.30 PM.png, Screenshot > 2021-02-01 at 6.32.46 PM.png > > > On clicking the links on REST API Documentation page, for instance, > [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] > it leads to "Not Found The requested URL was not found on this server." > > On click of the hyperlink below > !Screenshot 2021-02-01 at 6.27.30 PM.png! > - > The following error throws > !Screenshot 2021-02-01 at 6.32.46 PM.png! > The same applies for links found in the below pages too > * [https://atlas.apache.org/api/v2/resource_EntityREST.html] > * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] > * [https://atlas.apache.org/api/v2/resource_LineageREST.html] > * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] > * [https://atlas.apache.org/api/v2/resource_TypesREST.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4119) Atlas REST API Documentation has links leading to 404
[ https://issues.apache.org/jira/browse/ATLAS-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4119: Attachment: (was: Screenshot 2021-02-01 at 6.27.43 PM.png) > Atlas REST API Documentation has links leading to 404 > - > > Key: ATLAS-4119 > URL: https://issues.apache.org/jira/browse/ATLAS-4119 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2021-02-01 at 6.27.30 PM.png, Screenshot > 2021-02-01 at 6.32.46 PM.png > > > On clicking the links on REST API Documentation page, for instance, > [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] > it leads to "Not Found The requested URL was not found on this server." > > On click of the hyperlink below > !Screenshot 2021-02-01 at 6.27.30 PM.png! > - > The following error throws > !Screenshot 2021-02-01 at 6.32.46 PM.png! > The same applies for links found in the below pages too > * [https://atlas.apache.org/api/v2/resource_EntityREST.html] > * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] > * [https://atlas.apache.org/api/v2/resource_LineageREST.html] > * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] > * [https://atlas.apache.org/api/v2/resource_TypesREST.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4119) Atlas REST API Documentation has links leading to 404
[ https://issues.apache.org/jira/browse/ATLAS-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4119: Description: On clicking the links on REST API Documentation page, for instance, [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] it leads to "Not Found The requested URL was not found on this server." On click of the hyperlink below !Screenshot 2021-02-01 at 6.27.30 PM.png! - The following error throws !Screenshot 2021-02-01 at 6.27.43 PM.png! The same applies for links found in the below pages too * [https://atlas.apache.org/api/v2/resource_EntityREST.html] * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] * [https://atlas.apache.org/api/v2/resource_LineageREST.html] * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] * [https://atlas.apache.org/api/v2/resource_TypesREST.html] was: On clicking the links on REST API Documentation page, for instance, [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] it leads to "Not Found The requested URL was not found on this server." On click of they hyperlink below !Screenshot 2021-02-01 at 6.27.30 PM.png! The following error throws !Screenshot 2021-02-01 at 6.27.43 PM.png! The same applies for links found in the below pages too * [https://atlas.apache.org/api/v2/resource_EntityREST.html] * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] * [https://atlas.apache.org/api/v2/resource_LineageREST.html] * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] * https://atlas.apache.org/api/v2/resource_TypesREST.html > Atlas REST API Documentation has links leading to 404 > - > > Key: ATLAS-4119 > URL: https://issues.apache.org/jira/browse/ATLAS-4119 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2021-02-01 at 6.27.30 PM.png, Screenshot > 2021-02-01 at 6.27.43 PM.png > > > On clicking the links on REST API Documentation page, for instance, > [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] > it leads to "Not Found The requested URL was not found on this server." > > On click of the hyperlink below > !Screenshot 2021-02-01 at 6.27.30 PM.png! > - > The following error throws > !Screenshot 2021-02-01 at 6.27.43 PM.png! > The same applies for links found in the below pages too > * [https://atlas.apache.org/api/v2/resource_EntityREST.html] > * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] > * [https://atlas.apache.org/api/v2/resource_LineageREST.html] > * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] > * [https://atlas.apache.org/api/v2/resource_TypesREST.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4119) Atlas REST API Documentation has links leading to 404
Umesh Padashetty created ATLAS-4119: --- Summary: Atlas REST API Documentation has links leading to 404 Key: ATLAS-4119 URL: https://issues.apache.org/jira/browse/ATLAS-4119 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2021-02-01 at 6.27.30 PM.png, Screenshot 2021-02-01 at 6.27.43 PM.png On clicking the links on REST API Documentation page, for instance, [https://atlas.apache.org/api/v2/resource_DiscoveryREST.html|https://atlas.apache.org/api/v2/resource_DiscoveryREST.html,] it leads to "Not Found The requested URL was not found on this server." On click of they hyperlink below !Screenshot 2021-02-01 at 6.27.30 PM.png! The following error throws !Screenshot 2021-02-01 at 6.27.43 PM.png! The same applies for links found in the below pages too * [https://atlas.apache.org/api/v2/resource_EntityREST.html] * [https://atlas.apache.org/api/v2/resource_GlossaryREST.html] * [https://atlas.apache.org/api/v2/resource_LineageREST.html] * [https://atlas.apache.org/api/v2/resource_RelationshipREST.html] * https://atlas.apache.org/api/v2/resource_TypesREST.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4105) table details are set to null for a dropped hbase_column_family
[ https://issues.apache.org/jira/browse/ATLAS-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17272597#comment-17272597 ] Umesh Padashetty commented on ATLAS-4105: - Thanks, [~mandar_va]. But as a repercussion, this causes ATLAS-3551 ATLAS-3551 is still in PATCH AVAILABLE state, can we please merge the fix? > table details are set to null for a dropped hbase_column_family > --- > > Key: ATLAS-4105 > URL: https://issues.apache.org/jira/browse/ATLAS-4105 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Assignee: Mandar Ambawane >Priority: Minor > Attachments: Screenshot 2021-01-20 at 12.19.22 AM.png, Screenshot > 2021-01-20 at 12.21.50 AM.png, Screenshot 2021-01-20 at 12.22.01 AM.png > > > Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE > whereas col_fam_kpgfu_1 is DELETED. > On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is > ACTIVE, the table info is set to hbase_table_endlu > whereas for col_fam_kpgfu_1 which is DELETED, it is set to N/A (UI displays > null values as N/A) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4105) table details are set to null for a dropped hbase_column_family
[ https://issues.apache.org/jira/browse/ATLAS-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4105: Description: Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE whereas col_fam_kpgfu_1 is DELETED. On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is ACTIVE, the table info is set to hbase_table_endlu whereas for col_fam_kpgfu_1 which is DELETED, it is set to N/A (UI displays null values as N/A) was: Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE whereas col_fam_kpgfu_1 is DELETED. On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is ACTIVE, the table info is set to hbase_table_endlu whereas for col_fam_kpgfu_1 which is DELETED, it i set to N/A (UI displays null values as N/A) !Screenshot 2021-01-20 at 12.19.22 AM.png! > table details are set to null for a dropped hbase_column_family > --- > > Key: ATLAS-4105 > URL: https://issues.apache.org/jira/browse/ATLAS-4105 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Umesh Padashetty >Priority: Minor > Attachments: Screenshot 2021-01-20 at 12.19.22 AM.png, Screenshot > 2021-01-20 at 12.21.50 AM.png, Screenshot 2021-01-20 at 12.22.01 AM.png > > > Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE > whereas col_fam_kpgfu_1 is DELETED. > On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is > ACTIVE, the table info is set to hbase_table_endlu > whereas for col_fam_kpgfu_1 which is DELETED, it is set to N/A (UI displays > null values as N/A) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4105) table details are set to null for a dropped hbase_column_family
Umesh Padashetty created ATLAS-4105: --- Summary: table details are set to null for a dropped hbase_column_family Key: ATLAS-4105 URL: https://issues.apache.org/jira/browse/ATLAS-4105 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: Screenshot 2021-01-20 at 12.19.22 AM.png, Screenshot 2021-01-20 at 12.21.50 AM.png, Screenshot 2021-01-20 at 12.22.01 AM.png Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE whereas col_fam_kpgfu_1 is DELETED. On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is ACTIVE, the table info is set to hbase_table_endlu whereas for col_fam_kpgfu_1 which is DELETED, it i set to N/A (UI displays null values as N/A) !Screenshot 2021-01-20 at 12.19.22 AM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4072) spark_column_lineage missing for insert into select * queries run via spark-shell
[
https://issues.apache.org/jira/browse/ATLAS-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4072:
Attachment: Screenshot 2020-12-11 at 1.34.24 AM.png
> spark_column_lineage missing for insert into select * queries run via
> spark-shell
> -
>
> Key: ATLAS-4072
> URL: https://issues.apache.org/jira/browse/ATLAS-4072
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-12-11 at 1.29.39 AM.png, Screenshot
> 2020-12-11 at 1.34.24 AM.png
>
>
> From the spark-shell, ran the below queries
> * spark.sql("create table umesh(name string)");
> * spark.sql("create table umesh_insert(name string)");
> * spark.sql("insert into umesh_insert select * from umesh");
> There is a spark_process created between umesh and umesh_insert tables, but
> the spark_column_lineage is missing between the umesh.name and
> umesh_insert.name columns
> !Screenshot 2020-12-11 at 1.29.39 AM.png|width=438,height=435!
> To cross verify the behavior, I ran similar hive queries via beeline and
> found out that along with hive_process being created between umesh_hive and
> umesh_hive_insert tables, hive_column_lineage is created between
> umesh_hive.name and umesh_hive_insert.name columns.
> Queries run via beeline
> * create table umesh_hive(name string);
> * create table umesh_hive_insert(name string);
> * insert into umesh_hive_insert select * from umesh_hive;
> !Screenshot 2020-12-11 at 1.34.24 AM.png|width=441,height=548!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4072) spark_column_lineage missing for insert into select * queries run via spark-shell
[
https://issues.apache.org/jira/browse/ATLAS-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4072:
Attachment: Screenshot 2020-12-11 at 1.29.39 AM.png
> spark_column_lineage missing for insert into select * queries run via
> spark-shell
> -
>
> Key: ATLAS-4072
> URL: https://issues.apache.org/jira/browse/ATLAS-4072
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-12-11 at 1.29.39 AM.png, Screenshot
> 2020-12-11 at 1.34.24 AM.png
>
>
> From the spark-shell, ran the below queries
> * spark.sql("create table umesh(name string)");
> * spark.sql("create table umesh_insert(name string)");
> * spark.sql("insert into umesh_insert select * from umesh");
> There is a spark_process created between umesh and umesh_insert tables, but
> the spark_column_lineage is missing between the umesh.name and
> umesh_insert.name columns
> !Screenshot 2020-12-11 at 1.29.39 AM.png|width=438,height=435!
> To cross verify the behavior, I ran similar hive queries via beeline and
> found out that along with hive_process being created between umesh_hive and
> umesh_hive_insert tables, hive_column_lineage is created between
> umesh_hive.name and umesh_hive_insert.name columns.
> Queries run via beeline
> * create table umesh_hive(name string);
> * create table umesh_hive_insert(name string);
> * insert into umesh_hive_insert select * from umesh_hive;
> !Screenshot 2020-12-11 at 1.34.24 AM.png|width=441,height=548!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4072) spark_column_lineage missing for insert into select * queries run via spark-shell
[
https://issues.apache.org/jira/browse/ATLAS-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4072:
Description:
>From the spark-shell, ran the below queries
* spark.sql("create table umesh(name string)");
* spark.sql("create table umesh_insert(name string)");
* spark.sql("insert into umesh_insert select * from umesh");
There is a spark_process created between umesh and umesh_insert tables, but the
spark_column_lineage is missing between the umesh.name and umesh_insert.name
columns
!Screenshot 2020-12-11 at 1.29.39 AM.png!
To cross verify the behavior, I ran similar hive queries via beeline and found
out that along with hive_process being created between umesh_hive and
umesh_hive_insert tables, hive_column_lineage is created between
umesh_hive.name and umesh_hive_insert.name columns.
Queries run via beeline
* create table umesh_hive(name string);
* create table umesh_hive_insert(name string);
* insert into umesh_hive_insert select * from umesh_hive;
!Screenshot 2020-12-11 at 1.34.24 AM.png!
was:
>From the spark-shell, ran the below queries
* spark.sql("create table umesh(name string)");
* spark.sql("create table umesh_insert(name string)");
* spark.sql("insert into umesh_insert select * from umesh");
There is a spark_process created between umesh and umesh_insert tables, but the
spark_column_lineage is missing between the umesh.name and umesh_insert.name
columns
!Screenshot 2020-12-11 at 1.29.39 AM.png|width=438,height=435!
To cross verify the behavior, I ran similar hive queries via beeline and found
out that along with hive_process being created between umesh_hive and
umesh_hive_insert tables, hive_column_lineage is created between
umesh_hive.name and umesh_hive_insert.name columns.
Queries run via beeline
* create table umesh_hive(name string);
* create table umesh_hive_insert(name string);
* insert into umesh_hive_insert select * from umesh_hive;
!Screenshot 2020-12-11 at 1.34.24 AM.png|width=441,height=548!
> spark_column_lineage missing for insert into select * queries run via
> spark-shell
> -
>
> Key: ATLAS-4072
> URL: https://issues.apache.org/jira/browse/ATLAS-4072
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-12-11 at 1.29.39 AM.png, Screenshot
> 2020-12-11 at 1.34.24 AM.png
>
>
> From the spark-shell, ran the below queries
> * spark.sql("create table umesh(name string)");
> * spark.sql("create table umesh_insert(name string)");
> * spark.sql("insert into umesh_insert select * from umesh");
> There is a spark_process created between umesh and umesh_insert tables, but
> the spark_column_lineage is missing between the umesh.name and
> umesh_insert.name columns
> !Screenshot 2020-12-11 at 1.29.39 AM.png!
> To cross verify the behavior, I ran similar hive queries via beeline and
> found out that along with hive_process being created between umesh_hive and
> umesh_hive_insert tables, hive_column_lineage is created between
> umesh_hive.name and umesh_hive_insert.name columns.
> Queries run via beeline
> * create table umesh_hive(name string);
> * create table umesh_hive_insert(name string);
> * insert into umesh_hive_insert select * from umesh_hive;
> !Screenshot 2020-12-11 at 1.34.24 AM.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4072) spark_column_lineage missing for insert into select * queries run via spark-shell
Umesh Padashetty created ATLAS-4072:
---
Summary: spark_column_lineage missing for insert into select *
queries run via spark-shell
Key: ATLAS-4072
URL: https://issues.apache.org/jira/browse/ATLAS-4072
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
>From the spark-shell, ran the below queries
* spark.sql("create table umesh(name string)");
* spark.sql("create table umesh_insert(name string)");
* spark.sql("insert into umesh_insert select * from umesh");
There is a spark_process created between umesh and umesh_insert tables, but the
spark_column_lineage is missing between the umesh.name and umesh_insert.name
columns
!Screenshot 2020-12-11 at 1.29.39 AM.png|width=438,height=435!
To cross verify the behavior, I ran similar hive queries via beeline and found
out that along with hive_process being created between umesh_hive and
umesh_hive_insert tables, hive_column_lineage is created between
umesh_hive.name and umesh_hive_insert.name columns.
Queries run via beeline
* create table umesh_hive(name string);
* create table umesh_hive_insert(name string);
* insert into umesh_hive_insert select * from umesh_hive;
!Screenshot 2020-12-11 at 1.34.24 AM.png|width=441,height=548!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties
[ https://issues.apache.org/jira/browse/ATLAS-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17247058#comment-17247058 ] Umesh Padashetty commented on ATLAS-4066: - !Screenshot 2020-12-10 at 12.56.11 PM.png! There's a JS error on click. > [UI] Attribute Filter: 'is null' and 'is not null' does not work for > user-defined properties > - > > Key: ATLAS-4066 > URL: https://issues.apache.org/jira/browse/ATLAS-4066 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot > 2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png, > Screenshot 2020-12-10 at 12.56.11 PM.png > > > For user-defined properties, currently only 'contains' filter is working. > !Screenshot 2020-12-08 at 11.56.54 PM.png! > When I select either 'is null' or 'is not null', nothing happens (both when i > click on apply or search) > !Screenshot 2020-12-08 at 11.56.45 PM.png! > !Screenshot 2020-12-08 at 11.56.36 PM.png! > 'is null' or 'is not null' works fine for all other System attributes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties
[ https://issues.apache.org/jira/browse/ATLAS-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4066: Attachment: Screenshot 2020-12-10 at 12.56.11 PM.png > [UI] Attribute Filter: 'is null' and 'is not null' does not work for > user-defined properties > - > > Key: ATLAS-4066 > URL: https://issues.apache.org/jira/browse/ATLAS-4066 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot > 2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png, > Screenshot 2020-12-10 at 12.56.11 PM.png > > > For user-defined properties, currently only 'contains' filter is working. > !Screenshot 2020-12-08 at 11.56.54 PM.png! > When I select either 'is null' or 'is not null', nothing happens (both when i > click on apply or search) > !Screenshot 2020-12-08 at 11.56.45 PM.png! > !Screenshot 2020-12-08 at 11.56.36 PM.png! > 'is null' or 'is not null' works fine for all other System attributes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4069) Export/Importing a recreated deleted entity has the relationshipStatus set to ACTIVE instead of DELETED for deleted entity
[
https://issues.apache.org/jira/browse/ATLAS-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4069:
Description:
Run the below queries:
# create database IF NOT EXISTS database34_${var:rand_str};
# create table IF NOT EXISTS
database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
date);
# drop table database34_${var:rand_str}.table_${var:rand_str}_34;
# drop database database34_${var:rand_str};
# create database IF NOT EXISTS database34_${var:rand_str};
# create table IF NOT EXISTS
database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
date);
As you can see, create a database/table, followed by drop statements, and then
recreated them.
Hence, there are 2 entities with same name, but the state is different (1 is
ACTIVE, 1 is DELETED).
Text compare: !Screenshot 2020-12-09 at 5.51.10 PM.png|width=799,height=134!
was:
Run the below queries:
# create database IF NOT EXISTS database34_${var:rand_str};
# create table IF NOT EXISTS
database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
date);
# drop table database34_${var:rand_str}.table_${var:rand_str}_34;
# drop database database34_${var:rand_str};
# create database IF NOT EXISTS database34_${var:rand_str};
# create table IF NOT EXISTS
database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
date);
As you can see, create a database/table, followed by drop statements, and then
recreated them.
Hence, there are 2 entities with same name, but the state is different (1 is
ACTIVE, 1 is DELETED).
Text compare: !Screenshot 2020-12-09 at 5.51.10 PM.png!
> Export/Importing a recreated deleted entity has the relationshipStatus set to
> ACTIVE instead of DELETED for deleted entity
> --
>
> Key: ATLAS-4069
> URL: https://issues.apache.org/jira/browse/ATLAS-4069
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: Screenshot 2020-12-09 at 5.51.10 PM.png
>
>
> Run the below queries:
> # create database IF NOT EXISTS database34_${var:rand_str};
> # create table IF NOT EXISTS
> database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
> date);
> # drop table database34_${var:rand_str}.table_${var:rand_str}_34;
> # drop database database34_${var:rand_str};
> # create database IF NOT EXISTS database34_${var:rand_str};
> # create table IF NOT EXISTS
> database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
> date);
> As you can see, create a database/table, followed by drop statements, and
> then recreated them.
> Hence, there are 2 entities with same name, but the state is different (1 is
> ACTIVE, 1 is DELETED).
> Text compare: !Screenshot 2020-12-09 at 5.51.10 PM.png|width=799,height=134!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4070) hive_column_lineage .json and impala_column_lineage .json files are missing in /admin/export zip file
Umesh Padashetty created ATLAS-4070: --- Summary: hive_column_lineage .json and impala_column_lineage .json files are missing in /admin/export zip file Key: ATLAS-4070 URL: https://issues.apache.org/jira/browse/ATLAS-4070 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Currently hive_column_lineage .json and impala_column_lineage .json files are missing in /admin/export zip file. It is to be noted that spark_column_lineage .json is getting created fine But the important thing to note is, even though the hive_column_lineage .json and impala_column_lineage .json files are missing in /admin/export zip file, the hive_column_lineage and impala_column_lineage is getting imported to the target cluster properly. In the HDP world, we used to create the file hive_column_lineage .json, but we are no more creating it. Wanted to check if this is expected behaviour. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4069) Export/Importing a recreated deleted entity has the relationshipStatus set to ACTIVE instead of DELETED for deleted entity
Umesh Padashetty created ATLAS-4069:
---
Summary: Export/Importing a recreated deleted entity has the
relationshipStatus set to ACTIVE instead of DELETED for deleted entity
Key: ATLAS-4069
URL: https://issues.apache.org/jira/browse/ATLAS-4069
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.1.0
Reporter: Umesh Padashetty
Attachments: Screenshot 2020-12-09 at 5.51.10 PM.png
Run the below queries:
# create database IF NOT EXISTS database34_${var:rand_str};
# create table IF NOT EXISTS
database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
date);
# drop table database34_${var:rand_str}.table_${var:rand_str}_34;
# drop database database34_${var:rand_str};
# create database IF NOT EXISTS database34_${var:rand_str};
# create table IF NOT EXISTS
database34_${var:rand_str}.table_${var:rand_str}_34(id int,name string,dob
date);
As you can see, create a database/table, followed by drop statements, and then
recreated them.
Hence, there are 2 entities with same name, but the state is different (1 is
ACTIVE, 1 is DELETED).
Text compare: !Screenshot 2020-12-09 at 5.51.10 PM.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4067) In Entity Audits tab, show action as "user-defined properties added/updated/deleted" instead of plain 'Entity Updated'
[ https://issues.apache.org/jira/browse/ATLAS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4067: Description: Currently in the entity audits tab, we show actions as below: * Business Attribute(s) Updated * Classification Added * Label(s) Added !Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440! But for user-defined properties alone, we show "Entity Updated" for all the udp actions. !Screenshot 2020-12-09 at 12.57.59 AM.png|width=1028,height=292! This makes it very difficult to find out from the audits tab in which "Entity Update" action the udp was updated for an entity. Though the user can expand the operation and find out what happened with udp, this is not very intuitive was: Currently in the entity audits tab, we show actions as below: * Business Attribute(s) Updated * Classification Added * Label(s) Added !Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440! But for user-defined properties alone, we show "Entity Updated" for all the udp actions. !Screenshot 2020-12-09 at 12.57.59 AM.png|width=1239,height=352! This makes it very difficult to find out from the audits tab in which "Entity Update" action the udp was updated for an entity. Though the user can expand the operation and find out what happened with udp, this is not very intuitive > In Entity Audits tab, show action as "user-defined properties > added/updated/deleted" instead of plain 'Entity Updated' > -- > > Key: ATLAS-4067 > URL: https://issues.apache.org/jira/browse/ATLAS-4067 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2020-12-09 at 1.03.44 AM.png, Screenshot > 2020-12-09 at 12.57.59 AM.png > > > Currently in the entity audits tab, we show actions as below: > * Business Attribute(s) Updated > * Classification Added > * Label(s) Added > !Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440! > But for user-defined properties alone, we show "Entity Updated" for all the > udp actions. > !Screenshot 2020-12-09 at 12.57.59 AM.png|width=1028,height=292! > This makes it very difficult to find out from the audits tab in which "Entity > Update" action the udp was updated for an entity. > Though the user can expand the operation and find out what happened with udp, > this is not very intuitive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4067) In Entity Audits tab, show action as "user-defined properties added/updated/deleted" instead of plain 'Entity Updated'
Umesh Padashetty created ATLAS-4067: --- Summary: In Entity Audits tab, show action as "user-defined properties added/updated/deleted" instead of plain 'Entity Updated' Key: ATLAS-4067 URL: https://issues.apache.org/jira/browse/ATLAS-4067 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 2.1.0 Reporter: Umesh Padashetty Attachments: Screenshot 2020-12-09 at 1.03.44 AM.png, Screenshot 2020-12-09 at 12.57.59 AM.png Currently in the entity audits tab, we show actions as below: * Business Attribute(s) Updated * Classification Added * Label(s) Added !Screenshot 2020-12-09 at 1.03.44 AM.png! But for user-defined properties alone, we show "Entity Updated" for all the udp actions. !Screenshot 2020-12-09 at 12.57.59 AM.png! This makes it very difficult to find out from the audits tab in which "Entity Update" action the udp was updated for an entity. Though the user can expand the operation and find out what happened with udp, this is not very intuitive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4067) In Entity Audits tab, show action as "user-defined properties added/updated/deleted" instead of plain 'Entity Updated'
[ https://issues.apache.org/jira/browse/ATLAS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4067: Description: Currently in the entity audits tab, we show actions as below: * Business Attribute(s) Updated * Classification Added * Label(s) Added !Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440! But for user-defined properties alone, we show "Entity Updated" for all the udp actions. !Screenshot 2020-12-09 at 12.57.59 AM.png|width=1239,height=352! This makes it very difficult to find out from the audits tab in which "Entity Update" action the udp was updated for an entity. Though the user can expand the operation and find out what happened with udp, this is not very intuitive was: Currently in the entity audits tab, we show actions as below: * Business Attribute(s) Updated * Classification Added * Label(s) Added !Screenshot 2020-12-09 at 1.03.44 AM.png! But for user-defined properties alone, we show "Entity Updated" for all the udp actions. !Screenshot 2020-12-09 at 12.57.59 AM.png! This makes it very difficult to find out from the audits tab in which "Entity Update" action the udp was updated for an entity. Though the user can expand the operation and find out what happened with udp, this is not very intuitive > In Entity Audits tab, show action as "user-defined properties > added/updated/deleted" instead of plain 'Entity Updated' > -- > > Key: ATLAS-4067 > URL: https://issues.apache.org/jira/browse/ATLAS-4067 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2020-12-09 at 1.03.44 AM.png, Screenshot > 2020-12-09 at 12.57.59 AM.png > > > Currently in the entity audits tab, we show actions as below: > * Business Attribute(s) Updated > * Classification Added > * Label(s) Added > !Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440! > But for user-defined properties alone, we show "Entity Updated" for all the > udp actions. > !Screenshot 2020-12-09 at 12.57.59 AM.png|width=1239,height=352! > This makes it very difficult to find out from the audits tab in which "Entity > Update" action the udp was updated for an entity. > Though the user can expand the operation and find out what happened with udp, > this is not very intuitive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties
[ https://issues.apache.org/jira/browse/ATLAS-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4066: Component/s: atlas-webui > [UI] Attribute Filter: 'is null' and 'is not null' does not work for > user-defined properties > - > > Key: ATLAS-4066 > URL: https://issues.apache.org/jira/browse/ATLAS-4066 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot > 2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png > > > For user-defined properties, currently only 'contains' filter is working. > !Screenshot 2020-12-08 at 11.56.54 PM.png! > When I select either 'is null' or 'is not null', nothing happens (both when i > click on apply or search) > !Screenshot 2020-12-08 at 11.56.45 PM.png! > !Screenshot 2020-12-08 at 11.56.36 PM.png! > 'is null' or 'is not null' works fine for all other System attributes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties
[ https://issues.apache.org/jira/browse/ATLAS-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4066: Affects Version/s: 2.1.0 > [UI] Attribute Filter: 'is null' and 'is not null' does not work for > user-defined properties > - > > Key: ATLAS-4066 > URL: https://issues.apache.org/jira/browse/ATLAS-4066 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot > 2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png > > > For user-defined properties, currently only 'contains' filter is working. > !Screenshot 2020-12-08 at 11.56.54 PM.png! > When I select either 'is null' or 'is not null', nothing happens (both when i > click on apply or search) > !Screenshot 2020-12-08 at 11.56.45 PM.png! > !Screenshot 2020-12-08 at 11.56.36 PM.png! > 'is null' or 'is not null' works fine for all other System attributes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties
Umesh Padashetty created ATLAS-4066: --- Summary: [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties Key: ATLAS-4066 URL: https://issues.apache.org/jira/browse/ATLAS-4066 Project: Atlas Issue Type: Bug Reporter: Umesh Padashetty Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot 2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png For user-defined properties, currently only 'contains' filter is working. !Screenshot 2020-12-08 at 11.56.54 PM.png! When I select either 'is null' or 'is not null', nothing happens (both when i click on apply or search) !Screenshot 2020-12-08 at 11.56.45 PM.png! !Screenshot 2020-12-08 at 11.56.36 PM.png! 'is null' or 'is not null' works fine for all other System attributes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4049) Issue with few /admin APIs when hit on PASSIVE Atlas instance in HA mode
Umesh Padashetty created ATLAS-4049:
---
Summary: Issue with few /admin APIs when hit on PASSIVE Atlas
instance in HA mode
Key: ATLAS-4049
URL: https://issues.apache.org/jira/browse/ATLAS-4049
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.1.0
Reporter: Umesh Padashetty
Atlas supports the following types of /admin APIs
# /version
# /audits
# /purge
# /metrics
# /status
# /export
# /import
# /patches
# /checkstate
# /activeSearches/\{id}
# /activeSearches
# /audit/\{auditGuid}/details
# /expimp/audit
# /server/\{serverName}
# /importfile
# /stack
# /session
Observing issues when these APIs are hit on PASSIVE Atlas instance in HA mode
Following APIs do not have any issue, when hit on ACTIVE or PASSIVE instance,
they produce the same output
# /version
# /status
# /session
# /stack
# /patches
# /activeSearches
# /activeSearches/\{id}
# /checkstate
But the following APIs have issue, when hit on the PASSIVE instance, they
either produce partial information, or they throw an ERROR.
* /audits
** Error:
{code:java}
{"errorCode":"ATLAS-400-00-00A","errorMessage":"__AtlasAuditEntry:
Unknown/invalid typename"} {code}
* /purge
** Error:
{code:java}
{"errorCode":"ATLAS-400-00-014","errorMessage":"Type ENTITY with name
aws_s3_v2_object does not exist"} {code}
* /export (I understand this is by design, so can be ignored?)
** Error:
{code:java}
2020-11-24 18:06:59,250 ERROR - [etp402695541-112:] ~ URL not supported in HA
mode: /api/atlas/admin/export (ActiveServerFilter:120) 2020-11-24 18:06:59,252
INFO - [etp402695541-112:] ~ Not active. Redirecting to
https://quasar-jfuidh-4.quasar-jfuidh.root.hwx.site:31443/api/atlas/admin/export
(ActiveServerFilter:172) {code}
* /import (I understand this is by design, so can be ignored?)
** Error:
{code:java}
2020-11-24 18:07:22,702 ERROR - [etp402695541-118:] ~ URL not supported in HA
mode: /api/atlas/admin/import (ActiveServerFilter:120) 2020-11-24 18:07:22,704
INFO - [etp402695541-118:] ~ Not active. Redirecting to
https://quasar-jfuidh-4.quasar-jfuidh.root.hwx.site:31443/api/atlas/admin/import
(ActiveServerFilter:172) {code}
* /importfile (I understand this is by design, so can be ignored?)
** Error:
{code:java}
2020-11-24 18:07:22,702 ERROR - [etp402695541-118:] ~ URL not supported in HA
mode: /api/atlas/admin/import (ActiveServerFilter:120) 2020-11-24 18:07:22,704
INFO - [etp402695541-118:] ~ Not active. Redirecting to
https://quasar-jfuidh-4.quasar-jfuidh.root.hwx.site:31443/api/atlas/admin/import
(ActiveServerFilter:172) {code}
* /audit/\{auditGuid}/details
** Error:
{code:java}
{ "errorCode": "ATLAS-404-00-001", "errorMessage": "Given typename
__AtlasAuditEntry was invalid" } {code}
* /server/\{serverName}
** Error:
{code:java}
There was an error processing your request. It has been logged (ID
a52953c92b609fb8). 2020-11-24 18:05:32,259 ERROR - [etp402695541-70 -
47fbcd4a-e547-4bba-b12b-af018e33a893:] ~ Error handling a request:
a52953c92b609fb8 (ExceptionMapperUtil:32) java.lang.NullPointerException {code}
* /metrics
** Error:
{code:java}
Returns only partial information {code}
* /expimp/audit
** Error:
{code:java}
{ "errorCode": "ATLAS-400-00-00A", "errorMessage": "__ExportImportAuditEntry:
Unknown/invalid typename" } {code}
The case when an /admin API is hit on the PASSIVE instance, we should either
return a proper response, or we should redirect the request to the ACTIVE
instance. Providing partial information/error seems to be incorrect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4048) Issue with Business Metadata in Export/Import APIs
Umesh Padashetty created ATLAS-4048: --- Summary: Issue with Business Metadata in Export/Import APIs Key: ATLAS-4048 URL: https://issues.apache.org/jira/browse/ATLAS-4048 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 2.1.0 Reporter: Umesh Padashetty -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4044) There is no way to differentiate between complete (non-shell) and incomplete (shell) entities in UI
[ https://issues.apache.org/jira/browse/ATLAS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4044: Description: Previously, we used to show the hourglass icon for the shell entities. But this behaviour is now removed and we show the same icons for both shell and non-shell entities. One difference between these 2 on UI is we show only minimal information for shell entities, like qualifiedName and typeName. But this not very obvious, and sometimes it gets very difficult to differentiate between the two. Attached screenshots. It is important to note that api/atlas/v2/entity/guid/ does return "isIncomplete": true. So, it would be great if we can show isIncomplete parameter on the UI, which would help the user in differentiation. was: Previously, we used to show the hourglass icon for the shell entities. But this behaviour is no removed and we show the same icons for both shell and non-shell entities. One difference between these 2 on UI is we show only minimal information for shell entities, like qualifiedName and typeName. But this not very obvious, and sometimes it gets very difficult to differentiate between the two. Attached screenshots. It is important to note that api/atlas/v2/entity/guid/ does return "isIncomplete": true. So, it would be great if we can show isIncomplete parameter on the UI, which would help the user in differentiation. > There is no way to differentiate between complete (non-shell) and incomplete > (shell) entities in UI > --- > > Key: ATLAS-4044 > URL: https://issues.apache.org/jira/browse/ATLAS-4044 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Attachments: non-shell entity.png, shell entity.png, > shell_entity_guid.png > > > Previously, we used to show the hourglass icon for the shell entities. But > this behaviour is now removed and we show the same icons for both shell and > non-shell entities. > One difference between these 2 on UI is we show only minimal information for > shell entities, like qualifiedName and typeName. But this not very obvious, > and sometimes it gets very difficult to differentiate between the two. > Attached screenshots. > It is important to note that api/atlas/v2/entity/guid/ > does return "isIncomplete": true. > So, it would be great if we can show isIncomplete parameter on the UI, which > would help the user in differentiation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4043) Atlas import-kafka.sh does not import "__consumer_offsets" topic
[
https://issues.apache.org/jira/browse/ATLAS-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4043:
Attachment: Screenshot 2020-11-20 at 11.23.47 PM.png
> Atlas import-kafka.sh does not import "__consumer_offsets" topic
>
>
> Key: ATLAS-4043
> URL: https://issues.apache.org/jira/browse/ATLAS-4043
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-11-20 at 11.23.47 PM.png
>
>
> Even though kafka-topics.sh --list, lists the __consumer_offsets topic as
> below, this topic alone is not imported into Atlas when import-kafka.sh
> script is run
> {code:java}
> ATLAS_ENTITIES
> ATLAS_HOOK
> ATLAS_SPARK_HOOK
> __consumer_offsets
> connect-configs
> connect-offsets
> connect-status {code}
> I did not find anything unusual in atlas/application.log. This was working
> fine before, seems like a regression.
> As per official Kafka documentation, __consumer_offsets is used to store
> information about committed offsets for each topic:partition per group of
> consumers (groupID). It is compacted topic, so data will be periodically
> compressed and only latest offsets information available.
> Since __consumer_offsets has __ in the beginning, I have created a topic
> starting with __ and ran the import-kafka script. And it works fine. So that
> leaves us with having issue with __consumer_offsets alone.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4043) Atlas import-kafka.sh does not import "__consumer_offsets" topic
[
https://issues.apache.org/jira/browse/ATLAS-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4043:
Description:
Even though kafka-topics.sh --list, lists the __consumer_offsets topic as
below, this topic alone is not imported into Atlas when import-kafka.sh script
is run
{code:java}
ATLAS_ENTITIES
ATLAS_HOOK
ATLAS_SPARK_HOOK
__consumer_offsets
connect-configs
connect-offsets
connect-status {code}
I did not find anything unusual in atlas/application.log. This was working fine
before, seems like a regression.
As per official Kafka documentation, __consumer_offsets is used to store
information about committed offsets for each topic:partition per group of
consumers (groupID). It is compacted topic, so data will be periodically
compressed and only latest offsets information available.
Since __consumer_offsets has __ in the beginning, I have created a topic
starting with __ and ran the import-kafka script. And it works fine. So that
leaves us with having issue with __consumer_offsets alone.
was:
Even though kafka-topics.sh --list, lists the __consumer_offsets topic as
below, this topic alone is not imported into Atlas when import-kafka.sh script
is run
{code:java}
ATLAS_ENTITIES
ATLAS_HOOK
ATLAS_SPARK_HOOK
__consumer_offsets
connect-configs
connect-offsets
connect-status {code}
I did not find anything unusual in atlas/application.log
> Atlas import-kafka.sh does not import "__consumer_offsets" topic
>
>
> Key: ATLAS-4043
> URL: https://issues.apache.org/jira/browse/ATLAS-4043
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-11-20 at 11.23.47 PM.png
>
>
> Even though kafka-topics.sh --list, lists the __consumer_offsets topic as
> below, this topic alone is not imported into Atlas when import-kafka.sh
> script is run
> {code:java}
> ATLAS_ENTITIES
> ATLAS_HOOK
> ATLAS_SPARK_HOOK
> __consumer_offsets
> connect-configs
> connect-offsets
> connect-status {code}
> I did not find anything unusual in atlas/application.log. This was working
> fine before, seems like a regression.
> As per official Kafka documentation, __consumer_offsets is used to store
> information about committed offsets for each topic:partition per group of
> consumers (groupID). It is compacted topic, so data will be periodically
> compressed and only latest offsets information available.
> Since __consumer_offsets has __ in the beginning, I have created a topic
> starting with __ and ran the import-kafka script. And it works fine. So that
> leaves us with having issue with __consumer_offsets alone.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4045) Typos and other grammatical mistakes in Atlas Export/Import API Documentation
[ https://issues.apache.org/jira/browse/ATLAS-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236242#comment-17236242 ] Umesh Padashetty commented on ATLAS-4045: - Review Board Request: https://reviews.apache.org/r/73031/ > Typos and other grammatical mistakes in Atlas Export/Import API Documentation > - > > Key: ATLAS-4045 > URL: https://issues.apache.org/jira/browse/ATLAS-4045 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4045.patch > > > There are multiple typos and grammatical mistakes in > [https://atlas.apache.org/index.html#/ImportAPI] and > [https://atlas.apache.org/index.html#/ExportAPI] and other pages related to > it. > This Jira is to fix these documentation issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4045) Typos and other grammatical mistakes in Atlas Export/Import API Documentation
[ https://issues.apache.org/jira/browse/ATLAS-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty updated ATLAS-4045: Attachment: ATLAS-4045.patch > Typos and other grammatical mistakes in Atlas Export/Import API Documentation > - > > Key: ATLAS-4045 > URL: https://issues.apache.org/jira/browse/ATLAS-4045 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4045.patch > > > There are multiple typos and grammatical mistakes in > [https://atlas.apache.org/index.html#/ImportAPI] and > [https://atlas.apache.org/index.html#/ExportAPI] and other pages related to > it. > This Jira is to fix these documentation issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4045) Typos and other grammatical mistakes in Atlas Export/Import API Documentation
[ https://issues.apache.org/jira/browse/ATLAS-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Padashetty reassigned ATLAS-4045: --- Assignee: Umesh Padashetty > Typos and other grammatical mistakes in Atlas Export/Import API Documentation > - > > Key: ATLAS-4045 > URL: https://issues.apache.org/jira/browse/ATLAS-4045 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Minor > > There are multiple typos and grammatical mistakes in > [https://atlas.apache.org/index.html#/ImportAPI] and > [https://atlas.apache.org/index.html#/ExportAPI] and other pages related to > it. > This Jira is to fix these documentation issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4045) Typos and other grammatical mistakes in Atlas Export/Import API Documentation
Umesh Padashetty created ATLAS-4045: --- Summary: Typos and other grammatical mistakes in Atlas Export/Import API Documentation Key: ATLAS-4045 URL: https://issues.apache.org/jira/browse/ATLAS-4045 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 2.1.0 Reporter: Umesh Padashetty There are multiple typos and grammatical mistakes in [https://atlas.apache.org/index.html#/ImportAPI] and [https://atlas.apache.org/index.html#/ExportAPI] and other pages related to it. This Jira is to fix these documentation issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4044) There is no way to differentiate between complete (non-shell) and incomplete (shell) entities in UI
Umesh Padashetty created ATLAS-4044: --- Summary: There is no way to differentiate between complete (non-shell) and incomplete (shell) entities in UI Key: ATLAS-4044 URL: https://issues.apache.org/jira/browse/ATLAS-4044 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 2.1.0 Reporter: Umesh Padashetty Attachments: non-shell entity.png, shell entity.png, shell_entity_guid.png Previously, we used to show the hourglass icon for the shell entities. But this behaviour is no removed and we show the same icons for both shell and non-shell entities. One difference between these 2 on UI is we show only minimal information for shell entities, like qualifiedName and typeName. But this not very obvious, and sometimes it gets very difficult to differentiate between the two. Attached screenshots. It is important to note that api/atlas/v2/entity/guid/ does return "isIncomplete": true. So, it would be great if we can show isIncomplete parameter on the UI, which would help the user in differentiation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4043) Atlas import-kafka.sh does not import "__consumer_offsets" topic
Umesh Padashetty created ATLAS-4043:
---
Summary: Atlas import-kafka.sh does not import
"__consumer_offsets" topic
Key: ATLAS-4043
URL: https://issues.apache.org/jira/browse/ATLAS-4043
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.1.0
Reporter: Umesh Padashetty
Even though kafka-topics.sh --list, lists the __consumer_offsets topic as
below, this topic alone is not imported into Atlas when import-kafka.sh script
is run
{code:java}
ATLAS_ENTITIES
ATLAS_HOOK
ATLAS_SPARK_HOOK
__consumer_offsets
connect-configs
connect-offsets
connect-status {code}
I did not find anything unusual in atlas/application.log
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4025) [Export/Import] Removing a classification from the entity in source cluster does not remove the classification in target cluster
Umesh Padashetty created ATLAS-4025: --- Summary: [Export/Import] Removing a classification from the entity in source cluster does not remove the classification in target cluster Key: ATLAS-4025 URL: https://issues.apache.org/jira/browse/ATLAS-4025 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 2.1.0 Reporter: Umesh Padashetty Steps to reproduce: # Created a table src_test8_t1 in the source cluster # Assigned the classification "test_classification" to the src_test8_t1 hive_table entity in source cluster # Ran Atlas export in source, followed by import in target cluster # Entity src_test8_t1 was created in target cluster with classification "test_classification" assigned to it correctly # Now, I removed the classification "test_classification" from the entity src_test8_t1 in source cluster # Ran Atlas export in source, followed by import in target cluster # Now, the expectation is the classification "test_classification" is removed in the target cluster from the entity src_test8_t1. But it is not, classification is still assigned to the entity -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4024) Atlas terms are not imported to target cluster using Atlas export/import API
Umesh Padashetty created ATLAS-4024:
---
Summary: Atlas terms are not imported to target cluster using
Atlas export/import API
Key: ATLAS-4024
URL: https://issues.apache.org/jira/browse/ATLAS-4024
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.1.0
Reporter: Umesh Padashetty
Attachments: destination.png, source.png
Created a table with name "src_test5_t1" and assigned "test term" to it.Created
a table with name "src_test5_t1" and assigned "test term" to it.
Atlas export API was then run with below payload:
{code:java}
{ "itemsToExport": [{ "typeName": "hive_db", "uniqueAttributes": {
"qualifiedName": "src_test5@cm" } }], "options": { "replicatedTo": "cm",
"fetchType": "incremental", "skipLineage": true, "changeMarker": 0 },
"fetchTypeOptionValue": "incremental", "skipLineageOptionValue": true,
"changeTokenFromOptions": 0} {code}
Atlas Import was run with below payload:
{code:java}
{ { options = { transformers: [{ "conditions": { "__entity": "topLevel: " },
"action": { "__entity": "ADD_CLASSIFICATION: cm_replicated" } }, { "action": {
"__entity.replicatedTo": "CLEAR:", "__entity.replicatedFrom": "CLEAR:" } }, {
"conditions": { "hive_db.clusterName": "EQUALS: cm" }, "action": {
"hive_db.clusterName": "SET: cm" } }, { "conditions": { "hive_db.name":
"EQUALS: src_test5" }, "action": { "hive_db.name": "SET: tgt_test5" } }, {
"conditions": { "hive_db.location": "STARTS_WITH_IGNORE_CASE: hdfs://host:8020"
}, "action": { "hive_db.location": "REPLACE_PREFIX: =
:hdfs://host:8020=hdfs://host:8020" } }, { "conditions": {
"hive_storagedesc.location": "STARTS_WITH_IGNORE_CASE: hdfs://host:8020" },
"action": { "hive_storagedesc.location": "REPLACE_PREFIX: =
:hdfs://host:8020=hdfs://host:8020" } }], replicatedFrom: cm, size: 1 } } {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4014) changeMarker in Atlas Export API response does not get updated
Umesh Padashetty created ATLAS-4014:
---
Summary: changeMarker in Atlas Export API response does not get
updated
Key: ATLAS-4014
URL: https://issues.apache.org/jira/browse/ATLAS-4014
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.1.0
Reporter: Umesh Padashetty
As per [https://atlas.apache.org/index.html#/IncrementalExport,] changeMarker
is used in conjunction with "fetchType": "incremental" to incrementally export
the metadata, instead of exporting everything, thereby reducing the redundancy.
As per this logic, the Atlas Export API returns a new change changeMarker after
every successful Export API call (provided there is a change in Atlas metadata).
I ran the Atlas export on a DB. And then added few tables into the DB and then
again ran the Export. Expectation was changeMarker would be updated. But it is
being observed that the changeMarker never changes and is currently always set
to 1604003211134 in the instance I am testing.
The same changeMarker is set in the atlas-export-info.json too.
The changeMarker is used by Hive Replication Manager for incremental Export.
Since atlas is always returning the same changeMarker, Hive is always passing
back the same changeMarker to atlas in the eventual export calls. This is
leading to full export, instead of incremental export as desired.
Following is the result of grep i did in atlas server logs. As you can see,
changeMarker returned is always 1604003211134.
{code:java}
[root@quasar-ggealw-4 atlas]# grep "<== export" application.log | grep
changeMarker 2020-10-30 05:48:54,451 INFO - [etp1261153343-492 -
bd3b60a4-a2b3-4f5c-96c5-166b09157828:] ~ <== export(user=hrt_qa,
from=10.101.80.202): status SUCCESS: changeMarker: 1604003211134
(ExportService:101) 2020-10-30 06:03:43,282 INFO - [etp1261153343-483 -
3114c858-8f89-4d8f-917c-2c7a3d695d2f:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 06:15:43,880 INFO -
[etp1261153343-489 -
ccb8da65-e433-44a4-a470-898843dccb17:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 06:23:10,810 INFO -
[etp1261153343-51 -
a702086a-984b-43d1-adc8-f9dd0d7950c7:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 06:26:20,227 INFO -
[etp1261153343-493 -
1423275f-b645-42bd-9095-a135707f34ba:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 06:41:47,192 INFO -
[etp1261153343-41 - 2bd5e05f-534f-4a67-b7ef-d8ccc70966ea:] ~ <==
export(user=hrt_qa, from=10.101.80.202): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 06:43:39,920 INFO -
[etp1261153343-27 - 812b6c59-24b4-4a4a-8737-008865af5384:] ~ <==
export(user=hrt_qa, from=10.101.80.202): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 07:16:19,144 INFO -
[etp1261153343-554 -
e4678848-12b3-4bae-b339-b3766ec5bb9a:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 07:17:55,540 INFO -
[etp1261153343-52 -
95551e0b-98f7-4366-8806-0452d7a49c4c:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 09:49:22,376 INFO -
[etp1261153343-740 -
f94e92cc-4d80-4d61-b19b-c6956b30b987:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 10:11:31,160 INFO -
[etp1261153343-52 -
5e8152c8-d210-4688-914a-06f983fb3898:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 10:24:53,328 INFO -
[etp1261153343-547 -
2cdc6326-4786-4a69-a116-f15c476dc6a0:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) 2020-10-30 11:20:49,768 INFO -
[etp1261153343-27 -
1c88be93-17e8-4530-a46d-8c28f8bcc4b7:hive:POST/api/atlas/admin/export] ~ <==
export(user=hive, from=172.27.160.133): status SUCCESS: changeMarker:
1604003211134 (ExportService:101) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4006) Support for Business Metadata in Atlas Export API
Umesh Padashetty created ATLAS-4006: --- Summary: Support for Business Metadata in Atlas Export API Key: ATLAS-4006 URL: https://issues.apache.org/jira/browse/ATLAS-4006 Project: Atlas Issue Type: Bug Affects Versions: 2.1.0 Reporter: Umesh Padashetty Business metadata definition and Entity's Business metadata details are not exported currently via Atlas Export API, we need to build support for this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4007) Support for Business Metadata in Atlas Import API
Umesh Padashetty created ATLAS-4007: --- Summary: Support for Business Metadata in Atlas Import API Key: ATLAS-4007 URL: https://issues.apache.org/jira/browse/ATLAS-4007 Project: Atlas Issue Type: Bug Affects Versions: 2.1.0 Reporter: Umesh Padashetty Business metadata definition and Entity's Business metadata details are not imported currently via Atlas Import API, we need to build support for this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3926) Atlas1.2 with Kerberos problem
[ https://issues.apache.org/jira/browse/ATLAS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17185023#comment-17185023 ] Umesh Padashetty commented on ATLAS-3926: - [~yuyu_1998] it is complaining of missing credentials. You have to first kinit before you run the import script in case of secure kerberised clusters. The same has been mentioned by [~nixon] above. In the screenshots you attached, none of them has the kinit details. You can check the kerberos credentials by running the klist command You can read about kinit and klist more at [https://web.mit.edu/kerberos/krb5-1.12/doc/user/user_commands/kinit.html] and [https://web.mit.edu/kerberos/krb5-1.12/doc/user/user_commands/klist.html] > Atlas1.2 with Kerberos problem > -- > > Key: ATLAS-3926 > URL: https://issues.apache.org/jira/browse/ATLAS-3926 > Project: Atlas > Issue Type: Bug > Components: falcon-integration, hive-integration >Affects Versions: 1.2.0 >Reporter: yuyu >Priority: Major > Fix For: 1.2.0 > > Attachments: image-2020-08-25-16-29-12-906.png, > image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, > image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, > image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, > image-2020-08-25-16-38-45-645.png > > > Hello, everyone. Recently, I encountered a problem with Kerberos when > deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH > version 5.16 and Kerberos service deployed.My installation method is Atlas > 1.2 integrated CDH HBase and external 5.5.1 Solr > When I start the atlas service, I can successfully access the atlas web page > through my computer： > !image-2020-08-25-16-29-29-667.png! > But when I tried to import hive metadata information, something went wrong，as > shown in the figure below: > !image-2020-08-25-16-30-34-221.png! > !image-2020-08-25-16-38-45-645.png! > !image-2020-08-25-16-31-28-330.png! > It seems to indicate that I don't have a valid Kerberos principal? > Here is part of my atlas configuration file atlas-application.properties： > !image-2020-08-25-16-34-41-642.png! > !image-2020-08-25-16-35-09-836.png! > Can anyone tell me what the problem is,thanks. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3840) Atlas website's html meta description is set to "My awesome app using docz"
[
https://issues.apache.org/jira/browse/ATLAS-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-3840:
Attachment: ATLAS-3840-1.patch
> Atlas website's html meta description is set to "My awesome app using docz"
> ---
>
> Key: ATLAS-3840
> URL: https://issues.apache.org/jira/browse/ATLAS-3840
> Project: Atlas
> Issue Type: Bug
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Major
> Attachments: ATLAS-3840-1.patch, ATLAS-3840.patch, Screenshot
> 2020-06-04 at 3.11.48 PM.png, Screenshot 2020-06-12 at 9.36.43 PM.png
>
>
> As seen at [view-source:https://atlas.apache.org/#/] meta tag is set to
> {code:java}
> {code}
> !Screenshot 2020-06-12 at 9.36.43 PM.png|width=1390,height=122!
> When Atlas website link is posted in apps which support thumbnail view (like
> Slack, WhatsApp etc), the thumbnail view shows "My awesome app using docz"
> !Screenshot 2020-06-04 at 3.11.48 PM.png|width=596,height=194!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3840) Atlas website's html meta description is set to "My awesome app using docz"
[
https://issues.apache.org/jira/browse/ATLAS-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134356#comment-17134356
]
Umesh Padashetty commented on ATLAS-3840:
-
Review board request: [https://reviews.apache.org/r/72590/]
> Atlas website's html meta description is set to "My awesome app using docz"
> ---
>
> Key: ATLAS-3840
> URL: https://issues.apache.org/jira/browse/ATLAS-3840
> Project: Atlas
> Issue Type: Bug
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Major
> Attachments: ATLAS-3840.patch, Screenshot 2020-06-04 at 3.11.48
> PM.png, Screenshot 2020-06-12 at 9.36.43 PM.png
>
>
> As seen at [view-source:https://atlas.apache.org/#/] meta tag is set to
> {code:java}
> {code}
> !Screenshot 2020-06-12 at 9.36.43 PM.png|width=1390,height=122!
> When Atlas website link is posted in apps which support thumbnail view (like
> Slack, WhatsApp etc), the thumbnail view shows "My awesome app using docz"
> !Screenshot 2020-06-04 at 3.11.48 PM.png|width=596,height=194!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-3840) Atlas website's html meta description is set to "My awesome app using docz"
[
https://issues.apache.org/jira/browse/ATLAS-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty reassigned ATLAS-3840:
---
Attachment: ATLAS-3840.patch
Assignee: Umesh Padashetty
> Atlas website's html meta description is set to "My awesome app using docz"
> ---
>
> Key: ATLAS-3840
> URL: https://issues.apache.org/jira/browse/ATLAS-3840
> Project: Atlas
> Issue Type: Bug
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Major
> Attachments: ATLAS-3840.patch, Screenshot 2020-06-04 at 3.11.48
> PM.png, Screenshot 2020-06-12 at 9.36.43 PM.png
>
>
> As seen at [view-source:https://atlas.apache.org/#/] meta tag is set to
> {code:java}
> {code}
> !Screenshot 2020-06-12 at 9.36.43 PM.png|width=1390,height=122!
> When Atlas website link is posted in apps which support thumbnail view (like
> Slack, WhatsApp etc), the thumbnail view shows "My awesome app using docz"
> !Screenshot 2020-06-04 at 3.11.48 PM.png|width=596,height=194!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3840) Atlas website's html meta description is set to "My awesome app using docz"
Umesh Padashetty created ATLAS-3840:
---
Summary: Atlas website's html meta description is set to "My
awesome app using docz"
Key: ATLAS-3840
URL: https://issues.apache.org/jira/browse/ATLAS-3840
Project: Atlas
Issue Type: Bug
Reporter: Umesh Padashetty
Attachments: Screenshot 2020-06-04 at 3.11.48 PM.png, Screenshot
2020-06-12 at 9.36.43 PM.png
As seen at [view-source:https://atlas.apache.org/#/] meta tag is set to
{code:java}
{code}
!Screenshot 2020-06-12 at 9.36.43 PM.png|width=1390,height=122!
When Atlas website link is posted in apps which support thumbnail view (like
Slack, WhatsApp etc), the thumbnail view shows "My awesome app using docz"
!Screenshot 2020-06-04 at 3.11.48 PM.png|width=596,height=194!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3813) Import-.sh script shows wrong message of Import success even when there are no database/table/topic are imported in the System
[ https://issues.apache.org/jira/browse/ATLAS-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123107#comment-17123107 ] Umesh Padashetty commented on ATLAS-3813: - Kafka file import was built this way and isan expected behavior. Following is the test case I had written while testing Kafka import. Do we now plan to change this behavior? Test Scenario: * Verify that when an invalid topic name is saved in the file and when this file path is passed as a param to import script with -f option, then there should not be any error when the script is run Expected Result: * The topics which are valid should be read and added (if new) updated (if pre existing). Rest topics should be ignored > Import-.sh script shows wrong message of Import success even when > there are no database/table/topic are imported in the System > -- > > Key: ATLAS-3813 > URL: https://issues.apache.org/jira/browse/ATLAS-3813 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > While importing Hive-data from the file, if file has db names and table names > which are not in the Hive. Application still shows message as "Hive Meta Data > imported successfully!!!" > While importing Kafka-Topic data from the file, if file has Topic names > which are not present in Kafka. Application still shows message as "Kafka > Data Model imported successfully!!!" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3745) [Business Metadata] Newly added BM definitions in admin/BM page are not immediately listed. Refresh is needed to load the new BM definitions.
Umesh Padashetty created ATLAS-3745: --- Summary: [Business Metadata] Newly added BM definitions in admin/BM page are not immediately listed. Refresh is needed to load the new BM definitions. Key: ATLAS-3745 URL: https://issues.apache.org/jira/browse/ATLAS-3745 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 7.26.22 PM.png, Screenshot 2020-04-20 at 7.26.44 PM.png This was working fine before, seems to be a regression. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3744) [Beta UI] Long entity type filter load time
Umesh Padashetty created ATLAS-3744: --- Summary: [Beta UI] Long entity type filter load time Key: ATLAS-3744 URL: https://issues.apache.org/jira/browse/ATLAS-3744 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 12.57.05 PM.png, Screenshot 2020-04-20 at 12.57.16 PM.png Sometimes, we are taking around 15-20 seconds to load the entity type filters in the new Beta UI when the user clicks on Filters drop down. Once the user clicks on Filters, the UI just freezes there, while the content is loaded in the background. This gives a feeling to the end-user that nothing is happening and the UI is stuck, while in reality it isnt. This is pretty confusing. I think it is a good idea to introduce a loading icon while the data is being loaded in the backend. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes
Umesh Padashetty created ATLAS-3743: --- Summary: [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes Key: ATLAS-3743 URL: https://issues.apache.org/jira/browse/ATLAS-3743 Project: Atlas Issue Type: Bug Components: atlas-core, atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 8.53.54 PM.png, Screenshot 2020-04-20 at 8.54.12 PM.png Following are the issues observed: # All the BM related operations on an entity are listed as BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up for all the operations. ## When a BM attribute is added for the first time, ideally BUSINESS_ATTRIBUTE_ADD action should show up. ## On the same lines, when all the BM attributes are removed from entity, BUSINESS_ATTRIBUTE_DELETE should show up. # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of plain text like "Business Attribute(s) Updated" # Date type value is shown as timestamp instead of date, in audit/technical properties. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
