[jira] [Updated] (ATLAS-4072) spark_column_lineage missing for insert into select * queries run via spark-shell

2020-12-10 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-10 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-10 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-10 Thread Umesh Padashetty (Jira)
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

2020-12-09 Thread Umesh Padashetty (Jira)


[ 
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

2020-12-09 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-09 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-09 Thread Umesh Padashetty (Jira)
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

2020-12-09 Thread Umesh Padashetty (Jira)
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'

2020-12-08 Thread Umesh Padashetty (Jira)


 [ 
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'

2020-12-08 Thread Umesh Padashetty (Jira)
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'

2020-12-08 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-08 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-08 Thread Umesh Padashetty (Jira)


 [ 
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

2020-12-08 Thread Umesh Padashetty (Jira)
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

2020-11-24 Thread Umesh Padashetty (Jira)
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

2020-11-24 Thread Umesh Padashetty (Jira)
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

2020-11-23 Thread Umesh Padashetty (Jira)


 [ 
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

2020-11-20 Thread Umesh Padashetty (Jira)


 [ 
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

2020-11-20 Thread Umesh Padashetty (Jira)


 [ 
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

2020-11-20 Thread Umesh Padashetty (Jira)


[ 
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

2020-11-20 Thread Umesh Padashetty (Jira)


 [ 
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

2020-11-20 Thread Umesh Padashetty (Jira)


 [ 
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

2020-11-20 Thread Umesh Padashetty (Jira)
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

2020-11-20 Thread Umesh Padashetty (Jira)
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

2020-11-20 Thread Umesh Padashetty (Jira)
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

2020-11-12 Thread Umesh Padashetty (Jira)
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

2020-11-12 Thread Umesh Padashetty (Jira)
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

2020-11-03 Thread Umesh Padashetty (Jira)
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

2020-10-24 Thread Umesh Padashetty (Jira)
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

2020-10-24 Thread Umesh Padashetty (Jira)
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

2020-08-26 Thread Umesh Padashetty (Jira)


[ 
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"

2020-06-17 Thread Umesh Padashetty (Jira)


 [ 
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"

2020-06-12 Thread Umesh Padashetty (Jira)


[ 
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"

2020-06-12 Thread Umesh Padashetty (Jira)


 [ 
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"

2020-06-12 Thread Umesh Padashetty (Jira)
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

2020-06-01 Thread Umesh Padashetty (Jira)


[ 
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.

2020-04-20 Thread Umesh Padashetty (Jira)
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

2020-04-20 Thread Umesh Padashetty (Jira)
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

2020-04-20 Thread Umesh Padashetty (Jira)
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)


[jira] [Created] (ATLAS-3742) [Business Metadata] Quick Search/Suggestions does not work with Business metadata attributes, apart from string types

2020-04-20 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3742:
---

 Summary: [Business Metadata] Quick Search/Suggestions does not 
work with Business metadata attributes, apart from string types
 Key: ATLAS-3742
 URL: https://issues.apache.org/jira/browse/ATLAS-3742
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-04-20 at 7.34.22 PM.png, Screenshot 
2020-04-20 at 7.38.33 PM.png, Screenshot 2020-04-20 at 7.38.38 PM.png

Business metadata attributes can be defined to be of the following types. 
 * string
 * boolean
 * byte
 * short
 * int
 * float
 * double
 * long
 * date
 * enum

Quick search and suggestions works fine only if the business metadata attribute 
is defined to be of string type. It is not working for any of the other (listed 
above) BM attribute types we support.

Attached screenshots.

Also, we support quick search/suggestions on BM Attributes values. So in case 
of data types like enum, byte, boolean, date etc. how would the user search? 
For instance, how would the user enter a valid date? what is the valid date 
format? And for cases like boolean, entering a search text like "true" returns 
me 100s of returns which are of not much use. Should we support quick search 
and suggestions on BM attribute names instead of values?



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


[jira] [Created] (ATLAS-3741) [Business Metadata] Quick Search/Suggestions does not work with multi valued Business metadata attribute

2020-04-20 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3741:
---

 Summary: [Business Metadata] Quick Search/Suggestions does not 
work with multi valued Business metadata attribute
 Key: ATLAS-3741
 URL: https://issues.apache.org/jira/browse/ATLAS-3741
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-04-20 at 7.12.02 PM.png, Screenshot 
2020-04-20 at 7.12.46 PM.png

Business metadata attibutes can defined to have multi values. When an attribute 
which has multi value enabled is added to the entity, the BM attribute assigned 
entity and the BM attribute value do not apear in neither quick search, nor 
suggestions.  

This could be similar to https://issues.apache.org/jira/browse/ATLAS-3682

Attached screenshots.



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


[jira] [Created] (ATLAS-3740) [Business Metadata] Suggestions doesn't work correctly with case sensitive Business Metadata attribute values

2020-04-20 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3740:
---

 Summary: [Business Metadata] Suggestions doesn't work correctly 
with case sensitive Business Metadata attribute values 
 Key: ATLAS-3740
 URL: https://issues.apache.org/jira/browse/ATLAS-3740
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-04-20 at 5.23.16 PM.png, Screenshot 
2020-04-20 at 5.23.25 PM.png, Screenshot 2020-04-20 at 5.23.34 PM.png, 
Screenshot 2020-04-20 at 5.23.43 PM.png

Entity Details > Business Metadata attributes supports addition of values with 
case sensitivity. These can be viewed once updated, and later can be edited 
without any issues. 

But the problem is, while searching on these attribute values via quick 
search/suggestions bar, suggestions are being listed only if the user enters 
these BM attribute values in lower case. If the user enter the case sensitive 
values as entered in the BM attribute values, there are no suggestions being 
listed.

This works fine with Quick search though. Attached screenshots.  



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


[jira] [Created] (ATLAS-3739) [Business Metadata] Suggestions lists Business Metadata attribute values which were previously added and deleted

2020-04-20 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3739:
---

 Summary: [Business Metadata] Suggestions lists Business Metadata 
attribute values which were previously added and deleted
 Key: ATLAS-3739
 URL: https://issues.apache.org/jira/browse/ATLAS-3739
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-04-20 at 4.09.35 PM.png, Screenshot 
2020-04-20 at 4.09.39 PM.png

Since Suggestions work on BM attribute's value. I added few BM attributes to 
entities (for instance test1a1value, test2a1value, test3a1value) and then later 
deleted them. But when I search with "test" in the search box, I still see 
suggestions for test1a1value, test2a1value, test3a1value. 

Also, when I do click on these suggestions, as expected, it returns empty 
results. Since there are no entities tagged with this BM attribute value. 

Quick search works fine though. Attached screenshots.



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


[jira] [Created] (ATLAS-3738) [Business Metadata] Suggestions does not honour Business Metadata Attribute's Search Weight value

2020-04-20 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3738:
---

 Summary: [Business Metadata] Suggestions does not honour Business 
Metadata Attribute's Search Weight value
 Key: ATLAS-3738
 URL: https://issues.apache.org/jira/browse/ATLAS-3738
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-04-20 at 4.02.28 PM.png, Screenshot 
2020-04-20 at 4.02.36 PM.png

In the new Business Metadata UI, the user can provide the search weight for 
each attribute. This search weight is used in quick search and suggestions API, 
to list the values based on their search weight. An attribute with a search 
weight 10 appears before the attribute with a search weight of 9, when they 
have the same attribute values. 

Defined BM attributes, with search weight in the following order 
 * Test2A1 = Test2A3 > Test1A1 > Test3A1 > Test4A1

where Test1, Test2... are the Business Metadatas.

Added these BM attributes to the entities with values +value for 
better clarity. 

As per the functionality, suggestions should be listed in below order when I 
enter "test"
 * test2a1value
 * test2a3value
 * test1a1value
 * test3a1value
 * test4a1value

but they are listed as 
 * test2a1value
 * test3a1value
 * test1a1value
 * test4a1value
 * test2a3value

Quick search, on the other hand, works fine. Also, the following logs were 
observed in atlas/application.log when I enter a search pattern in quick 
search/suggestion box.
{code:java}
2020-04-20 10:39:15,969 WARN  - [etp851765426-201 - 
56181e81-11e6-4e02-a23a-d72940f3703c:] ~ Could not convert given VERTEX index 
query: [test1a1value] (IndexSerializer:626)
2020-04-20 10:39:15,978 WARN  - [etp851765426-201 - 
56181e81-11e6-4e02-a23a-d72940f3703c:] ~ Could not convert given VERTEX index 
query: [test1a1value] (IndexSerializer:626)
2020-04-20 10:39:24,733 WARN  - [etp851765426-160 - 
d0030733-2fb9-4dfc-8659-7a3c62415ee0:] ~ Could not convert given VERTEX index 
query: [test1a1value*] (IndexSerializer:626)
2020-04-20 10:39:24,784 WARN  - [etp851765426-160 - 
d0030733-2fb9-4dfc-8659-7a3c62415ee0:] ~ Could not convert given VERTEX index 
query: [test1a1value*] (IndexSerializer:626)
2020-04-20 10:39:26,831 WARN  - [etp851765426-201 - 
7d11aa19-e517-4157-a86c-9ce25a19c1ab:] ~ Could not convert given VERTEX index 
query: [te*] (IndexSerializer:626)
2020-04-20 10:39:26,861 WARN  - [etp851765426-201 - 
7d11aa19-e517-4157-a86c-9ce25a19c1ab:] ~ Could not convert given VERTEX index 
query: [te*] (IndexSerializer:626)
2020-04-20 10:39:27,342 WARN  - [etp851765426-160 - 
66c8be42-f375-4707-bc51-5f0c592828dc:] ~ Could not convert given VERTEX index 
query: [test*] (IndexSerializer:626) {code}
Attached screenshots.



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


[jira] [Assigned] (ATLAS-3717) [Business Metadata] businessmetadata is misplelled as businessmetata in entity rest calls

2020-04-02 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty reassigned ATLAS-3717:
---

Attachment: ATLAS-3717.patch
  Assignee: Umesh Padashetty

Review board request: [https://reviews.apache.org/r/72308/]

> [Business Metadata] businessmetadata is misplelled as businessmetata in 
> entity rest calls
> -
>
> Key: ATLAS-3717
> URL: https://issues.apache.org/jira/browse/ATLAS-3717
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Blocker
> Attachments: ATLAS-3717.patch, Screenshot 2020-04-01 at 4.55.42 PM.png
>
>
> The business metadata entity rest apis have misspelled businessmetadata as 
> businessmetata. Since these are new APIs introduced recently, it is rather a 
> good idea to fix this typo before these APIs start getting noticed.
> Needs change in
> @POST
> @Path("/guid/\{guid}/businessmetata")
> @DELETE
> @Path("/guid/\{guid}/businessmetata")
> @POST
> @Path("/guid/\{guid}/businessmetata/\{bmName}")
> @DELETE
> @Path("/guid/\{guid}/businessmetata/\{bmName}")



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


[jira] [Updated] (ATLAS-3716) Display queryText instead of process_execution name in process > processExecutions listing

2020-04-02 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3716:

Attachment: hive_process_properties.json

> Display queryText instead of process_execution name in process > 
> processExecutions listing
> --
>
> Key: ATLAS-3716
> URL: https://issues.apache.org/jira/browse/ATLAS-3716
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-04-02 at 7.36.50 PM.png, Screenshot 
> 2020-04-02 at 7.37.05 PM.png, Screenshot 2020-04-02 at 7.49.20 PM.png, 
> hive_process_properties.json
>
>
> Recently, with https://issues.apache.org/jira/browse/ATLAS-3621, we made a 
> change where we stopped populating the process_name/process_execution name 
> with the query string. Instead these query strings are populated in the 
> queryText field alone.
> With this change, the process_executions listed for a particular process do 
> not make sense anymore. For instance, I ran the below queries
>  * insert into t3 select * from t2 where name="umesh";
>  * insert into t3 select * from t2;
>  * insert into t3 select * from t2 where name="umesh";
> This creates multiple process_executions under the sam process. But in the 
> UI, it is listed as below
>   * 
> QUERY:default.t2@cm:1585835224000->:INSERT:default.t3@cm:1585835274000:1585835636968:1585835638832
>  * 
> QUERY:default.t2@cm:1585835224000->:INSERT:default.t3@cm:1585835274000:1585835568869:1585835579187
>  * 
> QUERY:default.t2@cm:1585835224000->:INSERT:default.t3@cm:1585835274000:1585835618877:1585835623532
> Which does not provide any info. Instead of displaying the process execution 
> name, we can show the queryText in these cases. This way the user will 
> uniquely know the list of queries run.
> Attached screenshots. 



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


[jira] [Created] (ATLAS-3717) [Business Metadata] businessmetadata is misplelled as businessmetata in entity rest calls

2020-04-02 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3717:
---

 Summary: [Business Metadata] businessmetadata is misplelled as 
businessmetata in entity rest calls
 Key: ATLAS-3717
 URL: https://issues.apache.org/jira/browse/ATLAS-3717
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-04-01 at 4.55.42 PM.png

The business metadata entity rest apis have misspelled businessmetadata as 
businessmetata. Since these are new APIs introduced recently, it is rather a 
good idea to fix this typo before these APIs start getting noticed.

Needs change in

@POST
@Path("/guid/\{guid}/businessmetata")

@DELETE
@Path("/guid/\{guid}/businessmetata")

@POST
@Path("/guid/\{guid}/businessmetata/\{bmName}")

@DELETE
@Path("/guid/\{guid}/businessmetata/\{bmName}")



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


[jira] [Created] (ATLAS-3716) Display queryText instead of process_execution name in process > processExecutions listing

2020-04-02 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3716:
---

 Summary: Display queryText instead of process_execution name in 
process > processExecutions listing
 Key: ATLAS-3716
 URL: https://issues.apache.org/jira/browse/ATLAS-3716
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-04-02 at 7.36.50 PM.png, Screenshot 
2020-04-02 at 7.37.05 PM.png, Screenshot 2020-04-02 at 7.49.20 PM.png

Recently, with https://issues.apache.org/jira/browse/ATLAS-3621, we made a 
change where we stopped populating the process_name/process_execution name with 
the query string. Instead these query strings are populated in the queryText 
field alone.

With this change, the process_executions listed for a particular process do not 
make sense anymore. For instance, I ran the below queries
 * insert into t3 select * from t2 where name="umesh";
 * insert into t3 select * from t2;
 * insert into t3 select * from t2 where name="umesh";

This creates multiple process_executions under the sam process. But in the UI, 
it is listed as below
  * 
QUERY:default.t2@cm:1585835224000->:INSERT:default.t3@cm:1585835274000:1585835636968:1585835638832
 * 
QUERY:default.t2@cm:1585835224000->:INSERT:default.t3@cm:1585835274000:1585835568869:1585835579187
 * 
QUERY:default.t2@cm:1585835224000->:INSERT:default.t3@cm:1585835274000:1585835618877:1585835623532

Which does not provide any info. Instead of displaying the process execution 
name, we can show the queryText in these cases. This way the user will uniquely 
know the list of queries run.

Attached screenshots. 



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


[jira] [Created] (ATLAS-3710) [Business Metadata] Missing Business Metadata attribute info in list view

2020-03-31 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3710:
---

 Summary: [Business Metadata] Missing Business Metadata attribute 
info in list view
 Key: ATLAS-3710
 URL: https://issues.apache.org/jira/browse/ATLAS-3710
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty
 Fix For: 2.1.0, 3.0.0
 Attachments: Screenshot 2020-03-31 at 7.28.48 PM.png, Screenshot 
2020-03-31 at 7.29.39 PM.png

Currently only Attribute Name, Type and Applicable Type(s) are listed in the 
UI. Need to list Search Weight, Enable Multi values and Max length too. 

Currently, the only way to know these attributes is to click on edit. Tedious 
when the user wants to track multiple attributes.

Screenshots attached.



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


[jira] [Created] (ATLAS-3709) [Business Metadata] Issues with quick search/suggestions in conjunction with Business Metadata attributes

2020-03-31 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3709:
---

 Summary: [Business Metadata] Issues with quick search/suggestions 
in conjunction with Business Metadata attributes
 Key: ATLAS-3709
 URL: https://issues.apache.org/jira/browse/ATLAS-3709
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-03-31 at 6.10.14 PM.png, Screenshot 
2020-03-31 at 6.15.51 PM.png

Quick search and suggestions has been enabled on Business metadata attriibutes 
as per ATLAS-3675. But they don't seem to work as expected.

For instance, we can define search weight for each business metadatda 
attributes. And once these attributes are assigned to entities, attribute 
values should be listed in suggestions dorp down and the entities should be 
listed in quick search results.

Issues observed:
 # Under a single Business Metadata
 ## When multiple attributes are defined and added to entities (with the same 
search weight), quick search and suggestion is working only on the first 
attribute which is added to the entity. Any attributes (with same weight) which 
are added to entity later are not listed in suggestions or quick search
 ## When multiple attributes are defined and added to entities (with the 
different search weight), quick search and suggestion is working only on the 
attributes with search weight 10. Even if we first add an attribute to an 
entity which has search weight=9
 # Under 2 different Business Metadata
 ## Quick search and suggestions stops working completely on all the previous 
attributes as soon as a new Business Metadata is defined.
 ## Once I assign this newly defined business metadata, it starts working (but 
again, only for this attribute value)

Screenshots attached.



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


[jira] [Updated] (ATLAS-3697) [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously

2020-03-26 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3697:

Attachment: Issue with editing attribute values post error.mov

> [Business Metadata] Incorrect values populated in Entity details > Business 
> Metatdata attribute values, after encountering an error previously
> --
>
> Key: ATLAS-3697
> URL: https://issues.apache.org/jira/browse/ATLAS-3697
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Priority: Critical
> Attachments: Issue with editing attribute values post error.mov
>
>
> While adding/updating a Business Metadata attribute value in the entity 
> details page, suppose a user updates multiple values, and then click on save. 
> If say, there is an error in updating some value, the user cannot obviously 
> save it. So once you click on cancel, and click on edit again, instead of 
> populating the original values, we are populating the values which the user 
> tried to update while he encountered an error.
> This could be problematic because let's say the user changes the mind and 
> wants to update only one value. Now he cannot do it, because the original 
> values are not populated. Also, the user might save wrong data unknowingly 
> while trying to fix a rogue field.
> Attached video for the detailed explanation. 



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


[jira] [Created] (ATLAS-3697) [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously

2020-03-26 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3697:
---

 Summary: [Business Metadata] Incorrect values populated in Entity 
details > Business Metatdata attribute values, after encountering an error 
previously
 Key: ATLAS-3697
 URL: https://issues.apache.org/jira/browse/ATLAS-3697
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty


While adding/updating a Business Metadata attribute value in the entity details 
page, suppose a user updates multiple values, and then click on save. If say, 
there is an error in updating some value, the user cannot obviously save it. So 
once you click on cancel, and click on edit again, instead of populating the 
original values, we are populating the values which the user tried to update 
while he encountered an error.

This could be problematic because let's say the user changes the mind and wants 
to update only one value. Now he cannot do it, because the original values are 
not populated. Also, the user might save wrong data unknowingly while trying to 
fix a rogue field.

Attached video for the detailed explanation. 



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


[jira] [Created] (ATLAS-3696) [Business Metadata] No option to check/uncheck Business Metadata field in search results

2020-03-26 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3696:
---

 Summary: [Business Metadata] No option to check/uncheck Business 
Metadata field in search results
 Key: ATLAS-3696
 URL: https://issues.apache.org/jira/browse/ATLAS-3696
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-03-26 at 9.00.55 PM.png, Screenshot 
2020-03-26 at 9.04.22 PM.png

For instance, there is no way to show "Business Metadata" column if Business 
Metadata attribute filter is not applied while searching. Attached screenshots



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


[jira] [Updated] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name

2020-03-26 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3695:

Attachment: Screenshot 2020-03-26 at 8.10.11 PM.png
Screenshot 2020-03-26 at 8.09.45 PM.png

> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 8.09.45 PM.png, Screenshot 
> 2020-03-26 at 8.10.11 PM.png
>
>
> Special characters are not being allowed in the Business Metadata Name, but 
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in 
> Attributes name. Attached screenshots. This is reproducible both from UI and 
> API. Screenshots attached.
> {code:java}
> curl -X POST \
>   'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
>   -H 'cache-control: no-cache' \
>   -H 'content-type: application/json' \
>   -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
>   -H 'x-xsrf-header: \"\"' \
>   -d 
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
>  Character 
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
>  {code}



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


[jira] [Updated] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name

2020-03-26 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3695:

Description: 
Special characters are not being allowed in the Business Metadata Name, but are 
being allowed in the Attribute Name and Description.

Having special characters in Description should be fine, but not in Attributes 
name. Attached screenshots. This is reproducible both from UI and API. 
Screenshots attached.
{code:java}
curl -X POST \
  'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
  -H 'x-xsrf-header: \"\"' \
  -d 
'{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
 Character 
Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
 {code}

  was:
Special characters are not being allowed in the Business Metadata Name, but are 
being allowed in the Attribute Name and Description.

Having special characters in Description should be fine, but not in Attributes 
name. Attached screenshots. This is reproducible both from UI and API
{code:java}
curl -X POST \
  'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
  -H 'x-xsrf-header: \"\"' \
  -d 
'{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
 Character 
Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
 {code}


> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 8.09.45 PM.png, Screenshot 
> 2020-03-26 at 8.10.11 PM.png
>
>
> Special characters are not being allowed in the Business Metadata Name, but 
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in 
> Attributes name. Attached screenshots. This is reproducible both from UI and 
> API. Screenshots attached.
> {code:java}
> curl -X POST \
>   'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
>   -H 'cache-control: no-cache' \
>   -H 'content-type: application/json' \
>   -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
>   -H 'x-xsrf-header: \"\"' \
>   -d 
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
>  Character 
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
>  {code}



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


[jira] [Created] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name

2020-03-26 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3695:
---

 Summary: [Business Metadata] Special characters are being allowed 
in Attribute Name
 Key: ATLAS-3695
 URL: https://issues.apache.org/jira/browse/ATLAS-3695
 Project: Atlas
  Issue Type: Bug
Reporter: Umesh Padashetty


Special characters are not being allowed in the Business Metadata Name, but are 
being allowed in the Attribute Name and Description.

Having special characters in Description should be fine, but not in Attributes 
name. Attached screenshots. This is reproducible both from UI and API
{code:java}
curl -X POST \
  'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
  -H 'x-xsrf-header: \"\"' \
  -d 
'{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
 Character 
Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
 {code}



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


[jira] [Updated] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name

2020-03-26 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3695:

Component/s: atlas-webui
  atlas-core

> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Priority: Major
>
> Special characters are not being allowed in the Business Metadata Name, but 
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in 
> Attributes name. Attached screenshots. This is reproducible both from UI and 
> API
> {code:java}
> curl -X POST \
>   'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
>   -H 'cache-control: no-cache' \
>   -H 'content-type: application/json' \
>   -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
>   -H 'x-xsrf-header: \"\"' \
>   -d 
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
>  Character 
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
>  {code}



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


[jira] [Created] (ATLAS-3694) [Business Metadata] Max length defined for attributes of string type is not getting enforced

2020-03-26 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3694:
---

 Summary: [Business Metadata] Max length defined for attributes of 
string type is not getting enforced
 Key: ATLAS-3694
 URL: https://issues.apache.org/jira/browse/ATLAS-3694
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core, atlas-webui
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-03-26 at 7.49.51 PM.png, Screenshot 
2020-03-26 at 7.51.13 PM.png

Even when the max length applicable to an attribute is defined as 10, I was 
able to add all the alphabets of an english language i.e. a-z, 26 in length, as 
the attribute value.

This is reproducible both from API as well as UI.
{code:java}
curl -X POST \
  
'https://:31443/api/atlas/v2/entity/guid/ab29815d-6d20-44ee-b426-8fba946b72a5/businessmetata?isOverwrite=true'
 \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'postman-token: 6c5a0476-ac64-57c9-5845-cbea945fdf99' \
  -H 'x-xsrf-header: \"\"' \
  -d '{"String Length":{"Name":"abcdefghijklmnopqrstuvwxyz"}}' {code}
Screenshots attached.



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


[jira] [Created] (ATLAS-3693) [Business Metadata] Unable to add negative values in multi-valued attributes for byte, short, int, long, float, double

2020-03-26 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3693:
---

 Summary: [Business Metadata] Unable to add negative values in 
multi-valued attributes for byte, short, int, long, float, double 
 Key: ATLAS-3693
 URL: https://issues.apache.org/jira/browse/ATLAS-3693
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty


byte, short, int, long, float, double data types can have values ranging from - 
to +, but when the attribute is defined as multi valued, unable to add negative 
values for these attributes. Entering a - sign, does nothing. The same works 
fine if the attribute is defined to be non multi-valued.

Also, this works fine via the REST API.
{code:java}
curl -X POST \ 
'https://:31443/api/atlas/v2/entity/guid/ab29815d-6d20-44ee-b426-8fba946b72a5/businessmetata?isOverwrite=true'
 \ -H 'cache-control: no-cache' \ -H 'content-type: application/json' \ -H 
'postman-token: 43107e84-a29c-b1b9-b628-4e0cf4645158' \ -H 'x-xsrf-header: 
\"\"' \ -d '{"Test Multi":{"int":["1221","121222", 
"-99162"]},"Test":{"long":"922337203685477"}}'  {code}



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


[jira] [Created] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored

2020-03-26 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3692:
---

 Summary: [Business Metadata] Incorrect values for long data type 
being stored 
 Key: ATLAS-3692
 URL: https://issues.apache.org/jira/browse/ATLAS-3692
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty
 Attachments: long issue.mov

While assigning very long values to the business metadata attribute, the values 
are being stored incorrectly. For instance, the range of long data type in java 
is +9223372036854775807 to -9223372036854775808. But the following issues are 
being observed 
 # When you give the value as +9223372036854775807 it is being stored as 
+9223372036854776000
 # When you give the value as -9223372036854775808 it is being stored as 
-9223372036854776000
 # Once the value gets stored as 9223372036854776000, any further save on the 
attribute values keeps throwing out of range exception. This is weird, because 
the value is still saved as 9223372036854776000, but UI keeps complaining

Attached is the video



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


[jira] [Created] (ATLAS-3691) [Business Metadata] Date field does not have year and month selector

2020-03-26 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3691:
---

 Summary: [Business Metadata] Date field does not have year and 
month selector
 Key: ATLAS-3691
 URL: https://issues.apache.org/jira/browse/ATLAS-3691
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty


While assigining the business metadata attribute in the entity details page, 
the date selector does not have an option to change the year. We can just 
change the monthwise.

Imagine the case where I went to set the date to some distant date, either in 
past (say Jan 20, 1989) or future (say Feb 26, 2036), the user will have to 
click hundreds of times to reach this date. It is better to provide an year 
selection option



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


[jira] [Created] (ATLAS-3683) Entity details > Business Metadata, multi-valued attribute spacing issue

2020-03-24 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3683:
---

 Summary: Entity details > Business Metadata, multi-valued 
attribute spacing issue
 Key: ATLAS-3683
 URL: https://issues.apache.org/jira/browse/ATLAS-3683
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Umesh Padashetty
 Fix For: 2.1.0, 3.0.0
 Attachments: Screenshot 2020-03-25 at 1.14.15 AM.png

While applying Business metadata attribute to an entity, once the multi-valued 
attribute is applied, the multi values are displayed without any spacing. This 
is a bit unreadable. It would be good if we can add a space between 
comma-separated values.

CC: [~kevalbhatt]



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


[jira] [Created] (ATLAS-3682) Multivalued attributes are not listed under Business Metadata Attribute filter

2020-03-23 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3682:
---

 Summary: Multivalued attributes are not listed under Business 
Metadata Attribute filter
 Key: ATLAS-3682
 URL: https://issues.apache.org/jira/browse/ATLAS-3682
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-03-24 at 1.01.54 AM.png, Screenshot 
2020-03-24 at 1.02.28 AM.png

Added attributes of different types, noticed that the multi valued attributes 
are bot being listed for an entity filter, even when the attribute is 
applicable to that entity. Screenshots attached below.

As you can see, the attribute "Reviewed by" which is of type "array" is 
not being listed under the Business Metadata Attribute drop down.

CC: [~kevalbhatt]



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


[jira] [Created] (ATLAS-3681) Cluttered Business Metadata Attribute listing under entity filters

2020-03-23 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3681:
---

 Summary: Cluttered Business Metadata Attribute listing under 
entity filters
 Key: ATLAS-3681
 URL: https://issues.apache.org/jira/browse/ATLAS-3681
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-03-24 at 12.22.41 AM.png

When there are multiple Business Metadata and attributes, the way these are 
listed under the "Business Metadata Attribute" section in filters is too 
cluttered and difficult to read. 

We can
 # Add some spacing between Business Metadata, so that it is easier to 
differentiate between 2 different Business Metadata
 # Follow the approach we have followed for labels and user-defined properties.

CC: [~kevalbhatt]

Screenshot attached

!Screenshot 2020-03-24 at 12.22.41 AM.png!



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


[jira] [Created] (ATLAS-3680) Regression : _ALL_ENTITY_TYPES with any system attribute filter throws 500 exception

2020-03-23 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3680:
---

 Summary: Regression : _ALL_ENTITY_TYPES with any system attribute 
filter throws 500 exception
 Key: ATLAS-3680
 URL: https://issues.apache.org/jira/browse/ATLAS-3680
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
Assignee: Madhan Neethiraj


Search with specific type. such as hive_table and system attribute __timestamp 
and conditions returns right results.

with _ALL_ENTITY_TYPES and any system attribute say __timestamp , 500 Exception 
is thrown with stack trace:
{code:java}
2020-03-23 12:54:05,247 ERROR - [pool-2-thread-10 - 
4cd9a02a-f62c-48bd-8a1d-973c5cdba474:] ~ Error handling a request: 
85f5f4278846ecae (ExceptionMapperUtil:32)
java.lang.IllegalArgumentException: Predicate must not be null
at 
org.apache.commons.collections.functors.AndPredicate.getInstance(AndPredicate.java:51)
at 
org.apache.commons.collections.PredicateUtils.andPredicate(PredicateUtils.java:262)
at 
org.apache.atlas.discovery.EntitySearchProcessor.(EntitySearchProcessor.java:122)
at 
org.apache.atlas.discovery.SearchContext.(SearchContext.java:168)
at 
org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458)
at 
org.apache.atlas.discovery.EntityDiscoveryService$$FastClassBySpringCGLIB$$1af2cf1f.invoke()
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
at 
org.apache.atlas.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$912a463.searchWithParameters()
at 
org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:336)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1712)
at 
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:104)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1699)
at 

[jira] [Assigned] (ATLAS-3678) User defined properties are not listed under suggestions

2020-03-23 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty reassigned ATLAS-3678:
---

Assignee: Madhan Neethiraj

> User defined properties are not listed under suggestions
> 
>
> Key: ATLAS-3678
> URL: https://issues.apache.org/jira/browse/ATLAS-3678
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot 
> 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, 
> Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 
> PM.png
>
>
> When user-defined properties are added to an entity, and when we type the 
> "user-defined property" in the global search bar, the expectation is that 
>  # The corresponding entity appears in the quick search, entities dropdown. 
> This is working 
>  # The user-defined property itself should appear in the suggestions 
> dropdown. This is not working
> Tried similar tests with labels, entities that are tagged with labels appear 
> in the quick search drop down, and the labels itself appear as part of the 
> suggestions. Attached are the screenshots.
>  



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


[jira] [Updated] (ATLAS-3678) User defined properties are not listed under suggestions

2020-03-23 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3678:

Affects Version/s: 3.0.0
   2.1.0

> User defined properties are not listed under suggestions
> 
>
> Key: ATLAS-3678
> URL: https://issues.apache.org/jira/browse/ATLAS-3678
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot 
> 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, 
> Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 
> PM.png
>
>
> When user-defined properties are added to an entity, and when we type the 
> "user-defined property" in the global search bar, the expectation is that 
>  # The corresponding entity appears in the quick search, entities dropdown. 
> This is working 
>  # The user-defined property itself should appear in the suggestions 
> dropdown. This is not working
> Tried similar tests with labels, entities that are tagged with labels appear 
> in the quick search drop down, and the labels itself appear as part of the 
> suggestions. Attached are the screenshots.
>  



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


[jira] [Created] (ATLAS-3678) User defined properties are not listed under suggestions

2020-03-23 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3678:
---

 Summary: User defined properties are not listed under suggestions
 Key: ATLAS-3678
 URL: https://issues.apache.org/jira/browse/ATLAS-3678
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core, atlas-webui
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot 
2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, 
Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 PM.png

When user-defined properties are added to an entity, and when we type the 
"user-defined property" in the global search bar, the expectation is that 
 # The corresponding entity appears in the quick search, entities dropdown. 
This is working 
 # The user-defined property itself should appear in the suggestions dropdown. 
This is not working

Tried similar tests with labels, entities that are tagged with labels appear in 
the quick search drop down, and the labels itself appear as part of the 
suggestions. Attached are the screenshots.

 



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


[jira] [Created] (ATLAS-3677) Business metadata, User-defined properties and Labels information missing in /metrics API and UI

2020-03-22 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3677:
---

 Summary: Business metadata, User-defined properties and Labels 
information missing in /metrics API and UI
 Key: ATLAS-3677
 URL: https://issues.apache.org/jira/browse/ATLAS-3677
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core, atlas-webui
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty


We recently introduced the following in Atlas
 # Business Metadata
 # User-defined properties and
 # Labels

But this information is missing in the /metrics API and UI. We need to decide 
and implement which of the above info will be part of the UI/API



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


[jira] [Assigned] (ATLAS-3677) Business metadata, User-defined properties and Labels information missing in /metrics API and UI

2020-03-22 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty reassigned ATLAS-3677:
---

Assignee: Madhan Neethiraj

> Business metadata, User-defined properties and Labels information missing in 
> /metrics API and UI
> 
>
> Key: ATLAS-3677
> URL: https://issues.apache.org/jira/browse/ATLAS-3677
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Madhan Neethiraj
>Priority: Major
>
> We recently introduced the following in Atlas
>  # Business Metadata
>  # User-defined properties and
>  # Labels
> But this information is missing in the /metrics API and UI. We need to decide 
> and implement which of the above info will be part of the UI/API



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


[jira] [Created] (ATLAS-3676) admin > Administration UI throws Something went wrong error

2020-03-22 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3676:
---

 Summary: admin > Administration UI throws Something went wrong 
error
 Key: ATLAS-3676
 URL: https://issues.apache.org/jira/browse/ATLAS-3676
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
Assignee: Keval Bhatt
 Attachments: Screenshot 2020-03-22 at 10.39.22 PM.png

Looks like this issue is due to the recently added Audits tab under admin > 
administration page

The POST call to /api/atlas/admin/audits is failing with 500 Internal Server 
Error. Screenshot attached !Screenshot 2020-03-22 at 10.39.22 
PM.png|width=2146,height=986!



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


[jira] [Updated] (ATLAS-3637) [Namespace-UI] Incorrect values populated while editing a Namespace attribute, after an unsuccessful attempt to add a duplicate attribute

2020-02-25 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3637:

Description: 
Steps to reproduce:
 # In an existing Namespace, try to add a duplicate attribute. Change the 
applicable types, type and length. This throws an error due to ATLAS-3636
 # Now come back and try to edit the same attribute. The values populated are 
incorrect. Instead of populating the original attribute values, the UI is 
populating the recentmost duplicate attributes values which we tried to add in 
step 1

Video recordings attached.

  was:
Steps to reproduce:
 # In an existing Namespace, try to add a duplicate attribute. Change the 
applicable types, type and length. This throws an error due to ATLAS-3636
 # Now come back and try to edit the same attribute. The values populated are 
incorrect. Instead of populating the original attribute values, the UI is 
populating the recentmost duplicate attributes values which we tried to add in 
step 1


> [Namespace-UI] Incorrect values populated while editing a Namespace 
> attribute, after an unsuccessful attempt to add a duplicate attribute
> -
>
> Key: ATLAS-3637
> URL: https://issues.apache.org/jira/browse/ATLAS-3637
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3637-1.mov, ATLAS-3637.mov
>
>
> Steps to reproduce:
>  # In an existing Namespace, try to add a duplicate attribute. Change the 
> applicable types, type and length. This throws an error due to ATLAS-3636
>  # Now come back and try to edit the same attribute. The values populated are 
> incorrect. Instead of populating the original attribute values, the UI is 
> populating the recentmost duplicate attributes values which we tried to add 
> in step 1
> Video recordings attached.



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


[jira] [Updated] (ATLAS-3637) [Namespace-UI] Incorrect values populated while editing a Namespace attribute, after an unsuccessful attempt to add a duplicate attribute

2020-02-25 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3637:

Attachment: ATLAS-3637-1.mov
ATLAS-3637.mov

> [Namespace-UI] Incorrect values populated while editing a Namespace 
> attribute, after an unsuccessful attempt to add a duplicate attribute
> -
>
> Key: ATLAS-3637
> URL: https://issues.apache.org/jira/browse/ATLAS-3637
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3637-1.mov, ATLAS-3637.mov
>
>
> Steps to reproduce:
>  # In an existing Namespace, try to add a duplicate attribute. Change the 
> applicable types, type and length. This throws an error due to ATLAS-3636
>  # Now come back and try to edit the same attribute. The values populated are 
> incorrect. Instead of populating the original attribute values, the UI is 
> populating the recentmost duplicate attributes values which we tried to add 
> in step 1



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


[jira] [Created] (ATLAS-3637) [Namespace-UI] Incorrect values populated while editing a Namespace attribute, after an unsuccessful attempt to add a duplicate attribute

2020-02-25 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3637:
---

 Summary: [Namespace-UI] Incorrect values populated while editing a 
Namespace attribute, after an unsuccessful attempt to add a duplicate attribute
 Key: ATLAS-3637
 URL: https://issues.apache.org/jira/browse/ATLAS-3637
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
Assignee: Keval Bhatt


Steps to reproduce:
 # In an existing Namespace, try to add a duplicate attribute. Change the 
applicable types, type and length. This throws an error due to ATLAS-3636
 # Now come back and try to edit the same attribute. The values populated are 
incorrect. Instead of populating the original attribute values, the UI is 
populating the recentmost duplicate attributes values which we tried to add in 
step 1



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


[jira] [Updated] (ATLAS-3636) [Namespace-UI] Issues/ambiguous error messages while adding a new attribute in a Namespace

2020-02-25 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3636:

  Component/s: atlas-webui
Affects Version/s: 3.0.0
   2.1.0

> [Namespace-UI] Issues/ambiguous error messages while adding a new attribute 
> in a Namespace
> --
>
> Key: ATLAS-3636
> URL: https://issues.apache.org/jira/browse/ATLAS-3636
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: Screenshot 2020-02-25 at 4.03.16 PM.png, Screenshot 
> 2020-02-25 at 4.06.24 PM.png, Screenshot 2020-02-25 at 4.07.15 PM.png, 
> Screenshot 2020-02-25 at 4.08.33 PM.png, Screenshot 2020-02-25 at 4.18.39 
> PM.png
>
>
> Multiple issues have been observed when we click on add attribute in 
> admin>administration>Namespaces>\{existing_namespace}
>  # If the new attribute name and other parameters like Type, Max length, 
> Applicable Types are the same as an existing attribute, it is going ahead and 
> updating the attribute silently instead of throwing "Attribute already 
> exists" error.
>  # If the new attribute being added has all the parameters same except 
> Applicable Types
>  ## If we are adding a new applicable type without removing the old one, then 
> it is silently updating the older existing attribute with the new applicable 
> type
>  ## If we try to remove/provide empty applicable types, then an error is 
> being thrown in UI which is very ambiguous. Error is something like "Cannot 
> remove applicableEntityTypes in Attribute Def: Region, defined in namespace: 
> Customer"
>  # Once you get some error while adding an attribute (like step Step 2, 
> Sub-step 2 above), the same error message is being displayed for the 
> subsequent additions. 
>  ## For instance, I tried to add a duplicate attribute with the name Region. 
> And then tried to add a duplicate attribute with the name country. But while 
> adding country attribute, I am getting "Cannot remove applicableEntityTypes 
> in Attribute Def: Region, defined in namespace: Customer"
>  ## After this any attempt to add any new attribute with an non-duplicate 
> unique attribute thorws the same old error. I tried adding a new attribute 
> called Region1, but still keep getting the same error "Cannot remove 
> applicableEntityTypes in Attribute Def: Region, defined in namespace: 
> Customer"
>  ## One can successfully add a new attribute only after a page refresh
> Attached screenshots.



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


[jira] [Created] (ATLAS-3636) [Namespace-UI] Issues/ambiguous error messages while adding a new attribute in a Namespace

2020-02-25 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3636:
---

 Summary: [Namespace-UI] Issues/ambiguous error messages while 
adding a new attribute in a Namespace
 Key: ATLAS-3636
 URL: https://issues.apache.org/jira/browse/ATLAS-3636
 Project: Atlas
  Issue Type: Bug
Reporter: Umesh Padashetty
Assignee: Keval Bhatt
 Attachments: Screenshot 2020-02-25 at 4.03.16 PM.png, Screenshot 
2020-02-25 at 4.06.24 PM.png, Screenshot 2020-02-25 at 4.07.15 PM.png, 
Screenshot 2020-02-25 at 4.08.33 PM.png, Screenshot 2020-02-25 at 4.18.39 PM.png

Multiple issues have been observed when we click on add attribute in 
admin>administration>Namespaces>\{existing_namespace}
 # If the new attribute name and other parameters like Type, Max length, 
Applicable Types are the same as an existing attribute, it is going ahead and 
updating the attribute silently instead of throwing "Attribute already exists" 
error.
 # If the new attribute being added has all the parameters same except 
Applicable Types
 ## If we are adding a new applicable type without removing the old one, then 
it is silently updating the older existing attribute with the new applicable 
type
 ## If we try to remove/provide empty applicable types, then an error is being 
thrown in UI which is very ambiguous. Error is something like "Cannot remove 
applicableEntityTypes in Attribute Def: Region, defined in namespace: Customer"
 # Once you get some error while adding an attribute (like step Step 2, 
Sub-step 2 above), the same error message is being displayed for the subsequent 
additions. 
 ## For instance, I tried to add a duplicate attribute with the name Region. 
And then tried to add a duplicate attribute with the name country. But while 
adding country attribute, I am getting "Cannot remove applicableEntityTypes in 
Attribute Def: Region, defined in namespace: Customer"
 ## After this any attempt to add any new attribute with an non-duplicate 
unique attribute thorws the same old error. I tried adding a new attribute 
called Region1, but still keep getting the same error "Cannot remove 
applicableEntityTypes in Attribute Def: Region, defined in namespace: Customer"
 ## One can successfully add a new attribute only after a page refresh

Attached screenshots.



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


[jira] [Updated] (ATLAS-3635) [Namespace-UI] Noticeable delay in loading Namespace section in entity details page

2020-02-25 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty updated ATLAS-3635:

Description: 
On clicking an entity, the Namespace section takes around 3-4 seconds extra to 
load even when the complete page has loaded successfully. The namespace section 
suddenly pops up.

This behavior is consistently reproducible in Google Chrome, and not so evident 
in Firefox (the delay is way lesser, hence difficult to notice)

Attached screenshots.

  was:
On clicking an entity, the Namespace section takes around 3-4 seconds extra to 
load even when the complete page has loaded successfully. The namespace section 
suddenly pops up.

This behavior is consistently reproducible in Google Chrome, and not so evident 
in Firefox (the delay is way lesser, hence difficult to notice)

Attached screenshots and video.[^Screen Recording 2020-02-25 at 2.59.07 PM.mov]


> [Namespace-UI] Noticeable delay in loading Namespace section in entity 
> details page
> ---
>
> Key: ATLAS-3635
> URL: https://issues.apache.org/jira/browse/ATLAS-3635
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screenshot 2020-02-25 at 2.59.51 PM.png, Screenshot 
> 2020-02-25 at 3.00.14 PM.png
>
>
> On clicking an entity, the Namespace section takes around 3-4 seconds extra 
> to load even when the complete page has loaded successfully. The namespace 
> section suddenly pops up.
> This behavior is consistently reproducible in Google Chrome, and not so 
> evident in Firefox (the delay is way lesser, hence difficult to notice)
> Attached screenshots.



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


[jira] [Assigned] (ATLAS-3633) Namespace attributes defined for superTypes are not listed in the derived entity details page

2020-02-25 Thread Umesh Padashetty (Jira)


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

Umesh Padashetty reassigned ATLAS-3633:
---

Assignee: Keval Bhatt

> Namespace attributes defined for superTypes are not listed in the derived 
> entity details page
> -
>
> Key: ATLAS-3633
> URL: https://issues.apache.org/jira/browse/ATLAS-3633
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screenshot 2020-02-25 at 2.33.48 PM.png, Screenshot 
> 2020-02-25 at 2.34.03 PM.png
>
>
> As per Atlas Typesystem, [https://atlas.apache.org/#/TypeSystem], we have the 
> following pre-defined system types
>  * Referenceable:
>  * Asset:
>  * Infrastructure: 
>  * DataSet: 
>  * Process:
>  * Process Execution
> Since these are the super types, where -> stands for extends
>  * Referenceable -> Asset
>  * Referenceable -> Asset -> Infrastructure
>  * Referenceable -> Asset -> DataSet
>  * Referenceable -> Asset -> Process
>  * Referenceable -> Asset -> Process Execution
> Adding Referenceable/Asset/DataSet super types in the applicable types of a 
> Namespace attribute should ideally make it available for all the entity types 
> which extend these super types. 
> For instance, hive_table has DataSet as the superTypes. Adding DataSet as the 
> applicable type in namespace definition should allow us to link this 
> Namespace attribute to all the hive_table entities. Currently, these 
> attributes are not being listed in the entity details page, we have to 
> provide the exact derived entity (like hive_table) in the applicable types.
> Attached are the screenshots.



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


[jira] [Created] (ATLAS-3635) [Namespace-UI] Noticeable delay in loading Namespace section in entity details page

2020-02-25 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3635:
---

 Summary: [Namespace-UI] Noticeable delay in loading Namespace 
section in entity details page
 Key: ATLAS-3635
 URL: https://issues.apache.org/jira/browse/ATLAS-3635
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
Assignee: Keval Bhatt
 Attachments: Screenshot 2020-02-25 at 2.59.51 PM.png, Screenshot 
2020-02-25 at 3.00.14 PM.png

On clicking an entity, the Namespace section takes around 3-4 seconds extra to 
load even when the complete page has loaded successfully. The namespace section 
suddenly pops up.

This behavior is consistently reproducible in Google Chrome, and not so evident 
in Firefox (the delay is way lesser, hence difficult to notice)

Attached screenshots and video.[^Screen Recording 2020-02-25 at 2.59.07 PM.mov]



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


[jira] [Created] (ATLAS-3633) Namespace attributes defined for superTypes are not listed in the derived entity details page

2020-02-25 Thread Umesh Padashetty (Jira)
Umesh Padashetty created ATLAS-3633:
---

 Summary: Namespace attributes defined for superTypes are not 
listed in the derived entity details page
 Key: ATLAS-3633
 URL: https://issues.apache.org/jira/browse/ATLAS-3633
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core, atlas-webui
Affects Versions: 2.1.0, 3.0.0
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-02-25 at 2.33.48 PM.png, Screenshot 
2020-02-25 at 2.34.03 PM.png

As per Atlas Typesystem, [https://atlas.apache.org/#/TypeSystem], we have the 
following pre-defined system types
 * Referenceable:
 * Asset:
 * Infrastructure: 
 * DataSet: 
 * Process:
 * Process Execution

Since these are the super types, where -> stands for extends
 * Referenceable -> Asset
 * Referenceable -> Asset -> Infrastructure
 * Referenceable -> Asset -> DataSet
 * Referenceable -> Asset -> Process
 * Referenceable -> Asset -> Process Execution

Adding Referenceable/Asset/DataSet super types in the applicable types of a 
Namespace attribute should ideally make it available for all the entity types 
which extend these super types. 

For instance, hive_table has DataSet as the superTypes. Adding DataSet as the 
applicable type in namespace definition should allow us to link this Namespace 
attribute to all the hive_table entities. Currently, these attributes are not 
being listed in the entity details page, we have to provide the exact derived 
entity (like hive_table) in the applicable types.

Attached are the screenshots.



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


[jira] [Updated] (ATLAS-3239) Documentation fix in https://atlas.apache.org/TypeSystem.html and http://atlas.apache.org/InstallationSteps.html

2019-05-28 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3239:

Summary: Documentation fix in https://atlas.apache.org/TypeSystem.html and 
http://atlas.apache.org/InstallationSteps.html  (was: Documentation fix in 
https://atlas.apache.org/TypeSystem.html)

> Documentation fix in https://atlas.apache.org/TypeSystem.html and 
> http://atlas.apache.org/InstallationSteps.html
> 
>
> Key: ATLAS-3239
> URL: https://issues.apache.org/jira/browse/ATLAS-3239
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0, 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Trivial
> Fix For: 1.0.0, 1.1.0, 2.0.0
>
> Attachments: ATLAS-3239-1.patch, ATLAS-3239.patch
>
>
> In https://atlas.apache.org/TypeSystem.html, under "System specific types and 
> their significance" >> DataSet, Dataset is defined as "This type extends 
> Referenceable", but Dataset actually extends Asset, which in turn extends 
> Referenceable. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3239) Documentation fix in https://atlas.apache.org/TypeSystem.html and http://atlas.apache.org/InstallationSteps.html

2019-05-28 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3239:

Description: 
In [https://atlas.apache.org/TypeSystem.html], under "System specific types and 
their significance" >> DataSet, Dataset is defined as "This type extends 
Referenceable", but Dataset actually extends Asset, which in turn extends 
Referenceable. 

Replaced all 1.0.0 reference to 2.0.0 in 
[http://atlas.apache.org/InstallationSteps.html]

  was:In https://atlas.apache.org/TypeSystem.html, under "System specific types 
and their significance" >> DataSet, Dataset is defined as "This type extends 
Referenceable", but Dataset actually extends Asset, which in turn extends 
Referenceable. 


> Documentation fix in https://atlas.apache.org/TypeSystem.html and 
> http://atlas.apache.org/InstallationSteps.html
> 
>
> Key: ATLAS-3239
> URL: https://issues.apache.org/jira/browse/ATLAS-3239
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0, 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Trivial
> Fix For: 1.0.0, 1.1.0, 2.0.0
>
> Attachments: ATLAS-3239-1.patch, ATLAS-3239.patch
>
>
> In [https://atlas.apache.org/TypeSystem.html], under "System specific types 
> and their significance" >> DataSet, Dataset is defined as "This type extends 
> Referenceable", but Dataset actually extends Asset, which in turn extends 
> Referenceable. 
> Replaced all 1.0.0 reference to 2.0.0 in 
> [http://atlas.apache.org/InstallationSteps.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3239) Documentation fix in https://atlas.apache.org/TypeSystem.html

2019-05-28 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3239:

Attachment: ATLAS-3239-1.patch

> Documentation fix in https://atlas.apache.org/TypeSystem.html
> -
>
> Key: ATLAS-3239
> URL: https://issues.apache.org/jira/browse/ATLAS-3239
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0, 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Trivial
> Fix For: 1.0.0, 1.1.0, 2.0.0
>
> Attachments: ATLAS-3239-1.patch, ATLAS-3239.patch
>
>
> In https://atlas.apache.org/TypeSystem.html, under "System specific types and 
> their significance" >> DataSet, Dataset is defined as "This type extends 
> Referenceable", but Dataset actually extends Asset, which in turn extends 
> Referenceable. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-3239) Documentation fix in https://atlas.apache.org/TypeSystem.html

2019-05-27 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty commented on ATLAS-3239:
-

Review Board Link: [https://reviews.apache.org/r/70725/]

> Documentation fix in https://atlas.apache.org/TypeSystem.html
> -
>
> Key: ATLAS-3239
> URL: https://issues.apache.org/jira/browse/ATLAS-3239
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0, 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Umesh Padashetty
>Priority: Trivial
> Fix For: 1.0.0, 1.1.0, 2.0.0
>
> Attachments: ATLAS-3239.patch
>
>
> In https://atlas.apache.org/TypeSystem.html, under "System specific types and 
> their significance" >> DataSet, Dataset is defined as "This type extends 
> Referenceable", but Dataset actually extends Asset, which in turn extends 
> Referenceable. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-3239) Documentation fix in https://atlas.apache.org/TypeSystem.html

2019-05-27 Thread Umesh Padashetty (JIRA)
Umesh Padashetty created ATLAS-3239:
---

 Summary: Documentation fix in 
https://atlas.apache.org/TypeSystem.html
 Key: ATLAS-3239
 URL: https://issues.apache.org/jira/browse/ATLAS-3239
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.0.0, 1.1.0, 1.0.0
Reporter: Umesh Padashetty
Assignee: Umesh Padashetty
 Fix For: 2.0.0, 1.1.0, 1.0.0


In https://atlas.apache.org/TypeSystem.html, under "System specific types and 
their significance" >> DataSet, Dataset is defined as "This type extends 
Referenceable", but Dataset actually extends Asset, which in turn extends 
Referenceable. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (ATLAS-3237) Can't create Entities via Web Interface

2019-05-26 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty edited comment on ATLAS-3237 at 5/27/19 2:23 AM:
--

[~Zep] This is by design since most of the metadata in Atlas is onbaorded via 
hooks and bridges. The entity types which appear in the create entity drop down 
can be set using the config "atlas.ui.editable.entity.types" property which can 
be configured as editableEntityTypes and DEFAULT_EDITABLE_ENTITY_TYPES in 
AdminResource.java. 

If you prefer not making the changes in the code (allowing the entities to 
appear by default), then you can add the property 
atlas.ui.editable.entity.types in atlas-application.properties and restart.

Values are comma separated, for instance, 
_atlas.ui.editable.entity.types=hdfs_path,kafka_topic_


was (Author: umesh.padashetty):
[~Zep] This is by design, since most of the metadata in Atlas is onbaorded via 
hooks and bridges. The entites which appear in the create entity drop down can 
be set using the config "atlas.ui.editable.entity.types" property which can be 
configured as editableEntityTypes and DEFAULT_EDITABLE_ENTITY_TYPES in 
AdminResource.java. 

If you prefer not making the changes in the code (allowing the entities to 
appear by default), then you can add the property 
atlas.ui.editable.entity.types in atlas-application.properties and restart.

Values are comma separated, for instance, 
_atlas.ui.editable.entity.types=hdfs_path,kafka_topic_

> Can't create Entities via Web Interface
> ---
>
> Key: ATLAS-3237
> URL: https://issues.apache.org/jira/browse/ATLAS-3237
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0, 2.1.0, 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Umesh Padashetty
>Priority: Major
> Attachments: atlas.png
>
>
> Trying to create entities using web interface it is possible create entity 
> only of hdfs_path type. Is there any particular choice by design is simply a 
> bug?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-3237) Can't create Entities via Web Interface

2019-05-26 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty resolved ATLAS-3237.
-
Resolution: Not A Bug
  Assignee: Umesh Padashetty

> Can't create Entities via Web Interface
> ---
>
> Key: ATLAS-3237
> URL: https://issues.apache.org/jira/browse/ATLAS-3237
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0, 2.1.0, 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Umesh Padashetty
>Priority: Major
> Attachments: atlas.png
>
>
> Trying to create entities using web interface it is possible create entity 
> only of hdfs_path type. Is there any particular choice by design is simply a 
> bug?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (ATLAS-3231) Service specific icon should be shown for "process_execution"

2019-05-23 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty edited comment on ATLAS-3231 at 5/24/19 5:01 AM:
--

The recent introduction of Process Execution captures the multiple executions 
of DML queries. When navigating to process_execution, right now default icon is 
being shown. We need to show service specific icons here. Attached is the 
screenshot.


was (Author: umesh.padashetty):
The recent introduction of Process Execution captures the multiple executions 
of DDL queries. When navigating to process_execution, right now default icon is 
being shown. We need to show service specific icons here. Attached is the 
screenshot.

> Service specific icon should be shown for "process_execution"
> -
>
> Key: ATLAS-3231
> URL: https://issues.apache.org/jira/browse/ATLAS-3231
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2019-05-24 at 8.48.10 AM.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-3231) Service specific icon should be shown for "process_execution"

2019-05-23 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty commented on ATLAS-3231:
-

The recent introduction of Process Execution captures the multiple executions 
of DDL queries. When navigating to process_execution, right now default icon is 
being shown. We need to show service specific icons here. Attached is the 
screenshot.

> Service specific icon should be shown for "process_execution"
> -
>
> Key: ATLAS-3231
> URL: https://issues.apache.org/jira/browse/ATLAS-3231
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2019-05-24 at 8.48.10 AM.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-3229) DDL should not capture dml queries

2019-05-23 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty commented on ATLAS-3229:
-

Thanks for raising a Jira for this [~lma]. I have attached a screenshot to help 
debug.

> DDL should not capture dml queries
> --
>
> Key: ATLAS-3229
> URL: https://issues.apache.org/jira/browse/ATLAS-3229
> Project: Atlas
>  Issue Type: Bug
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
> Attachments: Screenshot 2019-05-24 at 8.46.02 AM.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-3231) Service specific icon should be shown for "hive_process_execution"

2019-05-23 Thread Umesh Padashetty (JIRA)
Umesh Padashetty created ATLAS-3231:
---

 Summary: Service specific icon should be shown for 
"hive_process_execution"
 Key: ATLAS-3231
 URL: https://issues.apache.org/jira/browse/ATLAS-3231
 Project: Atlas
  Issue Type: Improvement
Reporter: Umesh Padashetty
 Attachments: Screenshot 2019-05-24 at 8.48.10 AM.png





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3231) Service specific icon should be shown for "process_execution"

2019-05-23 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3231:

Summary: Service specific icon should be shown for "process_execution"  
(was: Service specific icon should be shown for "hive_process_execution")

> Service specific icon should be shown for "process_execution"
> -
>
> Key: ATLAS-3231
> URL: https://issues.apache.org/jira/browse/ATLAS-3231
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2019-05-24 at 8.48.10 AM.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3229) DDL should not capture dml queries

2019-05-23 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3229:

Attachment: Screenshot 2019-05-24 at 8.46.02 AM.png

> DDL should not capture dml queries
> --
>
> Key: ATLAS-3229
> URL: https://issues.apache.org/jira/browse/ATLAS-3229
> Project: Atlas
>  Issue Type: Bug
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
> Attachments: Screenshot 2019-05-24 at 8.46.02 AM.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (ATLAS-3175) UI: Incorrect count shown beside the Type and Classification dropdown list in search

2019-05-15 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty closed ATLAS-3175.
---

> UI: Incorrect count shown beside the Type and Classification dropdown list in 
> search
> 
>
> Key: ATLAS-3175
> URL: https://issues.apache.org/jira/browse/ATLAS-3175
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.3
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: Screenshot 2019-04-26 at 3.19.27 PM.png, Screenshot 
> 2019-04-26 at 3.20.13 PM.png
>
>
> Steps for reproduction:
>  # Login to Atlas UI
>  # Click on Advanced Search
>  # Click on "Search By Type"
>  # Check the count against kafka_topic
>  # Create a new kafka_topic entity
>  # Refresh the page
>  # Again check the count against kafka_topic under "Search By Type"
> It is taking a long time for the count to be updated in the UI. Browser clear 
> cache and incognito mode did not help
>  # The type count under "Search By Type" drop-down should be updated when a 
> new entity type is created. This is happening for entities created via UI as 
> well as via HOOK
>  # Classification count under "Search By Classification" should be updated 
> when an entity is classified. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-3198) update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements

2019-05-08 Thread Umesh Padashetty (JIRA)
Umesh Padashetty created ATLAS-3198:
---

 Summary: update/delete/truncate operations ATLAS_HOOK and 
ATLAS_ENTITIES improvements 
 Key: ATLAS-3198
 URL: https://issues.apache.org/jira/browse/ATLAS-3198
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Umesh Padashetty
 Fix For: 2.0.0
 Attachments: ATLAS_HOOK and ATLAS_ENTITIES messages.xlsx

With the recent changes, we have now stopped ingesting simple insert operations 
since with this operation, there is no change in the metadata. Ideally, we 
should be doing similar improvements w.r.t. update, delete and truncate 
operations too. 

Currently, for update/delete/truncate, we are pushing messages in both 
ATLAS_HOOK as well as ATLAS_ENTITIES topic, which can be avoided. 

If we stop ingesting updates/deletes/truncates, it will further help us reduce 
the burden on Kafka and save CPU cycles

I have created and attached an excel sheet, with the list of operations and the 
corresponding messages generated in ATLAS_HOOK and ATLAS_ENTITIES topic, along 
with suitable comments. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3188) Regression: Simple insert queries are being captured in ATLAS_HOOK topic

2019-05-02 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3188:

Fix Version/s: 2.0.0

> Regression: Simple insert queries are being captured in ATLAS_HOOK topic
> 
>
> Key: ATLAS-3188
> URL: https://issues.apache.org/jira/browse/ATLAS-3188
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Priority: Major
> Fix For: 2.0.0
>
>
> insert into  values () is triggering messages in ATLAS_HOOK 
> topic. Due to this, Atlas is reporting the operations in Audits. 
> Ideally, insert queries should not generate any messages in ATLAS_HOOK since 
> they do not play any role in lineage 
> Inserting 100 rows in a table is generating 100 messages in the kafka topic. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-3188) Regression: Simple insert queries are being captured in ATLAS_HOOK topic

2019-05-02 Thread Umesh Padashetty (JIRA)
Umesh Padashetty created ATLAS-3188:
---

 Summary: Regression: Simple insert queries are being captured in 
ATLAS_HOOK topic
 Key: ATLAS-3188
 URL: https://issues.apache.org/jira/browse/ATLAS-3188
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Umesh Padashetty


insert into  values () is triggering messages in ATLAS_HOOK 
topic. Due to this, Atlas is reporting the operations in Audits. 

Ideally, insert queries should not generate any messages in ATLAS_HOOK since 
they do not play any role in lineage 

Inserting 100 rows in a table is generating 100 messages in the kafka topic. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3175) UI: Incorrect count shown beside the Type and Classification dropdown list in search

2019-04-26 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3175:

Description: 
Steps for reproduction:
 # Login to Atlas UI
 # Click on Advanced Search
 # Click on "Search By Type"
 # Check the count against kafka_topic
 # Create a new kafka_topic entity
 # Refresh the page
 # Again check the count against kafka_topic under "Search By Type"

It is taking a long time for the count to be updated in the UI. Browser clear 
cache and incognito mode did not help
 # The type count under "Search By Type" drop-down should be updated when a new 
entity type is created. This is happening for entities created via UI as well 
as via HOOK
 # Classification count under "Search By Classification" should be updated when 
an entity is classified. 

  was:
It is taking a long time for the count to be updated in the UI. Browser clear 
cache and incognito mode did not help
 # The type count under "Search By Type" drop-down should be updated when a new 
entity type is created. This is happening for entities created via UI as well 
as via HOOK
 # Classification count under "Search By Classification" should be updated when 
an entity is classified. 


> UI: Incorrect count shown beside the Type and Classification dropdown list in 
> search
> 
>
> Key: ATLAS-3175
> URL: https://issues.apache.org/jira/browse/ATLAS-3175
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: Screenshot 2019-04-26 at 3.19.27 PM.png, Screenshot 
> 2019-04-26 at 3.20.13 PM.png
>
>
> Steps for reproduction:
>  # Login to Atlas UI
>  # Click on Advanced Search
>  # Click on "Search By Type"
>  # Check the count against kafka_topic
>  # Create a new kafka_topic entity
>  # Refresh the page
>  # Again check the count against kafka_topic under "Search By Type"
> It is taking a long time for the count to be updated in the UI. Browser clear 
> cache and incognito mode did not help
>  # The type count under "Search By Type" drop-down should be updated when a 
> new entity type is created. This is happening for entities created via UI as 
> well as via HOOK
>  # Classification count under "Search By Classification" should be updated 
> when an entity is classified. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3175) UI: Incorrect count shown beside the Type and Classification dropdown list in search

2019-04-26 Thread Umesh Padashetty (JIRA)


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

Umesh Padashetty updated ATLAS-3175:

Attachment: Screenshot 2019-04-26 at 3.20.13 PM.png

> UI: Incorrect count shown beside the Type and Classification dropdown list in 
> search
> 
>
> Key: ATLAS-3175
> URL: https://issues.apache.org/jira/browse/ATLAS-3175
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: Screenshot 2019-04-26 at 3.19.27 PM.png, Screenshot 
> 2019-04-26 at 3.20.13 PM.png
>
>
> It is taking a long time for the count to be updated in the UI. Browser clear 
> cache and incognito mode did not help
>  # The type count under "Search By Type" drop-down should be updated when a 
> new entity type is created. This is happening for entities created via UI as 
> well as via HOOK
>  # Classification count under "Search By Classification" should be updated 
> when an entity is classified. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


  1   2   >