[jira] [Resolved] (ATLAS-4203) [Business Metadata] Issue with saving floating point numbers in case of attributes of 'float' type

2021-06-16 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-4203.

  Assignee: Mandar Ambawane
Resolution: Won't Fix

> [Business Metadata] Issue with saving floating point numbers in case of 
> attributes of 'float' type 
> ---
>
> Key: ATLAS-4203
> URL: https://issues.apache.org/jira/browse/ATLAS-4203
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Umesh Padashetty
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: After save.png, Before save.png
>
>
> A value entered as -234567890123456.12 gets saved as -23456789400
> A value entered as 234567890123456.12 gets saved as 23456789400
> Screenshots attached.



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


[jira] [Commented] (ATLAS-4203) [Business Metadata] Issue with saving floating point numbers in case of attributes of 'float' type

2021-06-16 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane commented on ATLAS-4203:


Hi [~umesh.padashetty] 

This behavior is not specific to Business Metadata attributes. This can be seen 
in all over the application where Floating point Data type is used.

As Floating point numbers  have a limited number of digits, they cannot 
represent all real numbers accurately. When there are more digits than the 
format allows,  the number is rounded.

> [Business Metadata] Issue with saving floating point numbers in case of 
> attributes of 'float' type 
> ---
>
> Key: ATLAS-4203
> URL: https://issues.apache.org/jira/browse/ATLAS-4203
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: After save.png, Before save.png
>
>
> A value entered as -234567890123456.12 gets saved as -23456789400
> A value entered as 234567890123456.12 gets saved as 23456789400
> Screenshots attached.



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


[jira] [Assigned] (ATLAS-4336) Restrict attributes of type to be created starting with double underscore

2021-06-11 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4336:
--

Assignee: Mandar Ambawane

> Restrict attributes of type to be created starting with double underscore
> -
>
> Key: ATLAS-4336
> URL: https://issues.apache.org/jira/browse/ATLAS-4336
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha S
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently type can be updated with an attribute whose name starts with "__" 
> like __guid.
> This gets mixed up with system attributes.
> Hence attribute names should not be allowed to be started with double 
> underscore or following attribute names (system attribute names) should be 
> restricted when a type is created or updated :
> __classificationNames
> __modifiedBy
> __createdBy
> __state
> __typeName
> __modificationTimestamp
> __propagatedClassificationNames
> __customAttributes
> __isIncomplete
> __guid
> __timestamp
> __labels



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


[jira] [Resolved] (ATLAS-4038) Client ID field in the Admin audit result captures the Server/Host IP instead of the Client IP

2021-06-10 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-4038.

Resolution: Fixed

> Client ID field in the Admin audit result captures the Server/Host IP instead 
> of the Client IP
> --
>
> Key: ATLAS-4038
> URL: https://issues.apache.org/jira/browse/ATLAS-4038
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> The Client ID field is supposed to capture the Client address from which the 
> request is made, but it captures the server address on which this request 
> lands instead.
> This incorrect behaviour is observed in all the operations audits except 
> SERVER_START and SERVER_STATE_ACTIVE



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


[jira] [Updated] (ATLAS-4301) Handle Test Case Failure on Pre-commit environment

2021-06-03 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4301:
---
Description: 
Getting following error on Pre-commit build due to change in the file path

hive-bridge/target/logs/application.log
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}
 

Also,

There is Enum "Type" in the "Entity"
{code:java}
Class: org.apache.hadoop.hive.ql.hooks.Entity
Enum: Type{code}
Enum "Type" has one constant "LOCAL_DIR"

Due to recent changes, we need to provide support for this constant "LOCAL_DIR" 
in Testing Environment.

Without which following issues occuring on Testing Environment:
 # While creating "hive_process" entity, The "outputs" attribute is not getting 
set (Which is of type "hdfs_path").
 # While setting the "qualifiedName" of "hive_process" entity, File path is not 
getting appended.

This causing Failure of some Test cases.

  was:
Getting following error on Pre-commit build due to change in the file path

 hive-bridge/target/logs/application.log
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}


> Handle Test Case Failure on Pre-commit environment
> --
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> hive-bridge/target/logs/application.log
> {code:java}
> Wrong FS: 
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
>  expected: file:///
> {code}
>  
> Also,
> There is Enum "Type" in the "Entity"
> {code:java}
> Class: org.apache.hadoop.hive.ql.hooks.Entity
> Enum: Type{code}
> Enum "Type" has one constant "LOCAL_DIR"
> Due to recent changes, we need to provide support for this constant 
> "LOCAL_DIR" in Testing Environment.
> Without which following issues occuring on Testing Environment:
>  # While creating "hive_process" entity, The "outputs" attribute is not 
> getting set (Which is of type "hdfs_path").
>  # While setting the "qualifiedName" of "hive_process" entity, File path is 
> not getting appended.
> This causing Failure of some Test cases.



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


[jira] [Assigned] (ATLAS-4290) [Atlas: Glossary Term Bulk Import] There is not much info available in logs importing terms in bulk

2021-05-26 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4290:
--

Assignee: Mandar Ambawane

> [Atlas: Glossary Term Bulk Import] There is not much info available in logs 
> importing terms in bulk
> ---
>
> Key: ATLAS-4290
> URL: https://issues.apache.org/jira/browse/ATLAS-4290
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> While creating a term there is a statement "GraphTransaction intercept for 
> org.apache.atlas.glossary.GlossaryService.createTerm" in logs, but while 
> performing bulk import, there are no information logs available.
>  



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


[jira] [Updated] (ATLAS-4301) Handle Test Case Failure on Pre-commit environment

2021-05-24 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4301:
---
Summary: Handle Test Case Failure on Pre-commit environment  (was: Resolve 
Test Case Failure on Pre-commit environment)

> Handle Test Case Failure on Pre-commit environment
> --
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
>  hive-bridge/target/logs/application.log
> {code:java}
> Wrong FS: 
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
>  expected: file:///
> {code}



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


[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment

2021-05-24 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4301:
---
Description: 
Getting following error on Pre-commit build due to change in the file path

 hive-bridge/target/logs/application.log
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}

  was:
Getting following error on Pre-commit build due to change in the file path
+
hive-bridge/target/logs/application.log
+
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}


> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
>  hive-bridge/target/logs/application.log
> {code:java}
> Wrong FS: 
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
>  expected: file:///
> {code}



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


[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment

2021-05-24 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4301:
---
Description: 
Getting following error on Pre-commit build due to change in the file path
+
hive-bridge/target/logs/application.log
+
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}

  was:
Getting following error on Pre-commit build due to change in the file path
[hive-bridge/target/logs/application.log|https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/562/artifact/addons/hive-bridge/target/logs/application.log]
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}


> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> +
> hive-bridge/target/logs/application.log
> +
> {code:java}
> Wrong FS: 
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
>  expected: file:///
> {code}



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


[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment

2021-05-24 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4301:
---
Description: 
Getting following error on Pre-commit build due to change in the file path
[hive-bridge/target/logs/application.log|https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/562/artifact/addons/hive-bridge/target/logs/application.log]
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}

  was:
Getting following error on Pre-commit build due to change in the file path
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}


> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> [hive-bridge/target/logs/application.log|https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/562/artifact/addons/hive-bridge/target/logs/application.log]
> {code:java}
> Wrong FS: 
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
>  expected: file:///
> {code}



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


[jira] [Created] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment

2021-05-24 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-4301:
--

 Summary: Resolve Test Case Failure on Pre-commit environment
 Key: ATLAS-4301
 URL: https://issues.apache.org/jira/browse/ATLAS-4301
 Project: Atlas
  Issue Type: Improvement
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane






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


[jira] [Updated] (ATLAS-4301) Resolve Test Case Failure on Pre-commit environment

2021-05-24 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4301:
---
Description: 
Getting following error on Pre-commit build due to change in the file path
{code:java}
Wrong FS: 
pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
 expected: file:///
{code}

> Resolve Test Case Failure on Pre-commit environment
> ---
>
> Key: ATLAS-4301
> URL: https://issues.apache.org/jira/browse/ATLAS-4301
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Getting following error on Pre-commit build due to change in the file path
> {code:java}
> Wrong FS: 
> pfile:/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hive-bridge/target/partition-data-{dir},
>  expected: file:///
> {code}



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


[jira] [Resolved] (ATLAS-4040) Remove the result count field or update to N/A for TYPE_DEF_DELETE audit entry

2021-05-13 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-4040.

Resolution: Not A Bug

> Remove the result count field or update to N/A for TYPE_DEF_DELETE audit entry
> --
>
> Key: ATLAS-4040
> URL: https://issues.apache.org/jira/browse/ATLAS-4040
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> Delete call will always have result count as 1
> It will be good to remove the Result count field for this operation



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


[jira] [Resolved] (ATLAS-3763) Add "serviceType" in AtlasEntityHeader

2021-05-13 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-3763.

Resolution: Invalid

> Add "serviceType" in AtlasEntityHeader
> --
>
> Key: ATLAS-3763
> URL: https://issues.apache.org/jira/browse/ATLAS-3763
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Resolved] (ATLAS-3619) Allow to create a namespace typedef without specifying any "applicableEntityTypes"

2021-05-12 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-3619.

Resolution: Fixed

> Allow to create a namespace typedef without specifying any 
> "applicableEntityTypes"
> --
>
> Key: ATLAS-3619
> URL: https://issues.apache.org/jira/browse/ATLAS-3619
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Assigned] (ATLAS-4235) [Atlas: Audits] When business metadata attribute or user defined attribute of an entity is updated, action is appearing as "Entity updated" in v1 api response

2021-04-05 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4235:
--

Assignee: Mandar Ambawane

> [Atlas: Audits] When business metadata attribute or user defined attribute of 
> an entity is updated, action is appearing as "Entity updated" in v1 api 
> response
> --
>
> Key: ATLAS-4235
> URL: https://issues.apache.org/jira/browse/ATLAS-4235
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> Case 1:
> When business metadata attribute of an entity is updated, action is appearing 
> as "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
>  u'details': u'Updated business attributes: 
> {"typeName":"eibqk_bm","attributes":{"attrib_1":"111kezor","attrib_2":"222kezor"}}',
>  u'entityId': u'29068c0c-8573-4cf2-bddc-ddefd4d38281',
>  u'eventKey': 
> u'29068c0c-8573-4cf2-bddc-ddefd4d38281:1617296650400:0:1617296650414',
>  u'timestamp': 1617296650400,
>  u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated 
> business attributes*" but *action* displays "*ENTITY_UPDATE*"
> Case 2:
> When user-defined attribute  of an entity is updated, action is appearing as 
> "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
>  u'details': u'Updated custom attribute: 
> {"typeName":"entity_type_jmgur","guid":"a5770082-21b5-48ad-9540-0b2b7073359d","isIncomplete":false,"provenanceType":0,"version":0,"customAttributes":{"obtsv":"test
>  value 2","mjfid":"test value 3","qlomc":"test value 1"},"proxy":false}',
>  u'entityId': u'a5770082-21b5-48ad-9540-0b2b7073359d',
>  u'eventKey': 
> u'a5770082-21b5-48ad-9540-0b2b7073359d:1617297493442:0:1617297493450',
>  u'timestamp': 1617297493442,
>  u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated 
> custom attribute*" but *action* displays "*ENTITY_UPDATE*"
> *Minor:*
> Also it will be better if
> *"Updated custom attribute"* is updated as ** 
> *"**Updated custom attributes"* **
> Please not the 's' at the end to keep it consistent 



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


[jira] [Assigned] (ATLAS-4196) [Atlas: Audits] Audits are created for the (n-1) th operation in atlas while performing an insert operation

2021-03-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4196:
--

Assignee: Mandar Ambawane

> [Atlas: Audits] Audits are created for the (n-1) th operation in atlas while 
> performing an insert operation
> ---
>
> Key: ATLAS-4196
> URL: https://issues.apache.org/jira/browse/ATLAS-4196
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 11.26.45 AM.png, Screenshot 
> 2021-03-12 at 11.27.04 AM.png
>
>
> While inserting data into table, an audit entry is created but it displays 
> info of the n-1 th operation.
> Eg: When the first insert operation is performed with 3 rows of data, the 
> audit entry shows 0 rows .
> Now insert 2 more rows in 1 go, the audit data displays 3 rows instead of 5
> Latest audit and latest data in the tabled are shared
>  



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


[jira] [Assigned] (ATLAS-4195) [Atlas: Audits] 2 entries are created in audits when "replace columns" command is executed in hive

2021-03-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4195:
--

Assignee: Mandar Ambawane

> [Atlas: Audits] 2 entries are created in audits when "replace columns" 
> command is executed in hive
> --
>
> Key: ATLAS-4195
> URL: https://issues.apache.org/jira/browse/ATLAS-4195
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 10.31.13 AM.png
>
>
> While performing an update operation "replace columns" 2 entries are created 
> in atlas
> *Steps to repro:*
> {code:java}
> create table test_table_1(name string, eid int);
> alter table test_table_1 replace columns(ename string, eid int, dept string); 
> {code}
> 1 entry is created a hive user and the other entry is created as test user
> !Screenshot 2021-03-12 at 10.31.13 AM.png|width=671,height=166!
>  



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


[jira] [Assigned] (ATLAS-4197) [Atlas: Audits] [Regression] 2 entries are created while creating a new database in atlas audits

2021-03-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4197:
--

Assignee: Mandar Ambawane

> [Atlas: Audits] [Regression] 2 entries are created while creating a new 
> database in atlas audits
> 
>
> Key: ATLAS-4197
> URL: https://issues.apache.org/jira/browse/ATLAS-4197
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 11.43.19 AM.png
>
>
> Steps to repro:
> {code:java}
>  create database db_1;{code}
> Expecting 1 entry but 2 entries are created for the same
> 1 create audit as *hive* user and 1 update audit audit as *hrt_qa* user
> Looks like a possible regression of ATLAS-3360



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


[jira] [Assigned] (ATLAS-4199) [Atlas: Audits] 3 audit entries are created when a tables is created using ctas

2021-03-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4199:
--

Assignee: Mandar Ambawane

> [Atlas: Audits] 3 audit entries are created when a tables is created using 
> ctas
> ---
>
> Key: ATLAS-4199
> URL: https://issues.apache.org/jira/browse/ATLAS-4199
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 3.27.19 PM.png, Screenshot 
> 2021-03-12 at 3.34.25 PM.png
>
>
> *Steps to repro:*
>  # Create a table;
>  # Create a new table using ctas;
> {code:java}
> create table random_table;
> create table ctas_table as select * from random_table;{code}
>  
> *Expectation:*
> 1 audit entry for the creation of the new table and 1 audit for the 
> relationship with the old table
> *Current observation:*
>  * 3 audits are generated
>  * 1 audit as test user (hrt_qa)
>  * 2 audits as hive user



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


[jira] [Assigned] (ATLAS-4200) [Atlas: Audits] Relationship property is missing in the differential audit when the column name or column type is updated

2021-03-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4200:
--

Assignee: Mandar Ambawane

> [Atlas: Audits] Relationship property is missing in the differential audit 
> when the column name or column type is updated
> -
>
> Key: ATLAS-4200
> URL: https://issues.apache.org/jira/browse/ATLAS-4200
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 4.04.01 PM.png, Screenshot 
> 2021-03-12 at 4.10.33 PM.png
>
>
> When a column name or column type is updated, audit is created. When 
> differential audit is enabled only the modified part is updated in audit
> *atlas.entity.audit.differential=true*
> In this case the relationship property of the change is missing in the audit
> Added screenshots of the same



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


[jira] [Assigned] (ATLAS-4198) [Atlas: Audits][Regression] No audits should be created while inserting data into table

2021-03-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4198:
--

Assignee: Mandar Ambawane

> [Atlas: Audits][Regression] No audits should be created while inserting data 
> into table
> ---
>
> Key: ATLAS-4198
> URL: https://issues.apache.org/jira/browse/ATLAS-4198
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-03-12 at 12.42.50 PM.png
>
>
> As per ATLAS-3198, no audit entry should be created for insert operation. In 
> the latest code we are able to see audit entries for insert operation
> Steps to repro:
>  # Create a table
>  # Insert data into table
> *Create table:*
> {code:java}
> CREATE TABLE IF NOT EXISTS dharsh_test_1 ( eid int, name String, salary 
> String, designation String);{code}
> *Insert data into table:*
> {code:java}
> insert into dharsh_test_1 (eid, name, salary, designation)  values 
> (1001, "Gopal", "45000", "Technical manager"),
> (1002, "Manish", "45000", "Proof reader"), 
> (1003, "Masthanvali" , "4", "Technical writer"); {code}
> The above insert operation should not create any audit entry according to 
> ATLAS-3198,, but it now creates



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


[jira] [Resolved] (ATLAS-3597) Incorrect error message when attempting to update Namespacedef

2021-02-22 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-3597.

Resolution: Fixed

> Incorrect error message when attempting to update Namespacedef
> --
>
> Key: ATLAS-3597
> URL: https://issues.apache.org/jira/browse/ATLAS-3597
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> # Create a new namespaceDef:
>  
> {code:java}
> curl --location --request POST 
> 'http://localhost:21000/api/atlas/v2/types/typedefs' \
> --header 'Content-Type: application/json' \
> --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
> --data-raw '{
> "namespaceDefs": [
> {
> "name": "namespace1",
> "description": "Sample namespace1",
> "serviceType": "NAMESPACES",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "namespaceAttr1",
> "typeName": "string",
> "options": {
> "applicableEntityTypes": "[\"hive_db\", 
> \"hive_table\"]",
> "maxStrLength": "50"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> },
> {
> "name": "namespaceAttr2",
> "typeName": "int",
> "options": {
> "applicableEntityTypes": "[\"hive_db\", 
> \"hive_column\"]"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> }
> ]
> }
> ]
> }'{code}
>  
> 2. Update the namespaceDef to remove an entry from applicable entityTypes in 
> 'namespaceAttr1': 
>  
> {code:java}
> curl --location --request PUT 
> 'http://localhost:21000/api/atlas/v2/types/typedefs' \
> --header 'Content-Type: application/json' \
> --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
> --data-raw '{
> "namespaceDefs": [
> {
> "name": "namespace1",
> "description": "Sample namespace1",
> "serviceType": "NAMESPACES",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "namespaceAttr1",
> "typeName": "string",
> "options": {
> "applicableEntityTypes": "[\"hive_db\"]",
> "maxStrLength": "50"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> },
> {
> "name": "namespaceAttr2",
> "typeName": "int",
> "options": {
> "applicableEntityTypes": "[\"hive_db\", 
> \"hive_column\"]"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> }
> ]
> }
> ]
> }'{code}
>  
>  
> The following error message is thrown: 
>  
> {code:java}
> { "errorCode": "ATLAS-400-00-095", "errorMessage": "Cannot remove 
> applicableEntityTypes in Attribute Def: namespace1, defined in namespace: 
> {2}" }{code}
> error message should be: "Updating '*applicableEntityTypes*' in namespace: 
> \{namespace_name}, attribute: \{namespace_attribute} is not allowed."
>  
>  



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


[jira] [Resolved] (ATLAS-3534) EntityREST changes to allow namespace attributes to be added to an entity instance

2021-02-22 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-3534.

Resolution: Fixed

> EntityREST changes to allow namespace attributes to be added to an entity 
> instance
> --
>
> Key: ATLAS-3534
> URL: https://issues.apache.org/jira/browse/ATLAS-3534
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Aadarsh Jajodia
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Assigned] (ATLAS-4139) [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided in key:value format, the error message does not convey that

2021-02-10 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4139:
--

Assignee: Mandar Ambawane

> [Atlas: Glossary Term Bulk Import] When AdditionalAttributes is not provided 
> in key:value format, the error message does not convey that
> 
>
> Key: ATLAS-4139
> URL: https://issues.apache.org/jira/browse/ATLAS-4139
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-02-05 at 4.07.46 PM.png
>
>
> Consider the following input for bulk import term_glossary
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples, 
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, 
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, 
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> glossary_1,term_1, "glossary_1 term_1 short description", "glossary_1 term_1 
> long description", "Examples", "AB", "glossary_1 term_1 Usage", "random_key"
>  {code}
> Here *AdditionalAttributes* is *random_key*
> When this is imported we get
> {code:java}
> errorCode: "ATLAS-500-00-001"errorMessage: "The uploaded file has not been 
> processed due to the following errors : ↵[↵The Data in the uploaded file is 
> incorrectly specified  : random_key]" {code}
> It mentions The Data in the uploaded file is incorrectly specified : 
> random_key
> It would be good to convey as "AdditionalAttributes has to a key:value pair" 
> or something similar



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


[jira] [Updated] (ATLAS-4146) [Atlas: Glossary] On updating the related terms, UI allows the user to add the already added term

2021-02-10 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4146:
---
Component/s:  atlas-core

> [Atlas: Glossary] On updating the related terms, UI allows the user to add 
> the already added term
> -
>
> Key: ATLAS-4146
> URL: https://issues.apache.org/jira/browse/ATLAS-4146
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screen Recording 2021-02-05 at 6.50.31 PM.mov
>
>
> Steps to repro:
>  # Create a glossary(glossary_1) and a few terms (term_1, term_2, term_3, 
> term_4, term_5)
>  # Click on term_1 and add related terms "alsoSee"
>  # Choose term_5 of glossary_1
>  # Provide inputs and assign
>  # term_5 will be added as a related term
>  # Now, add one more related term and choose the same term_5 of glossary_1 
> [UI allows this]
>  # Provide new input and assign
>  # The assignment will be successful
> This makes the user think, that term_5 with new data is saved. But that is 
> not the case, only old data is present
> Expectation:
> Do not allow the user to assign the same term again.
> If allowed, update the data with the new data
> [^Screen Recording 2021-02-05 at 6.50.31 PM.mov]



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


[jira] [Assigned] (ATLAS-4146) [Atlas: Glossary] On updating the related terms, UI allows the user to add the already added term

2021-02-10 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4146:
--

Assignee: Mandar Ambawane

> [Atlas: Glossary] On updating the related terms, UI allows the user to add 
> the already added term
> -
>
> Key: ATLAS-4146
> URL: https://issues.apache.org/jira/browse/ATLAS-4146
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screen Recording 2021-02-05 at 6.50.31 PM.mov
>
>
> Steps to repro:
>  # Create a glossary(glossary_1) and a few terms (term_1, term_2, term_3, 
> term_4, term_5)
>  # Click on term_1 and add related terms "alsoSee"
>  # Choose term_5 of glossary_1
>  # Provide inputs and assign
>  # term_5 will be added as a related term
>  # Now, add one more related term and choose the same term_5 of glossary_1 
> [UI allows this]
>  # Provide new input and assign
>  # The assignment will be successful
> This makes the user think, that term_5 with new data is saved. But that is 
> not the case, only old data is present
> Expectation:
> Do not allow the user to assign the same term again.
> If allowed, update the data with the new data
> [^Screen Recording 2021-02-05 at 6.50.31 PM.mov]



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


[jira] [Assigned] (ATLAS-4135) [Atlas: Glossary Term Bulk Import] It will be good to ignore the glossaries and terms that are already present instead of failing the bulk import

2021-02-09 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4135:
--

Assignee: Mandar Ambawane

> [Atlas: Glossary Term Bulk Import] It will be good to ignore the glossaries 
> and terms that are already present instead of failing the bulk import
> -
>
> Key: ATLAS-4135
> URL: https://issues.apache.org/jira/browse/ATLAS-4135
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2021-02-04 at 7.06.56 PM.png
>
>
> Consider the following scenario:
> Already available glossaries and terms:
> glossary_1 ==> term_1
> glossary_1 ==> term_2
> glossary_2 ==> term_1
> glossary_2 ==> term_2
>  
> Now if the user is performing a bulk import and if glossary_1 ==> term_1 is 
> part of the input, currently the call fails.
> {code:java}
> {errorCode: "ATLAS-500-00-016", errorMessage: "Error occurred while creating 
> glossary term: {0}",…}errorCause: "Glossary term with qualifiedName 
> term_1@aglossary_01 already exists"errorCode: "ATLAS-500-00-016"errorMessage: 
> "Error occurred while creating glossary term: {0}" {code}
> Expectation:
> If it already exists, then just update the other field values eg, long 
> description and the linked terms and do not fail
>  



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


[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

2021-02-08 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4124:
---
Description: 
We can delete the entire BusinessMetadata TypeDef using the curl command.

But that will affect the entities which already have Business Attributes from 
this Deleted Business Metadata.
Those Business Attributes will be removed from the Entity.

This patch will restrict user from deleting Business Metadata, if Business 
Metadata is already associated with an entity.

> Restrict user from deleting Business Metadata, if Business Metadata is 
> already associated with an entity
> 
>
> Key: ATLAS-4124
> URL: https://issues.apache.org/jira/browse/ATLAS-4124
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>  Labels: BusinessMetadata
> Attachments: ATLAS-4124.patch
>
>
> We can delete the entire BusinessMetadata TypeDef using the curl command.
> But that will affect the entities which already have Business Attributes from 
> this Deleted Business Metadata.
> Those Business Attributes will be removed from the Entity.
> This patch will restrict user from deleting Business Metadata, if Business 
> Metadata is already associated with an entity.



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


[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

2021-02-08 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4124:
---
Fix Version/s: 3.0.0

> Restrict user from deleting Business Metadata, if Business Metadata is 
> already associated with an entity
> 
>
> Key: ATLAS-4124
> URL: https://issues.apache.org/jira/browse/ATLAS-4124
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>  Labels: BusinessMetadata
> Fix For: 3.0.0
>
> Attachments: ATLAS-4124.patch
>
>
> We can delete the entire BusinessMetadata TypeDef using the curl command.
> But that will affect the entities which already have Business Attributes from 
> this Deleted Business Metadata.
> Those Business Attributes will be removed from the Entity.
> This patch will restrict user from deleting Business Metadata, if Business 
> Metadata is already associated with an entity.



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


[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

2021-02-08 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4124:
---
Labels: BusinessMetadata  (was: )

> Restrict user from deleting Business Metadata, if Business Metadata is 
> already associated with an entity
> 
>
> Key: ATLAS-4124
> URL: https://issues.apache.org/jira/browse/ATLAS-4124
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>  Labels: BusinessMetadata
> Attachments: ATLAS-4124.patch
>
>




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


[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

2021-02-08 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4124:
---
Affects Version/s: 2.1.0

> Restrict user from deleting Business Metadata, if Business Metadata is 
> already associated with an entity
> 
>
> Key: ATLAS-4124
> URL: https://issues.apache.org/jira/browse/ATLAS-4124
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4124.patch
>
>




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


[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

2021-02-08 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4124:
---
Component/s:  atlas-core

> Restrict user from deleting Business Metadata, if Business Metadata is 
> already associated with an entity
> 
>
> Key: ATLAS-4124
> URL: https://issues.apache.org/jira/browse/ATLAS-4124
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4124.patch
>
>




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


[jira] [Updated] (ATLAS-4124) Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

2021-02-04 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4124:
---
Summary: Restrict user from deleting Business Metadata, if Business 
Metadata is already associated with an entity  (was: Prevent user from deleting 
Business Metadata, if Business Metadata is already associated with an entity)

> Restrict user from deleting Business Metadata, if Business Metadata is 
> already associated with an entity
> 
>
> Key: ATLAS-4124
> URL: https://issues.apache.org/jira/browse/ATLAS-4124
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Created] (ATLAS-4124) Prevent user from deleting Business Metadata, if Business Metadata is already associated with an entity

2021-02-03 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-4124:
--

 Summary: Prevent user from deleting Business Metadata, if Business 
Metadata is already associated with an entity
 Key: ATLAS-4124
 URL: https://issues.apache.org/jira/browse/ATLAS-4124
 Project: Atlas
  Issue Type: Improvement
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane






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


[jira] [Commented] (ATLAS-4105) table details are set to null for a dropped hbase_column_family

2021-01-25 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane commented on ATLAS-4105:


Hi [~umesh.padashetty],

This is the behavior as per the code written for the *Legacy Attributes*.

The code flow goes like this:

While retrieving the *DELETED* "*hbase_column_family*" entity, 
Relationship Attributes are set in method 
*EntityGraphRetriever.mapVertexToRelationshipAttribute()*
In the same method there is one check for the Legacy Attribute.

 
{code:java}
if (attributeEndDef.getIsLegacyAttribute() && 
!entity.hasAttribute(attributeName)) { 
          entity.setAttribute(attributeName, toLegacyAttribute(ret));       
 
}{code}
 


If the current Relationship Attribute is Legacy Attribute then it is also set 
as Normal Attribute in the Entity.      

In this case, "*hbase_table*" is the Legacy Attribute.    

While setting this as Normal Attribute,
In method *EntityGraphRetriever.toLegacyAttribute(AtlasRelatedObjectId 
relatedObjId)*   There is one check.
{code:java}
if (relatedObjId.getRelationshipStatus() == DELETED 
&& relatedObjId.getEntityStatus() == AtlasEntity.Status.ACTIVE) {  
          ret = null;        
}{code}
 


While setting the Relationship Attribute for hbase_column_family, when 
"*hbase_table*" comes at this check, both the conditions get satisfied. 
 # The relationship between "*hbase_table*" and "*hbase_column_family*" is 
deleted when we delete the "*hbase_column_family*".
 # The entity "*hbase_table*" is still "*ACTIVE*".



And hence the value is set as *NULL* for the Normal Attribute "*table*" of an 
entity "*hbase_column_family*"    

Therefore, for the DELETED "hbase_column_family" entity, the Normal Attribute 
"table" is set to NULL and we are not able to see it.

CC: [~sarath] [~nixon] [~jayendrap]

> table details are set to null for a dropped hbase_column_family
> ---
>
> Key: ATLAS-4105
> URL: https://issues.apache.org/jira/browse/ATLAS-4105
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Umesh Padashetty
>Assignee: Mandar Ambawane
>Priority: Minor
> Attachments: Screenshot 2021-01-20 at 12.19.22 AM.png, Screenshot 
> 2021-01-20 at 12.21.50 AM.png, Screenshot 2021-01-20 at 12.22.01 AM.png
>
>
> Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE 
> whereas col_fam_kpgfu_1 is DELETED.
> On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is 
> ACTIVE, the table info is set to hbase_table_endlu
> whereas for col_fam_kpgfu_1 which is DELETED, it is set to N/A (UI displays 
> null values as N/A)



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


[jira] [Assigned] (ATLAS-4105) table details are set to null for a dropped hbase_column_family

2021-01-19 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4105:
--

Assignee: Mandar Ambawane

> table details are set to null for a dropped hbase_column_family
> ---
>
> Key: ATLAS-4105
> URL: https://issues.apache.org/jira/browse/ATLAS-4105
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Umesh Padashetty
>Assignee: Mandar Ambawane
>Priority: Minor
> Attachments: Screenshot 2021-01-20 at 12.19.22 AM.png, Screenshot 
> 2021-01-20 at 12.21.50 AM.png, Screenshot 2021-01-20 at 12.22.01 AM.png
>
>
> Table hbase_table_endlu has 2 column families, col_fam_kpgfu_2 is ACTIVE 
> whereas col_fam_kpgfu_1 is DELETED.
> On clicking the entities, it can be seen that for col_fam_kpgfu_2 which is 
> ACTIVE, the table info is set to hbase_table_endlu
> whereas for col_fam_kpgfu_1 which is DELETED, it is set to N/A (UI displays 
> null values as N/A)



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


[jira] [Assigned] (ATLAS-4103) While listing Purge operation records in Administration-Audits, shows 'Something went wrong' message

2021-01-14 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4103:
--

Assignee: Mandar Ambawane

> While listing Purge operation records in Administration-Audits, shows 
> 'Something went wrong' message
> 
>
> Key: ATLAS-4103
> URL: https://issues.apache.org/jira/browse/ATLAS-4103
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Something_went_wrong_for_purge_operation_listing.png
>
>
> Steps to Reproduce ::
>  # Soft delete/Purge any entity (purged through postman)
>  # Go to Administration-Audits tab to see the above record
>  # In Filter select Operation(atlas_operation)=Purge
> Expected: The deleted entity details should have listed
> Actual: Shows 'Something went wrong' message on UI and console shows '500 
> Internal Server Error'



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


[jira] [Updated] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api

2021-01-06 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4092:
---
Attachment: ATLAS-4092.patch

> Remove unused attributes and add right attributes to the atlas admin audit api
> --
>
> Key: ATLAS-4092
> URL: https://issues.apache.org/jira/browse/ATLAS-4092
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4092.patch
>
>
> {code:java|title=Sample payload:}
> {
>   "currentPage": "page",
>   "pageSize": "per_page",
>   "totalPages": "total_pages",
>   "totalRecords": "total_entries",
>   "sortKey": "sort_by",
>   "order": "order",
>   "directions": {
> "1": "desc",
> "-1": "asc"
>   },
>   "auditFilters": {
> "condition": "AND",
> "criterion": [
>   {
> "attributeName": "operation",
> "operator": "eq",
> "attributeValue": "TYPE_DEF_CREATE"
>   }
> ]
>   },
>   "limit": 25,
>   "offset": 0
> }
> {code}
> Here the following attributes do not work:
> {code}
> "sortKey": "sort_by",
> "order": "order",
> {code}
> Instead the following works
> {code}
> "sortBy" : "startTime",
> "sortOrder" : "DESCENDING",
> {code}
> sortKey and order has to be removed and sortBy and sortOrder has to be added



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


[jira] [Updated] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api

2021-01-06 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4092:
---
Attachment: (was: ATLAS-4092.patch)

> Remove unused attributes and add right attributes to the atlas admin audit api
> --
>
> Key: ATLAS-4092
> URL: https://issues.apache.org/jira/browse/ATLAS-4092
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> {code:java|title=Sample payload:}
> {
>   "currentPage": "page",
>   "pageSize": "per_page",
>   "totalPages": "total_pages",
>   "totalRecords": "total_entries",
>   "sortKey": "sort_by",
>   "order": "order",
>   "directions": {
> "1": "desc",
> "-1": "asc"
>   },
>   "auditFilters": {
> "condition": "AND",
> "criterion": [
>   {
> "attributeName": "operation",
> "operator": "eq",
> "attributeValue": "TYPE_DEF_CREATE"
>   }
> ]
>   },
>   "limit": 25,
>   "offset": 0
> }
> {code}
> Here the following attributes do not work:
> {code}
> "sortKey": "sort_by",
> "order": "order",
> {code}
> Instead the following works
> {code}
> "sortBy" : "startTime",
> "sortOrder" : "DESCENDING",
> {code}
> sortKey and order has to be removed and sortBy and sortOrder has to be added



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


[jira] [Created] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api

2021-01-05 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-4092:
--

 Summary: Remove unused attributes and add right attributes to the 
atlas admin audit api
 Key: ATLAS-4092
 URL: https://issues.apache.org/jira/browse/ATLAS-4092
 Project: Atlas
  Issue Type: Improvement
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane


{code:java|title=Sample payload:}
{
  "currentPage": "page",
  "pageSize": "per_page",
  "totalPages": "total_pages",
  "totalRecords": "total_entries",
  "sortKey": "sort_by",
  "order": "order",
  "directions": {
"1": "desc",
"-1": "asc"
  },
  "auditFilters": {
"condition": "AND",
"criterion": [
  {
"attributeName": "operation",
"operator": "eq",
"attributeValue": "TYPE_DEF_CREATE"
  }
]
  },
  "limit": 25,
  "offset": 0
}
{code}
Here the following attributes do not work:
{code}
"sortKey": "sort_by",
"order": "order",
{code}

Instead the following works
{code}
"sortBy" : "startTime",
"sortOrder" : "DESCENDING",
{code}

sortKey and order has to be removed and sortBy and sortOrder has to be added



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


[jira] [Assigned] (ATLAS-4070) hive_column_lineage .json and impala_column_lineage .json files are missing in /admin/export zip file

2020-12-09 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4070:
--

Assignee: Mandar Ambawane

> 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
>Assignee: Mandar Ambawane
>Priority: Major
>
> 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] [Assigned] (ATLAS-4069) Export/Importing a recreated deleted entity has the relationshipStatus set to ACTIVE instead of DELETED for deleted entity

2020-12-09 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4069:
--

Assignee: Mandar Ambawane  (was: Ashutosh Mestry)

> 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: Mandar Ambawane
>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] [Updated] (ATLAS-4065) TYPE_DEF_UPDATE audit does not reflect the right values

2020-12-08 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4065:
---
Attachment: ATLAS-4065.patch

> TYPE_DEF_UPDATE audit does not reflect the right values
> ---
>
> Key: ATLAS-4065
> URL: https://issues.apache.org/jira/browse/ATLAS-4065
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4065.patch
>
>
> 1) Create a type as user_1 and update it as user_2
> The update audit should reflects user_2 in the update audit
> userName field reflects the right value but the result field displays the 
> incorrect value
> 2) There is a mismatch in the Version



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


[jira] [Assigned] (ATLAS-4065) TYPE_DEF_UPDATE audit does not reflect the right values

2020-12-07 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4065:
--

Assignee: Mandar Ambawane

> TYPE_DEF_UPDATE audit does not reflect the right values
> ---
>
> Key: ATLAS-4065
> URL: https://issues.apache.org/jira/browse/ATLAS-4065
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> 1) Create a type as user_1 and update it as user_2
> The update audit should reflects user_2 in the update audit
> userName field reflects the right value but the result field displays the 
> incorrect value
> 2) There is a mismatch in the Version



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


[jira] [Comment Edited] (ATLAS-4047) Audits Framework: Handling Long List

2020-11-24 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane edited comment on ATLAS-4047 at 11/25/20, 3:46 AM:
---

Hi [~amestry]
We have addressed this issue in [#https://reviews.apache.org/r/72903/]


was (Author: mandar_va):
Hi [~amestry]
We have addressed this issue in [#https://reviews.apache.org/r/72903/]

> Audits Framework: Handling Long List
> 
>
> Key: ATLAS-4047
> URL: https://issues.apache.org/jira/browse/ATLAS-4047
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-4047-AtlasAuditService-Handling-large-strings.patch
>
>
> *Background*
> Existing _AtlasAuditService_ implementation, accepts list of GUIDs (object 
> ids) and attempts to store it in a vertex.
> *Steps to Duplicate*
> Setup:
>  * Create an export payload with 50 tables each with about 50 columns.
> Steps to duplicate:
>  * Attempt to import. Import succeeds.
> Expected result: Import completes successfully.
> Actual result: Following exception is seen within the log, import returns and 
> error code:
> {code:java}
> at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:177)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:177)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:116)
>  at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
>  at 
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$f28200fc.createOrUpdate()
>  at org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:73) 
> at 
> org.apache.atlas.repository.audit.AtlasAuditService.save(AtlasAuditService.java:62)
>  at 
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:82)
>  at 
> org.apache.atlas.repository.audit.AtlasAuditService$$FastClassBySpringCGLIB$$2eddda47.invoke()
>  at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204){code}
>  CC: [~mandar.ambaw...@freestoneinfotech.com]



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


[jira] [Commented] (ATLAS-4047) Audits Framework: Handling Long List

2020-11-24 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane commented on ATLAS-4047:


Hi [~amestry]
We have addressed this issue in [#https://reviews.apache.org/r/72903/]

> Audits Framework: Handling Long List
> 
>
> Key: ATLAS-4047
> URL: https://issues.apache.org/jira/browse/ATLAS-4047
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-4047-AtlasAuditService-Handling-large-strings.patch
>
>
> *Background*
> Existing _AtlasAuditService_ implementation, accepts list of GUIDs (object 
> ids) and attempts to store it in a vertex.
> *Steps to Duplicate*
> Setup:
>  * Create an export payload with 50 tables each with about 50 columns.
> Steps to duplicate:
>  * Attempt to import. Import succeeds.
> Expected result: Import completes successfully.
> Actual result: Following exception is seen within the log, import returns and 
> error code:
> {code:java}
> at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:177)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.doCommitOrRollback(GraphTransactionInterceptor.java:177)
>  at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:116)
>  at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
>  at 
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$f28200fc.createOrUpdate()
>  at org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:73) 
> at 
> org.apache.atlas.repository.audit.AtlasAuditService.save(AtlasAuditService.java:62)
>  at 
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:82)
>  at 
> org.apache.atlas.repository.audit.AtlasAuditService$$FastClassBySpringCGLIB$$2eddda47.invoke()
>  at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204){code}
>  CC: [~mandar.ambaw...@freestoneinfotech.com]



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


[jira] [Updated] (ATLAS-4041) It will be good to have the operation status info of EXPORT operation in the Admin export audits

2020-11-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4041:
---
Attachment: ATLAS-4034-ATLAS-4041.patch

> It will be good to have the operation status info of EXPORT operation in the 
> Admin export audits
> 
>
> Key: ATLAS-4041
> URL: https://issues.apache.org/jira/browse/ATLAS-4041
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4034-ATLAS-4041.patch
>
>
> Currently we do not have information if the export operation is "PASS" or 
> "FAIL" or "PARTIAL_PASS"
> It will be good to have this information
> Current output:
> {code}
>  {
>  "guid": "",
>  "userName": "",
>  "operation": "EXPORT",
>  "params": "\{\"fetchType\":\"FULL\",\"matchType\":\"startsWith\"}",
>  "startTime": 1605089955917,
>  "endTime": 1605089957959,
>  "clientId": "",
>  "result": "\{\"hdfs_path\":1,\"dharshana\":1,\"hive_db\":1}",
>  "resultCount": 3
>  }
> {code}



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


[jira] [Updated] (ATLAS-4034) Export operation audit with result count 0 for empty exports is inconsistent

2020-11-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4034:
---
Attachment: ATLAS-4034-ATLAS-4041.patch

> Export operation audit with result count 0 for empty exports is inconsistent
> 
>
> Key: ATLAS-4034
> URL: https://issues.apache.org/jira/browse/ATLAS-4034
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4034-ATLAS-4041.patch
>
>
> Export operation creates an audit with *count 0* for the following request:
> {code:java}
> {
>  "itemsToExport": [
>  
>  ]
> }
> {code}
> But the following input does not create any audit entry : Please note the 
> *{}* in the *itemsToExport* array
> {code:java}
> {
>  "itemsToExport": [
>    {}
>  ]
> }
>  {code}
> We need to keep the result consistent. Either create entry for the later with 
> result count 0 or do not create an entry for the former



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


[jira] [Assigned] (ATLAS-4034) Export operation audit with result count 0 for empty exports is inconsistent

2020-11-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4034:
--

Assignee: Mandar Ambawane

> Export operation audit with result count 0 for empty exports is inconsistent
> 
>
> Key: ATLAS-4034
> URL: https://issues.apache.org/jira/browse/ATLAS-4034
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> Export operation creates an audit with *count 0* for the following request:
> {code:java}
> {
>  "itemsToExport": [
>  
>  ]
> }
> {code}
> But the following input does not create any audit entry : Please note the 
> *{}* in the *itemsToExport* array
> {code:java}
> {
>  "itemsToExport": [
>    {}
>  ]
> }
>  {code}
> We need to keep the result consistent. Either create entry for the later with 
> result count 0 or do not create an entry for the former



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


[jira] [Assigned] (ATLAS-4041) It will be good to have the operation status info of EXPORT operation in the Admin export audits

2020-11-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4041:
--

Assignee: Mandar Ambawane  (was: Deep Singh)

> It will be good to have the operation status info of EXPORT operation in the 
> Admin export audits
> 
>
> Key: ATLAS-4041
> URL: https://issues.apache.org/jira/browse/ATLAS-4041
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently we do not have information if the export operation is "PASS" or 
> "FAIL" or "PARTIAL_PASS"
> It will be good to have this information
> Current output:
> {code}
>  {
>  "guid": "",
>  "userName": "",
>  "operation": "EXPORT",
>  "params": "\{\"fetchType\":\"FULL\",\"matchType\":\"startsWith\"}",
>  "startTime": 1605089955917,
>  "endTime": 1605089957959,
>  "clientId": "",
>  "result": "\{\"hdfs_path\":1,\"dharshana\":1,\"hive_db\":1}",
>  "resultCount": 3
>  }
> {code}



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


[jira] [Updated] (ATLAS-4032) Filter group option in the Admin Audit tab is not giving the expected output

2020-11-19 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4032:
---
Attachment: ATLAS-4032.patch

> Filter group option in the Admin Audit tab is not giving the expected output
> 
>
> Key: ATLAS-4032
> URL: https://issues.apache.org/jira/browse/ATLAS-4032
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4032.patch, image-2020-11-18-14-05-05-000.png
>
>
> When we filter results using filter groups, the output received is the output 
> of the first group
> Criteria used:
> !image-2020-11-18-14-05-05-000.png|width=558,height=159!
> Expected output:
> The audits of operation that are either SERVER_START or SERVER_STATE_ACTIVE
>  
> Observed Output:
> The audits of SERVER_START operation 
>  



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


[jira] [Updated] (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-11-12 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3813:
---
Attachment: ATLAS-3813-V4.patch

> 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
> Attachments: ATLAS-3813-V4.patch
>
>
> 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] [Updated] (ATLAS-4016) Update authorization - "admin-audits" for retrieving admin audits

2020-11-11 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4016:
---
Attachment: ATLAS-4016-V2.patch

> Update authorization - "admin-audits" for retrieving admin audits
> -
>
> Key: ATLAS-4016
> URL: https://issues.apache.org/jira/browse/ATLAS-4016
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4016-V2.patch, ATLAS-4016.patch
>
>
>  
>   
>  For Atlas Admin Audits we need to add new privilege - "*admin-audits*"  for 
> authorization
> Similar permission needs to be updated in ranger atlas service-def .



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


[jira] [Updated] (ATLAS-4016) Update authorization - "admin-audits" for retrieving admin audits

2020-11-09 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-4016:
---
Attachment: ATLAS-4016.patch

> Update authorization - "admin-audits" for retrieving admin audits
> -
>
> Key: ATLAS-4016
> URL: https://issues.apache.org/jira/browse/ATLAS-4016
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4016.patch
>
>
>  
>   
>  For Atlas Admin Audits we need to add new privilege - "*admin-audits*"  for 
> authorization
> Similar permission needs to be updated in ranger atlas service-def .



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


[jira] [Assigned] (ATLAS-4016) Update authorization - "admin-audits" for retrieving admin audits

2020-11-09 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-4016:
--

Assignee: Mandar Ambawane

> Update authorization - "admin-audits" for retrieving admin audits
> -
>
> Key: ATLAS-4016
> URL: https://issues.apache.org/jira/browse/ATLAS-4016
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Mandar Ambawane
>Priority: Major
>
>  
>   
>  For Atlas Admin Audits we need to add new privilege - "*admin-audits*"  for 
> authorization
> Similar permission needs to be updated in ranger atlas service-def .



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


[jira] [Resolved] (ATLAS-3935) Use Audit framework to capture audit entries for Import/Export operations

2020-10-26 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane resolved ATLAS-3935.

Resolution: Fixed

> Use Audit framework to capture audit entries for Import/Export operations
> -
>
> Key: ATLAS-3935
> URL: https://issues.apache.org/jira/browse/ATLAS-3935
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-3935-V2.patch, ATLAS-3935-V3.patch
>
>
> By using Audit Framework, capture audit entries for Import/Export operations.
> These audit entries can be seen under the "Audits" tab of Admin section.
> *Add Import and Export specific information in Audit entry*
> * Total no. of entities imported/ exported
> * Total no. of entities imported/ exported of specific TypeDef
> * Export operation Fetch Type



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


[jira] [Commented] (ATLAS-3943) UI: Show Import/Export operations in administration audit.

2020-10-26 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane commented on ATLAS-3943:


+1 for the patch

> UI: Show Import/Export operations in administration audit.
> --
>
> Key: ATLAS-3943
> URL: https://issues.apache.org/jira/browse/ATLAS-3943
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3943-1.patch, ATLAS-3943-2.patch, 
> ATLAS-3943-3.patch, ATLAS-3943-4.patch, ATLAS-3943.patch
>
>




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


[jira] [Updated] (ATLAS-3957) Use Audit framework to capture audit entries for "Server Start" and "Server In Active mode" (HA)

2020-10-16 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3957:
---
Attachment: ATLAS-3957-V3.patch

> Use Audit framework to capture audit entries for "Server Start" and "Server 
> In Active mode" (HA)
> 
>
> Key: ATLAS-3957
> URL: https://issues.apache.org/jira/browse/ATLAS-3957
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-3957-V3.patch, ATLAS-3957.patch
>
>
> By using Audit Framework, capture audit entries for "Server Start" and 
> "Server In Active mode" (HA)
> These audit entries can be seen under the "Audits" tab of Admin section.



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


[jira] [Updated] (ATLAS-3935) Use Audit framework to capture audit entries for Import/Export operations

2020-10-16 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3935:
---
Attachment: ATLAS-3935-V3.patch

> Use Audit framework to capture audit entries for Import/Export operations
> -
>
> Key: ATLAS-3935
> URL: https://issues.apache.org/jira/browse/ATLAS-3935
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-3935-V2.patch, ATLAS-3935-V3.patch
>
>
> By using Audit Framework, capture audit entries for Import/Export operations.
> These audit entries can be seen under the "Audits" tab of Admin section.
> *Add Import and Export specific information in Audit entry*
> * Total no. of entities imported/ exported
> * Total no. of entities imported/ exported of specific TypeDef
> * Export operation Fetch Type



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


[jira] [Updated] (ATLAS-3935) Use Audit framework to capture audit entries for Import/Export operations

2020-10-16 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3935:
---
Attachment: ATLAS-3935-V2.patch

> Use Audit framework to capture audit entries for Import/Export operations
> -
>
> Key: ATLAS-3935
> URL: https://issues.apache.org/jira/browse/ATLAS-3935
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-3935-V2.patch
>
>
> By using Audit Framework, capture audit entries for Import/Export operations.
> These audit entries can be seen under the "Audits" tab of Admin section.
> *Add Import and Export specific information in Audit entry*
> * Total no. of entities imported/ exported
> * Total no. of entities imported/ exported of specific TypeDef
> * Export operation Fetch Type



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


[jira] [Updated] (ATLAS-3984) Add UI Date Timezone and UI Date Format in Session api

2020-10-16 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3984:
---
Attachment: ATLAS-3984-V2.patch

> Add UI Date Timezone and UI Date Format in Session api
> --
>
> Key: ATLAS-3984
> URL: https://issues.apache.org/jira/browse/ATLAS-3984
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-3984-V2.patch
>
>
> Add UI Date Timezone and UI Date Format in Session api.
> Provide a way to user to read these "UI Date Timezone" and "UI Date Format" 
> values from property file.



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


[jira] [Comment Edited] (ATLAS-3986) UI Allow user to update the date format from JAVA property file

2020-10-14 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane edited comment on ATLAS-3986 at 10/14/20, 2:40 PM:
---

+1 for the patch


was (Author: mandar_va):
+1

> UI Allow user to update the date format from JAVA property file
> ---
>
> Key: ATLAS-3986
> URL: https://issues.apache.org/jira/browse/ATLAS-3986
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3986.patch
>
>




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


[jira] [Commented] (ATLAS-3986) UI Allow user to update the date format from JAVA property file

2020-10-14 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane commented on ATLAS-3986:


+1

> UI Allow user to update the date format from JAVA property file
> ---
>
> Key: ATLAS-3986
> URL: https://issues.apache.org/jira/browse/ATLAS-3986
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3986.patch
>
>




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


[jira] [Created] (ATLAS-3984) Add UI Date Timezone and UI Date Format in Session api

2020-10-07 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3984:
--

 Summary: Add UI Date Timezone and UI Date Format in Session api
 Key: ATLAS-3984
 URL: https://issues.apache.org/jira/browse/ATLAS-3984
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane


Add UI Date Timezone and UI Date Format in Session api.

Provide a way to user to read these "UI Date Timezone" and "UI Date Format" 
values from property file.



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


[jira] [Updated] (ATLAS-3957) Use Audit framework to capture audit entries for "Server Start" and "Server In Active mode" (HA)

2020-09-28 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3957:
---
Attachment: ATLAS-3957.patch

> Use Audit framework to capture audit entries for "Server Start" and "Server 
> In Active mode" (HA)
> 
>
> Key: ATLAS-3957
> URL: https://issues.apache.org/jira/browse/ATLAS-3957
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-3957.patch
>
>
> By using Audit Framework, capture audit entries for "Server Start" and 
> "Server In Active mode" (HA)
> These audit entries can be seen under the "Audits" tab of Admin section.



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


[jira] [Created] (ATLAS-3957) Use Audit framework to capture audit entries for "Server Start" and "Server In Active mode" (HA)

2020-09-24 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3957:
--

 Summary: Use Audit framework to capture audit entries for "Server 
Start" and "Server In Active mode" (HA)
 Key: ATLAS-3957
 URL: https://issues.apache.org/jira/browse/ATLAS-3957
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane


By using Audit Framework, capture audit entries for "Server Start" and "Server 
In Active mode" (HA)

These audit entries can be seen under the "Audits" tab of Admin section.



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


[jira] [Created] (ATLAS-3937) Add Test Cases for Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-09-09 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3937:
--

 Summary: Add Test Cases for Audit framework to generate audit 
entries for TypeDefs CREATE, UPDATE and DELETE
 Key: ATLAS-3937
 URL: https://issues.apache.org/jira/browse/ATLAS-3937
 Project: Atlas
  Issue Type: Test
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane






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


[jira] [Created] (ATLAS-3935) Use Audit framework to capture audit entries for Import/Export operations

2020-08-31 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3935:
--

 Summary: Use Audit framework to capture audit entries for 
Import/Export operations
 Key: ATLAS-3935
 URL: https://issues.apache.org/jira/browse/ATLAS-3935
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane


By using Audit Framework, capture audit entries for Import/Export operations.

These audit entries can be seen under the "Audits" tab of Admin section.

*Add Import and Export specific information in Audit entry*
* Total no. of entities imported/ exported
* Total no. of entities imported/ exported of specific TypeDef
* Export operation Fetch Type



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


[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-08-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3583:
---
Description: 
By using Audit Framework, capture audit entries when Type defs are created/ 
updated/ deleted.

These audit entries can be seen under the "Audits" tab of Admin section.

If there are mutiple Typedefs created/ updated/ deleted in a single request, 
Then only one audit entry will be recorded. 
This audit entry will consist of entire information about all the included 
Typedefs.

> Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and 
> DELETE
> 
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3583-V3.patch, ATLAS-3583-V8.patch
>
>
> By using Audit Framework, capture audit entries when Type defs are created/ 
> updated/ deleted.
> These audit entries can be seen under the "Audits" tab of Admin section.
> If there are mutiple Typedefs created/ updated/ deleted in a single request, 
> Then only one audit entry will be recorded. 
> This audit entry will consist of entire information about all the included 
> Typedefs.



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


[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-08-14 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3583:
---
Attachment: ATLAS-3583-V8.patch

> Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and 
> DELETE
> 
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3583-V3.patch, ATLAS-3583-V8.patch
>
>




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


[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-07-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3583:
---
Attachment: ATLAS-3583-V3.patch

> Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and 
> DELETE
> 
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3583-V3.patch
>
>




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


[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-07-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3583:
---
Attachment: (was: ATLAS-3583-V3.patch)

> Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and 
> DELETE
> 
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0
>
>




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


[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-07-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3583:
---
Attachment: ATLAS-3583-V3.patch

> Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and 
> DELETE
> 
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3583-V3.patch
>
>




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


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

2020-07-16 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-3738:
--

Assignee: Mandar Ambawane

> [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
>Assignee: Mandar Ambawane
>Priority: Critical
> 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] [Updated] (ATLAS-3841) Response Headers: Code refactoring

2020-07-07 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3841:
---
Description: (was: Currently headers setting code is scattered at 
different places.
In this patch, code refactoring is done to set response headers from 
AtlasHeaderFilter.java

This patch provides flexibility to select response headers to be excluded.
Also this patch provides flexibility to select file formats to be excluded from 
applying response headers.)

> Response Headers: Code refactoring
> --
>
> Key: ATLAS-3841
> URL: https://issues.apache.org/jira/browse/ATLAS-3841
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Updated] (ATLAS-3841) Response Headers: Code refactoring

2020-07-07 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3841:
---
Description: 
Currently headers setting code is scattered at different places.
In this patch, code refactoring is done to set response headers from 
AtlasHeaderFilter.java

Currently js/ html files come under the unauthorized urls.
Therefore, these files do not have headers which are applied by default by 
spring security.

To overcome this problem, In this patch we are applying all the spring security 
headers to these unauthorized urls explicitly.
We are doing this by mapping all the urls (authorized + unauthorized) to go 
through one servlet filter which is AtlasHeaderFilter.

In case of authorized urls, spring by default set some of the headers. To avoid 
overwriting of these headers in authorized urls, those headers are skipped in 
the AtlasHeaderFilter.

Also this patch provides flexibility to select file formats to be excluded from 
applying response headers.

> Response Headers: Code refactoring
> --
>
> Key: ATLAS-3841
> URL: https://issues.apache.org/jira/browse/ATLAS-3841
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently headers setting code is scattered at different places.
> In this patch, code refactoring is done to set response headers from 
> AtlasHeaderFilter.java
> Currently js/ html files come under the unauthorized urls.
> Therefore, these files do not have headers which are applied by default by 
> spring security.
> To overcome this problem, In this patch we are applying all the spring 
> security headers to these unauthorized urls explicitly.
> We are doing this by mapping all the urls (authorized + unauthorized) to go 
> through one servlet filter which is AtlasHeaderFilter.
> In case of authorized urls, spring by default set some of the headers. To 
> avoid overwriting of these headers in authorized urls, those headers are 
> skipped in the AtlasHeaderFilter.
> Also this patch provides flexibility to select file formats to be excluded 
> from applying response headers.



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


[jira] [Updated] (ATLAS-3841) Response Headers: Code refactoring

2020-07-06 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3841:
---
Description: 
Currently headers setting code is scattered at different places.
In this patch, code refactoring is done to set response headers from 
AtlasHeaderFilter.java

This patch provides flexibility to select response headers to be excluded.
Also this patch provides flexibility to select file formats to be excluded from 
applying response headers.

> Response Headers: Code refactoring
> --
>
> Key: ATLAS-3841
> URL: https://issues.apache.org/jira/browse/ATLAS-3841
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Currently headers setting code is scattered at different places.
> In this patch, code refactoring is done to set response headers from 
> AtlasHeaderFilter.java
> This patch provides flexibility to select response headers to be excluded.
> Also this patch provides flexibility to select file formats to be excluded 
> from applying response headers.



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


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

2020-07-04 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane commented on ATLAS-3872:


*Cause of the problem:*
Type-def Column is created by quick-start script.

Here in this case, Type-def Column has the attribute "name". And it has 
property isOptional = true

Type-def Column is a child of Type-def Asset which also has the attribute 
"name". And it has property isOptional = false

Now while creating Entity of Type-def Column from UI, it does not show 
attribute "name" in the mandatory fields because for Type-def Column its 
property isOptional = true

But while validating the attributes from server side we iterate through all the 
attributes of Entity type (Including Parent's attributes)
In this case, while validating Type-def Asset's attribute "name" (which has 
property isOptional = false) we get an error because its value is sent as 
"null" from UI side.

> While creating Column entity shows error message
> 
>
> Key: ATLAS-3872
> URL: https://issues.apache.org/jira/browse/ATLAS-3872
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Durga Kadam
>Assignee: Mandar Ambawane
>Priority: Minor
> Attachments: column_entity_name_field_issue.ogv
>
>
> Description:: While creating Column entity(whose entity-type has been 
> generated from running quick_start.py) if user does not provide the 'name'(by 
> enabling the toggle 'Required All') it shows below error message.
> Error message:: 
> Invalid instance creation/updation parameters passed : Column.name: mandatory 
> attribute value missing in type Asset
> Steps to reproduce issue::
>  # Go to Create  entity
>  # Select 'Column' type
>  # Enter 'QualifiedName(string)' and select the 'Table(Table)' from drop-down
>  # Click on Create buttonIt will show error message
> Note-
>  # If user provides the 'name' which is listed inside the 'Required All' tab 
> it will allow user to save the entity. PFA attached video.
>  # Working fine for Hive_column and Hbase_column as user provides the 
> mandatory name field which is listed outside the 'Required All' tab



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


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

2020-06-30 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-3872:
--

Assignee: Mandar Ambawane

> While creating Column entity shows error message
> 
>
> Key: ATLAS-3872
> URL: https://issues.apache.org/jira/browse/ATLAS-3872
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Durga Kadam
>Assignee: Mandar Ambawane
>Priority: Minor
> Attachments: column_entity_name_field_issue.ogv
>
>
> Description:: While creating Column entity(whose entity-type has been 
> generated from running quick_start.py) if user does not provide the 'name'(by 
> enabling the toggle 'Required All') it shows below error message.
> Error message:: 
> Invalid instance creation/updation parameters passed : Column.name: mandatory 
> attribute value missing in type Asset
> Steps to reproduce issue::
>  # Go to Create  entity
>  # Select 'Column' type
>  # Enter 'QualifiedName(string)' and select the 'Table(Table)' from drop-down
>  # Click on Create buttonIt will show error message
> Note-
>  # If user provides the 'name' which is listed inside the 'Required All' tab 
> it will allow user to save the entity. PFA attached video.
>  # Working fine for Hive_column and Hbase_column as user provides the 
> mandatory name field which is listed outside the 'Required All' tab



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


[jira] [Created] (ATLAS-3854) Upgrade Spring Security version to 4.2.16

2020-06-22 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3854:
--

 Summary: Upgrade Spring Security version to 4.2.16
 Key: ATLAS-3854
 URL: https://issues.apache.org/jira/browse/ATLAS-3854
 Project: Atlas
  Issue Type: Bug
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane


Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
null initialization vector with CBC Mode in the implementation of the queryable 
text encryptor. A malicious user with access to the data that has been 
encrypted using such an encryptor may be able to derive the unencrypted values 
using a dictionary attack.
To resolve this need to upgrade Spring security to 4.2.16



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


[jira] [Updated] (ATLAS-3854) Upgrade Spring Security version to 4.2.16

2020-06-22 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3854:
---
Description: 
Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
null initialization vector with CBC Mode in the implementation of the queryable 
text encryptor. A malicious user with access to the data that has been 
encrypted using such an encryptor may be able to derive the unencrypted values 
using a dictionary attack.


 To resolve this need to upgrade Spring security to 4.2.16

  was:
Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
null initialization vector with CBC Mode in the implementation of the queryable 
text encryptor. A malicious user with access to the data that has been 
encrypted using such an encryptor may be able to derive the unencrypted values 
using a dictionary attack.
To resolve this need to upgrade Spring security to 4.2.16


> Upgrade Spring Security version to 4.2.16
> -
>
> Key: ATLAS-3854
> URL: https://issues.apache.org/jira/browse/ATLAS-3854
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
> prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
> null initialization vector with CBC Mode in the implementation of the 
> queryable text encryptor. A malicious user with access to the data that has 
> been encrypted using such an encryptor may be able to derive the unencrypted 
> values using a dictionary attack.
>  To resolve this need to upgrade Spring security to 4.2.16



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


[jira] [Assigned] (ATLAS-3841) Response Headers: Code refactoring

2020-06-15 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-3841:
--

Assignee: Mandar Ambawane

> Response Headers: Code refactoring
> --
>
> Key: ATLAS-3841
> URL: https://issues.apache.org/jira/browse/ATLAS-3841
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Created] (ATLAS-3841) Response Headers: Code refactoring

2020-06-15 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3841:
--

 Summary: Response Headers: Code refactoring
 Key: ATLAS-3841
 URL: https://issues.apache.org/jira/browse/ATLAS-3841
 Project: Atlas
  Issue Type: Bug
Reporter: Mandar Ambawane






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


[jira] [Assigned] (ATLAS-3835) Atlas security headers missing in .js and .html file apis

2020-06-10 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-3835:
--

Assignee: Mandar Ambawane

> Atlas security headers missing in .js and .html file apis
> -
>
> Key: ATLAS-3835
> URL: https://issues.apache.org/jira/browse/ATLAS-3835
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Created] (ATLAS-3835) Atlas security headers missing in .js and .html file apis

2020-06-10 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3835:
--

 Summary: Atlas security headers missing in .js and .html file apis
 Key: ATLAS-3835
 URL: https://issues.apache.org/jira/browse/ATLAS-3835
 Project: Atlas
  Issue Type: Bug
Reporter: Mandar Ambawane






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


[jira] [Created] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-06-01 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3822:
--

 Summary: UI changes: Audit entries for TypeDefs CREATE, UPDATE and 
DELETE
 Key: ATLAS-3822
 URL: https://issues.apache.org/jira/browse/ATLAS-3822
 Project: Atlas
  Issue Type: Bug
Reporter: Mandar Ambawane
Assignee: Keval Bhatt






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


[jira] [Created] (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-05-27 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3813:
--

 Summary: 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


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] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-05-05 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3583:
---
Summary: Use Audit framework to generate audit entries for TypeDefs CREATE, 
UPDATE and DELETE  (was: Use Audit framework to generate audit entries for 
Classification CREATE, UPDATE and DELETE)

> Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and 
> DELETE
> 
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Created] (ATLAS-3763) Add "serviceType" in AtlasEntityHeader

2020-04-29 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3763:
--

 Summary: Add "serviceType" in AtlasEntityHeader
 Key: ATLAS-3763
 URL: https://issues.apache.org/jira/browse/ATLAS-3763
 Project: Atlas
  Issue Type: Bug
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane






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


[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for Classification CREATE, UPDATE and DELETE

2020-04-20 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3583:
---
Component/s:  atlas-core

> Use Audit framework to generate audit entries for Classification CREATE, 
> UPDATE and DELETE
> --
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


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

2020-04-14 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-3692:
--

Assignee: Keval Bhatt

> [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
>Assignee: Keval Bhatt
>Priority: Major
> 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] [Assigned] (ATLAS-3709) [Business Metadata] Issues with quick search/suggestions in conjunction with Business Metadata attributes

2020-04-03 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-3709:
--

Assignee: Mandar Ambawane  (was: Keval Bhatt)

> [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
>Assignee: Mandar Ambawane
>Priority: Blocker
> 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] [Commented] (ATLAS-3681) Cluttered Business Metadata Attribute listing under entity filters

2020-04-03 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane commented on ATLAS-3681:


+1 for the patch

> 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
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3681.patch, Screen Shot 2020-04-03 at 12.25.38 
> PM.png, 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] [Updated] (ATLAS-3689) Add audits entries when Business Metadata Attributes are added/updated/deleted to an entity

2020-03-25 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3689:
---
Summary: Add audits entries when Business Metadata Attributes are 
added/updated/deleted to an entity  (was: Add audits entries when Namespace 
Attributes are added/updated/deleted to an entity)

> Add audits entries when Business Metadata Attributes are 
> added/updated/deleted to an entity
> ---
>
> Key: ATLAS-3689
> URL: https://issues.apache.org/jira/browse/ATLAS-3689
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


[jira] [Created] (ATLAS-3689) Add audits entries when Namespace Attributes are added/updated/deleted to an entity

2020-03-25 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3689:
--

 Summary: Add audits entries when Namespace Attributes are 
added/updated/deleted to an entity
 Key: ATLAS-3689
 URL: https://issues.apache.org/jira/browse/ATLAS-3689
 Project: Atlas
  Issue Type: Bug
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane






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


[jira] [Created] (ATLAS-3675) Enable quick search and suggestions for business metadata attributes

2020-03-21 Thread Mandar Ambawane (Jira)
Mandar Ambawane created ATLAS-3675:
--

 Summary: Enable quick search and suggestions for business metadata 
attributes
 Key: ATLAS-3675
 URL: https://issues.apache.org/jira/browse/ATLAS-3675
 Project: Atlas
  Issue Type: Bug
Reporter: Mandar Ambawane
Assignee: Mandar Ambawane






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


[jira] [Updated] (ATLAS-3645) Update default entity permission for labels and namespace resource in atlas-simple-authz-policy.json

2020-03-02 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3645:
---
Attachment: ATLAS-3645.patch

> Update default entity permission for labels and namespace resource in 
> atlas-simple-authz-policy.json
> 
>
> Key: ATLAS-3645
> URL: https://issues.apache.org/jira/browse/ATLAS-3645
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Nixon Rodrigues
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3645.patch
>
>
> default entity permissions for labels and namespace are missing in 
> atlas-simple-authz-policy.json for simple authz.



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


[jira] [Assigned] (ATLAS-3645) Update default entity permission for labels and namespace resource in atlas-simple-authz-policy.json

2020-03-02 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane reassigned ATLAS-3645:
--

Assignee: Mandar Ambawane

> Update default entity permission for labels and namespace resource in 
> atlas-simple-authz-policy.json
> 
>
> Key: ATLAS-3645
> URL: https://issues.apache.org/jira/browse/ATLAS-3645
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Nixon Rodrigues
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> default entity permissions for labels and namespace are missing in 
> atlas-simple-authz-policy.json for simple authz.



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


[jira] [Updated] (ATLAS-3625) Add Test cases for Namespace type creation and Namespace-Entity association

2020-02-27 Thread Mandar Ambawane (Jira)


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

Mandar Ambawane updated ATLAS-3625:
---
Summary: Add Test cases for Namespace type creation and Namespace-Entity 
association  (was: Add Test cases for Namespace type creationa and 
Namespace-Entity association)

> Add Test cases for Namespace type creation and Namespace-Entity association
> ---
>
> Key: ATLAS-3625
> URL: https://issues.apache.org/jira/browse/ATLAS-3625
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>




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


  1   2   >