[jira] [Commented] (ATLAS-3992) UI: Upgrade to JQuery 3.5.1

2020-10-21 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3992:


Commit 5097a76e0195e58ed311c1ce9ebbc68ba6d82ca2 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5097a76 ]

ATLAS-3992: UI: Upgrade to JQuery 3.5.1


> UI: Upgrade to JQuery 3.5.1
> ---
>
> Key: ATLAS-3992
> URL: https://issues.apache.org/jira/browse/ATLAS-3992
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3992.patch
>
>




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


[jira] [Commented] (ATLAS-3992) UI: Upgrade to JQuery 3.5.1

2020-10-21 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3992:


Commit 3f1cf185200206827d309ab76f3ad729ad7a5e3b in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3f1cf18 ]

ATLAS-3992: UI: Upgrade to JQuery 3.5.1


> UI: Upgrade to JQuery 3.5.1
> ---
>
> Key: ATLAS-3992
> URL: https://issues.apache.org/jira/browse/ATLAS-3992
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3992.patch
>
>




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


[jira] [Commented] (ATLAS-3999) Update build to avoid distro in multiple formats - tar.gz and dir

2020-10-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3999:


Commit bd9d1213b48721f269f32db1ee388e2beb9a7d3d in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=bd9d121 ]

ATLAS-3999: updated build to remove copying of dist artifacts into directories


> Update build to avoid distro in multiple formats - tar.gz and dir
> -
>
> Key: ATLAS-3999
> URL: https://issues.apache.org/jira/browse/ATLAS-3999
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3999.patch
>
>
> Atlas build generates distro in multiple formats - for example: tar.gz or zip 
> and a directory. To save build time and disk space, build should be updated 
> to only generate archives - .tar.gz or .zip, and avoid creating directories 
> with the same contents.



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


[jira] [Commented] (ATLAS-3938) Import Hive Script: Support deletion of non existing database and table entities

2020-10-19 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3938:


Commit d5ea2b838a142f17146bb0861eed9cd287179f79 in atlas's branch 
refs/heads/branch-2.0 from Pinal
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d5ea2b8 ]

ATLAS-3938 : Import Hive Script: Support deletion of non existing database and 
table entities

(cherry picked from commit b4e4f604b46805ade02413da6ef1a68b2f28da71)


> Import Hive Script:  Support deletion of non existing database and table 
> entities
> -
>
> Key: ATLAS-3938
> URL: https://issues.apache.org/jira/browse/ATLAS-3938
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> *Problem* : Whenever database or table is dropped in hive, and HiveHook is 
> not enabled, we dont have anyway to get the database and table sync with hive.
> *Workaround* : Added support to delete database and table entities present in 
> Atlas, but not in Hive.
> *Usage* : ./import-hive.sh -deleteNonExisting
> *NOTE : atlas.hook.hive.page.limit* property is added to configure the 
> pageSize/limit while fetching entities from Atlas



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


[jira] [Commented] (ATLAS-3938) Import Hive Script: Support deletion of non existing database and table entities

2020-10-19 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3938:


Commit b4e4f604b46805ade02413da6ef1a68b2f28da71 in atlas's branch 
refs/heads/master from Pinal
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b4e4f60 ]

ATLAS-3938 : Import Hive Script: Support deletion of non existing database and 
table entities


> Import Hive Script:  Support deletion of non existing database and table 
> entities
> -
>
> Key: ATLAS-3938
> URL: https://issues.apache.org/jira/browse/ATLAS-3938
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> *Problem* : Whenever database or table is dropped in hive, and HiveHook is 
> not enabled, we dont have anyway to get the database and table sync with hive.
> *Workaround* : Added support to delete database and table entities present in 
> Atlas, but not in Hive.
> *Usage* : ./import-hive.sh -deleteNonExisting
> *NOTE : atlas.hook.hive.page.limit* property is added to configure the 
> pageSize/limit while fetching entities from Atlas



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


[jira] [Commented] (ATLAS-3995) Atlas should support additional keystore/truststores types besides JKS

2020-10-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3995:


Commit f829adbbb0b7c4cbbfa0a35581b5829384bda56c in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f829adb ]

ATLAS-3995 : Atlas should support additional keystore/truststores types besides 
JKS.

(cherry picked from commit fd24e652b5e2f607cad0d665c88d770479832263)


> Atlas should support additional keystore/truststores types besides JKS
> --
>
> Key: ATLAS-3995
> URL: https://issues.apache.org/jira/browse/ATLAS-3995
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Currently Atlas server (through Jetty) only supports JKS keystore/truststore 
> types. There are additional keystore/truststore types used for different 
> applications like for FIPS crypto algorithms.
> Atlas server should support the default keystore type specified for the JDK 
> and have option to configure other keystore/truststore  types.



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


[jira] [Commented] (ATLAS-3982) Upgrade Atlas Spring framework version to 4.3.29.RELEASE

2020-10-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3982:


Commit 3612396c16cf43bf6eba5caf38974c2b32f54e34 in atlas's branch 
refs/heads/branch-2.0 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3612396 ]

ATLAS-3982 : Upgrade Atlas Spring framework version to 4.3.29.RELEASE

Signed-off-by: nixonrodrigues 
(cherry picked from commit d0de38970e1289cf726f8952dd3e2e93b0a158a3)


> Upgrade Atlas Spring framework version to 4.3.29.RELEASE
> 
>
> Key: ATLAS-3982
> URL: https://issues.apache.org/jira/browse/ATLAS-3982
> Project: Atlas
>  Issue Type: Improvement
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> Upgrade to prevent CVE-2020-5421



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


[jira] [Commented] (ATLAS-3982) Upgrade Atlas Spring framework version to 4.3.29.RELEASE

2020-10-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3982:


Commit d0de38970e1289cf726f8952dd3e2e93b0a158a3 in atlas's branch 
refs/heads/master from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d0de389 ]

ATLAS-3982 : Upgrade Atlas Spring framework version to 4.3.29.RELEASE

Signed-off-by: nixonrodrigues 


> Upgrade Atlas Spring framework version to 4.3.29.RELEASE
> 
>
> Key: ATLAS-3982
> URL: https://issues.apache.org/jira/browse/ATLAS-3982
> Project: Atlas
>  Issue Type: Improvement
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> Upgrade to prevent CVE-2020-5421



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


[jira] [Commented] (ATLAS-3995) Atlas should support additional keystore/truststores types besides JKS

2020-10-14 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3995:


Commit fd24e652b5e2f607cad0d665c88d770479832263 in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fd24e65 ]

ATLAS-3995 : Atlas should support additional keystore/truststores types besides 
JKS.


> Atlas should support additional keystore/truststores types besides JKS
> --
>
> Key: ATLAS-3995
> URL: https://issues.apache.org/jira/browse/ATLAS-3995
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Currently Atlas server (through Jetty) only supports JKS keystore/truststore 
> types. There are additional keystore/truststore types used for different 
> applications like for FIPS crypto algorithms.
> Atlas server should support the default keystore type specified for the JDK 
> and have option to configure other keystore/truststore  types.



--
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 ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3986:


Commit 3768c9dcd33eb045c834a8e6cebe4703ab0d933d in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3768c9d ]

ATLAS-3986: UI Allow user to update the date format from JAVA property file

(cherry picked from commit 39892854ffb696df70ecbc0f3e965c5a8261f621)


> 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 ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3986:


Commit 39892854ffb696df70ecbc0f3e965c5a8261f621 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3989285 ]

ATLAS-3986: UI Allow user to update the date format from JAVA property file


> 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-3990) UI: When user clicks to view hive-table details, shown some wrong tabs

2020-10-14 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3990:


Commit d5db1a67cd5bb8adc357c465dedcd043429fc771 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d5db1a6 ]

ATLAS-3990: UI: When user clicks to view hive-table details, shown some wrong 
tabs


> UI: When user clicks to view hive-table details, shown some wrong tabs
> --
>
> Key: ATLAS-3990
> URL: https://issues.apache.org/jira/browse/ATLAS-3990
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3990.patch, wrong_tabs_showing_on_clicks.mkv
>
>
> Steps to reproduce::
>  # Have a hive_db with at least one table
>  # Click on 'Tables' tab
>  # Click on one of the tables listed in the tab
>  # The page renders the table details, including addition of 'Schema' tab
>  # However, 'Tables' tab is still visible; this tab needs to be hidden
>  # Also, on clicking the db link in Properties page of hive_table, 'Schema' 
> tab is still visible. This should be hidden
> PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv



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


[jira] [Commented] (ATLAS-3990) UI: When user clicks to view hive-table details, shown some wrong tabs

2020-10-14 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3990:


Commit 94d43c63c6021450845ff17c5bd952dbf5f8958a in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=94d43c6 ]

ATLAS-3990: UI: When user clicks to view hive-table details, shown some wrong 
tabs


> UI: When user clicks to view hive-table details, shown some wrong tabs
> --
>
> Key: ATLAS-3990
> URL: https://issues.apache.org/jira/browse/ATLAS-3990
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3990.patch, wrong_tabs_showing_on_clicks.mkv
>
>
> Steps to reproduce::
>  # Have a hive_db with at least one table
>  # Click on 'Tables' tab
>  # Click on one of the tables listed in the tab
>  # The page renders the table details, including addition of 'Schema' tab
>  # However, 'Tables' tab is still visible; this tab needs to be hidden
>  # Also, on clicking the db link in Properties page of hive_table, 'Schema' 
> tab is still visible. This should be hidden
> PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv



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


[jira] [Commented] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3977:


Commit 374e20e49931040bee996a56e32d477ceb049893 in atlas's branch 
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=374e20e ]

ATLAS-3977: Deleted entity behavior fix during migration. Part 2


> Migration Script: Deleted entities in Atlas1.0 miss few attributes after 
> migrated to Atlas2.0
> -
>
> Key: ATLAS-3977
> URL: https://issues.apache.org/jira/browse/ATLAS-3977
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha S
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3977-Addressed-patch-processing-for.patch, 
> ATLAS-3977-Deleted-entity-behavior-fix-during-migrat-Part-2.patch, 
> am2cm_deleted_active_entity.png
>
>
> table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0
> Attributes like name , db , owner are missing in DELETED entities whereas 
> they are populated correctly in ACTIVE entities.
> Attaching the screenshot.



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


[jira] [Commented] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3977:


Commit 080e4843480743558bc4b61d9c2860b414786ccc in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=080e484 ]

ATLAS-3977: Deleted entity behavior fix during migration. Part 2


> Migration Script: Deleted entities in Atlas1.0 miss few attributes after 
> migrated to Atlas2.0
> -
>
> Key: ATLAS-3977
> URL: https://issues.apache.org/jira/browse/ATLAS-3977
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha S
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3977-Addressed-patch-processing-for.patch, 
> ATLAS-3977-Deleted-entity-behavior-fix-during-migrat-Part-2.patch, 
> am2cm_deleted_active_entity.png
>
>
> table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0
> Attributes like name , db , owner are missing in DELETED entities whereas 
> they are populated correctly in ACTIVE entities.
> Attaching the screenshot.



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


[jira] [Commented] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3875:


Commit aba621dd69de2cf8924ca32ec6dea5b2913e4e41 in atlas's branch 
refs/heads/branch-2.0 from jyoti0208
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=aba621d ]

ATLAS-3875: Introduce python client for Atlas

Signed-off-by: Sarath Subramanian 
(cherry picked from commit 5aab626e5a0436028389ba6b10734a323260cd66)


> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>  Labels: api, client
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3875-1.patch, ATLAS-3875-2.patch, 
> ATLAS-3875-4.patch
>
>
> 1. There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest
> 2. Added Sample-Project to showcase how to integrate with Atlas using 
> AtlasCleint. This helps the user to understand the basic rest functionality 
> of Atlas.



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


[jira] [Commented] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3875:


Commit 5aab626e5a0436028389ba6b10734a323260cd66 in atlas's branch 
refs/heads/master from jyoti0208
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5aab626 ]

ATLAS-3875: Introduce python client for Atlas

Signed-off-by: Sarath Subramanian 


> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>  Labels: api, client
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3875-1.patch, ATLAS-3875-2.patch, 
> ATLAS-3875-4.patch
>
>
> 1. There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest
> 2. Added Sample-Project to showcase how to integrate with Atlas using 
> AtlasCleint. This helps the user to understand the basic rest functionality 
> of Atlas.



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


[jira] [Commented] (ATLAS-3954) UI: Type system property table improvement

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3954:


Commit a9da759e5f342592179cc4cde574420d84d8529e in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a9da759 ]

ATLAS-3954: UI: Type system property table improvement

(cherry picked from commit 3c0b2746d0065b1d95b4511c46a8655d4167096e)


> UI: Type system property table improvement
> --
>
> Key: ATLAS-3954
> URL: https://issues.apache.org/jira/browse/ATLAS-3954
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3954-1.patch, ATLAS-3954.patch
>
>




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


[jira] [Commented] (ATLAS-3991) UI: Handlebar helper number format issue

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3991:


Commit cd9bd02befc6cb3c3cb8ddc1f807aa6a2e0a5250 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=cd9bd02 ]

ATLAS-3991: UI: Handlebar helper number format issue

(cherry picked from commit 74c9394148d175950615f82455dc1e302000c01b)


> UI: Handlebar helper number format issue
> 
>
> Key: ATLAS-3991
> URL: https://issues.apache.org/jira/browse/ATLAS-3991
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3991.patch, 
> screenshot-localhost_-2020.10.13-18_21_07.png
>
>
> if a number has coma in it then arithmetic helper not able to calculate the 
> value.
> Example:
> if the value is *20,201* then the helper will return the value *20*
>  
> *!screenshot-localhost_-2020.10.13-18_21_07.png!*



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


[jira] [Commented] (ATLAS-3954) UI: Type system property table improvement

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3954:


Commit 3c0b2746d0065b1d95b4511c46a8655d4167096e in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3c0b274 ]

ATLAS-3954: UI: Type system property table improvement


> UI: Type system property table improvement
> --
>
> Key: ATLAS-3954
> URL: https://issues.apache.org/jira/browse/ATLAS-3954
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3954-1.patch, ATLAS-3954.patch
>
>




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


[jira] [Commented] (ATLAS-3991) UI: Handlebar helper number format issue

2020-10-13 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3991:


Commit 74c9394148d175950615f82455dc1e302000c01b in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=74c9394 ]

ATLAS-3991: UI: Handlebar helper number format issue


> UI: Handlebar helper number format issue
> 
>
> Key: ATLAS-3991
> URL: https://issues.apache.org/jira/browse/ATLAS-3991
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3991.patch, 
> screenshot-localhost_-2020.10.13-18_21_07.png
>
>
> if a number has coma in it then arithmetic helper not able to calculate the 
> value.
> Example:
> if the value is *20,201* then the helper will return the value *20*
>  
> *!screenshot-localhost_-2020.10.13-18_21_07.png!*



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


[jira] [Commented] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication

2020-10-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3989:


Commit 757282f23338fa00c2a5112b538d43818d2057d0 in atlas's branch 
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=757282f ]

ATLAS-3989: Updated Export-Import Audits Writer to use metadata.namespace.


> Behavior change in Atlas API to get Atlas Server object during metadata 
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: 
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas 
> metadata replication in hive.
>  Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster 
> name, used to work.
>  Now, it doesn't work any more. This Api is used during replication to get 
> the changeMarker info.
>  Now the API works with some thing called server name which is 'default' by 
> default.
>  Also, now the prerequisite is to at least have one export or import API call 
> in order to get this 'default' initialized.
>  The change-marker is obtained prior to invoking export and hence the all 
> policy is bound to fail unless we mandate calling Export or Import API 
> outside hive replication once to get this object initialized, even if hive 
> uses 'default' in the call.
>  
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}



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


[jira] [Commented] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication

2020-10-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3989:


Commit 39ff496f129b64352e91b462c7882491a3929981 in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=39ff496 ]

ATLAS-3989: Updated Export-Import Audits Writer to use metadata.namespace.


> Behavior change in Atlas API to get Atlas Server object during metadata 
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: 
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas 
> metadata replication in hive.
>  Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster 
> name, used to work.
>  Now, it doesn't work any more. This Api is used during replication to get 
> the changeMarker info.
>  Now the API works with some thing called server name which is 'default' by 
> default.
>  Also, now the prerequisite is to at least have one export or import API call 
> in order to get this 'default' initialized.
>  The change-marker is obtained prior to invoking export and hence the all 
> policy is bound to fail unless we mandate calling Export or Import API 
> outside hive replication once to get this object initialized, even if hive 
> uses 'default' in the call.
>  
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}



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


[jira] [Commented] (ATLAS-3987) Atlas client export API does not pass server response code in case of failure

2020-10-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3987:


Commit 47c3155e04a438f02e2fd49740065ce983aa66e9 in atlas's branch 
refs/heads/branch-2.0 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=47c3155 ]

ATLAS-3987: Atlas client export API, must pass server error code in the 
exception

Signed-off-by: Ashutosh Mestry 


> Atlas client export API does not pass server response code in case of failure
> -
>
> Key: ATLAS-3987
> URL: https://issues.apache.org/jira/browse/ATLAS-3987
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
>
> For Atlas export, Admin priveledges are required. If such priveledges are not 
> there, then Export API fails with 403 status. However, the atlasClient does 
> not pass this information in the exception.



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


[jira] [Commented] (ATLAS-3987) Atlas client export API does not pass server response code in case of failure

2020-10-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3987:


Commit f5db98b3ba5a6bdf851b1319abab5f953d6ff0f4 in atlas's branch 
refs/heads/master from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f5db98b ]

ATLAS-3987: Atlas client export API, must pass server error code in the 
exception

Signed-off-by: Ashutosh Mestry 


> Atlas client export API does not pass server response code in case of failure
> -
>
> Key: ATLAS-3987
> URL: https://issues.apache.org/jira/browse/ATLAS-3987
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
>
> For Atlas export, Admin priveledges are required. If such priveledges are not 
> there, then Export API fails with 403 status. However, the atlasClient does 
> not pass this information in the exception.



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


[jira] [Commented] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work

2020-10-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3978:


Commit 87cf906b4a696a39130b4cd2310cbb096d7c1a83 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=87cf906 ]

ATLAS-3978: In Administration, Audits filter for 'OR' condition does not work

(cherry picked from commit 4ab4962314a80d9e0ac766f81018e22995c8e83d)


> In Administration, Audits filter for 'OR' condition does not work
> -
>
> Key: ATLAS-3978
> URL: https://issues.apache.org/jira/browse/ATLAS-3978
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3978.patch, OR condition not working.mkv
>
>
> Description::
> When user uses OR condition it does not apply on filter, results are listed 
> with AND condition. PFA evidence file [OR condition not working.mkv]
> Steps to regenerate::
>  # Go to Administration- Audits
>  # Select the OR condition filter
>  # Check the console for response
>  # Results are listed with 'AND' operator instead of 'OR'



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


[jira] [Commented] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work

2020-10-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3978:


Commit 4ab4962314a80d9e0ac766f81018e22995c8e83d in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4ab4962 ]

ATLAS-3978: In Administration, Audits filter for 'OR' condition does not work


> In Administration, Audits filter for 'OR' condition does not work
> -
>
> Key: ATLAS-3978
> URL: https://issues.apache.org/jira/browse/ATLAS-3978
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3978.patch, OR condition not working.mkv
>
>
> Description::
> When user uses OR condition it does not apply on filter, results are listed 
> with AND condition. PFA evidence file [OR condition not working.mkv]
> Steps to regenerate::
>  # Go to Administration- Audits
>  # Select the OR condition filter
>  # Check the console for response
>  # Results are listed with 'AND' operator instead of 'OR'



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


[jira] [Commented] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.

2020-10-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3979:


Commit 58d630bf19540710a36ec47ee9fdfd771aafa5b7 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=58d630b ]

ATLAS-3979: Beta UI : Removing one of the filters with an attribute name 
removes all of the filters with that attribute name.

(cherry picked from commit 70c1087a121feb3fe88cc67681b470109443ff81)


> Beta UI : Removing one of the filters with an attribute name removes all of 
> the filters with that attribute name.
> -
>
> Key: ATLAS-3979
> URL: https://issues.apache.org/jira/browse/ATLAS-3979
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3979.patch
>
>
> Create a basic search with filters:
> typename = _ALL_ENTITY_TYPES
> filters:
> _classificationNames = tag1 and
> _classificationNames = tag2 and
> _createdBy = hive
> Fire Search.
> From UI , remove "_classificationNames = tag1" filter .
> This removes "_classificationNames = tag2" filter too since the attribute 
> name _classificationNames is same.
> Other attribute _createdBy is intact.



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


[jira] [Commented] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger

2020-10-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3981:


Commit ba8b490cd192b497d3bc4996f68e016814a92fbb in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ba8b490 ]

ATLAS-3981: UI: Create Entity button is shown for a user without create entity 
permission in ranger

(cherry picked from commit f5ffd06486f6ef3c28236c6c70e74561542d30c1)


> UI: Create Entity button is shown for a user without create entity permission 
> in ranger
> ---
>
> Key: ATLAS-3981
> URL: https://issues.apache.org/jira/browse/ATLAS-3981
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3981.patch
>
>




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


[jira] [Commented] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.

2020-10-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3979:


Commit 70c1087a121feb3fe88cc67681b470109443ff81 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=70c1087 ]

ATLAS-3979: Beta UI : Removing one of the filters with an attribute name 
removes all of the filters with that attribute name.


> Beta UI : Removing one of the filters with an attribute name removes all of 
> the filters with that attribute name.
> -
>
> Key: ATLAS-3979
> URL: https://issues.apache.org/jira/browse/ATLAS-3979
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3979.patch
>
>
> Create a basic search with filters:
> typename = _ALL_ENTITY_TYPES
> filters:
> _classificationNames = tag1 and
> _classificationNames = tag2 and
> _createdBy = hive
> Fire Search.
> From UI , remove "_classificationNames = tag1" filter .
> This removes "_classificationNames = tag2" filter too since the attribute 
> name _classificationNames is same.
> Other attribute _createdBy is intact.



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


[jira] [Commented] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger

2020-10-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3981:


Commit f5ffd06486f6ef3c28236c6c70e74561542d30c1 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f5ffd06 ]

ATLAS-3981: UI: Create Entity button is shown for a user without create entity 
permission in ranger


> UI: Create Entity button is shown for a user without create entity permission 
> in ranger
> ---
>
> Key: ATLAS-3981
> URL: https://issues.apache.org/jira/browse/ATLAS-3981
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3981.patch
>
>




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


[jira] [Commented] (ATLAS-3971) Move authorization check for Business Metadata before type exist check

2020-10-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3971:


Commit 92b70715e0bf50fe7c3dcc5227182202f8fe0c6e in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=92b7071 ]

ATLAS-3971 :- Move authorization check for Business Metadata before type exist 
check.

(cherry picked from commit 8098bc5643cd45f53d2d9284785693a406d8a270)


> Move authorization check for Business Metadata before type exist check
> --
>
> Key: ATLAS-3971
> URL: https://issues.apache.org/jira/browse/ATLAS-3971
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3971.patch
>
>
> Refactor authorization check for Business Metadata before type exist check, 
> so that enduser is aware that a duplicate type creation is being attempted 
> which exist he is authorized to.



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


[jira] [Commented] (ATLAS-3971) Move authorization check for Business Metadata before type exist check

2020-10-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3971:


Commit 8098bc5643cd45f53d2d9284785693a406d8a270 in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8098bc5 ]

ATLAS-3971 :- Move authorization check for Business Metadata before type exist 
check.


> Move authorization check for Business Metadata before type exist check
> --
>
> Key: ATLAS-3971
> URL: https://issues.apache.org/jira/browse/ATLAS-3971
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3971.patch
>
>
> Refactor authorization check for Business Metadata before type exist check, 
> so that enduser is aware that a duplicate type creation is being attempted 
> which exist he is authorized to.



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


[jira] [Commented] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0

2020-10-07 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3977:


Commit 2101d82b05d5aaf03b9e47e910f39777013325f0 in atlas's branch 
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2101d82 ]

ATLAS-3977: Patch handler for addressing deleted entities after migration.


> Migration Script: Deleted entities in Atlas1.0 miss few attributes after 
> migrated to Atlas2.0
> -
>
> Key: ATLAS-3977
> URL: https://issues.apache.org/jira/browse/ATLAS-3977
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha S
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3977-Addressed-patch-processing-for.patch, 
> am2cm_deleted_active_entity.png
>
>
> table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0
> Attributes like name , db , owner are missing in DELETED entities whereas 
> they are populated correctly in ACTIVE entities.
> Attaching the screenshot.



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


[jira] [Commented] (ATLAS-3965) Relationships with null values are missing in entity relationshipAttributes

2020-10-07 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3965:


Commit 6cc3cf6b434e719b79434a01ea6eedaf3a3c0afd in atlas's branch 
refs/heads/branch-2.0 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6cc3cf6 ]

ATLAS-3965: Relationships with null values are missing in entity 
relationshipAttributes

Signed-off-by: Ashutosh Mestry 


> Relationships with null values are missing in entity relationshipAttributes
> ---
>
> Key: ATLAS-3965
> URL: https://issues.apache.org/jira/browse/ATLAS-3965
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Attachments: 
> 0002-ATLAS-3965-Relationships-with-null-values-are-missin.patch
>
>
> kafka_topic typedef has relationship attributes:
> {code:java}
> inputToProcesses
> pipeline
> schema
> model
> avroSchema
> meanings
> outputFromProcesses{code}
> When a kafka topic entity is created using import-kafka.sh script, the entity 
> doesn't have all relationship attributes :
> {code:java}
> "relationshipAttributes": {
> "inputToProcesses": [ ],
> "schema": [ ],
> "avroSchema": [ ],
> "meanings": [ ],
> "outputFromProcesses": [ ]}, {code}
> The missing ones are "pipeline" and "model" . 



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


[jira] [Commented] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0

2020-10-07 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3977:


Commit 54bab3f88ed580e54074fc0f26b01f6d103fde60 in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=54bab3f ]

ATLAS-3977: Patch handler for addressing deleted entities after migration.


> Migration Script: Deleted entities in Atlas1.0 miss few attributes after 
> migrated to Atlas2.0
> -
>
> Key: ATLAS-3977
> URL: https://issues.apache.org/jira/browse/ATLAS-3977
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha S
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3977-Addressed-patch-processing-for.patch, 
> am2cm_deleted_active_entity.png
>
>
> table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0
> Attributes like name , db , owner are missing in DELETED entities whereas 
> they are populated correctly in ACTIVE entities.
> Attaching the screenshot.



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


[jira] [Commented] (ATLAS-3983) Update handling of special characters in query-value for index-search

2020-10-07 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3983:


Commit 34cc3c023681ffcf930adf5e5874317f41949cd4 in atlas's branch 
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=34cc3c0 ]

ATLAS-3983: solr index query escape character handling

(cherry picked from commit 8bb3e853ea128e1eb2b181e8db869bf7d8050181)


> Update handling of special characters in query-value for index-search
> -
>
> Key: ATLAS-3983
> URL: https://issues.apache.org/jira/browse/ATLAS-3983
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3983.patch
>
>
> When query-value contains special characters, {{+-&|!(){}[]^"~*?:\/}}, Atlas 
> skips index-search and switches to graph-query, which could be expensive. 
> Index-search can still be used by escaping the special characters with a 
> backslash, per following Lucene documentation 
> [here|https://lucene.apache.org/core/6_5_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Escaping_Special_Characters]:
> {noformat}
> Escaping Special Characters
> Lucene supports escaping special characters that are part of the query 
> syntax. The current list special characters are
> + - && || ! ( ) { } [ ] ^ " ~ * ? : \ /
> To escape these character use the \ before the character. For example to 
> search for (1+1):2 use the query:
> \(1\+1\)\:2
> {noformat}



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


[jira] [Commented] (ATLAS-3983) Update handling of special characters in query-value for index-search

2020-10-07 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3983:


Commit 8bb3e853ea128e1eb2b181e8db869bf7d8050181 in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8bb3e85 ]

ATLAS-3983: solr index query escape character handling


> Update handling of special characters in query-value for index-search
> -
>
> Key: ATLAS-3983
> URL: https://issues.apache.org/jira/browse/ATLAS-3983
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3983.patch
>
>
> When query-value contains special characters, {{+-&|!(){}[]^"~*?:\/}}, Atlas 
> skips index-search and switches to graph-query, which could be expensive. 
> Index-search can still be used by escaping the special characters with a 
> backslash, per following Lucene documentation 
> [here|https://lucene.apache.org/core/6_5_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Escaping_Special_Characters]:
> {noformat}
> Escaping Special Characters
> Lucene supports escaping special characters that are part of the query 
> syntax. The current list special characters are
> + - && || ! ( ) { } [ ] ^ " ~ * ? : \ /
> To escape these character use the \ before the character. For example to 
> search for (1+1):2 use the query:
> \(1\+1\)\:2
> {noformat}



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


[jira] [Commented] (ATLAS-3964) Atlas UI displays large numbers incorrectly

2020-10-06 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3964:


Commit 4f95ee8cc199d17ec954f81d8af9d0152af142f4 in atlas's branch 
refs/heads/master from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4f95ee8 ]

ATLAS-3964: Atlas UI displays large numbers incorrectly #1

Signed-off-by: kevalbhatt 


> Atlas UI displays large numbers incorrectly
> ---
>
> Key: ATLAS-3964
> URL: https://issues.apache.org/jira/browse/ATLAS-3964
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Attachments: details.doc
>
>
> In the case of a type that has an attribute of type Long, and it contains a 
> very large number, the Atlas UI does not show the correct number.  
> Steps to reproduce:
> From the command line:
>  # create an entity type which has a field of type long
>  # create an entity of this same type and the value of the field should be 
> "1085741226505763426"
>  # Atlas will respond with the created entity, you will see that the field 
> value is correct
>  # now open the Atlas website and search for this same entity; you will see 
> the value displayed is "1085741226505763500"



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


[jira] [Commented] (ATLAS-3968) When un-authorised reader reads a type using the guid, the error message mentions about the type name instead of the guid

2020-10-05 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3968:


Commit 4fb04d76f8273ff8f7909d0870c8f4f84938d970 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4fb04d7 ]

ATLAS-3968:- Refactor the typedef API authoriation error msg from type Name to 
type guid

Change-Id: I7552084604f6dbe57f98bd33da013255a4facbad
(cherry picked from commit 45bb769f60ae2f23a4b260dd6e64d76149cd39d0)


> When un-authorised reader reads a type using the guid, the error message 
> mentions about the type name instead of the guid
> -
>
> Key: ATLAS-3968
> URL: https://issues.apache.org/jira/browse/ATLAS-3968
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Nixon Rodrigues
>Priority: Major
>
> On firing a request for /api/atlas/v2/types/businessmetadatadef/guid/ 
> as an unauthorised user, the following error message is displayed
> {code:java}
> {
> u'errorCode': u'ATLAS-403-00-001',
> u'errorMessage': u'hrt_20 is not authorized to perform read type bm_123'
> }
> {code}
> Since we are firing the request using guid, it will be better to mention the 
> guid instead of the type name



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


[jira] [Commented] (ATLAS-3968) When un-authorised reader reads a type using the guid, the error message mentions about the type name instead of the guid

2020-10-05 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3968:


Commit 45bb769f60ae2f23a4b260dd6e64d76149cd39d0 in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=45bb769 ]

ATLAS-3968:- Refactor the typedef API authoriation error msg from type Name to 
type guid

Change-Id: I7552084604f6dbe57f98bd33da013255a4facbad


> When un-authorised reader reads a type using the guid, the error message 
> mentions about the type name instead of the guid
> -
>
> Key: ATLAS-3968
> URL: https://issues.apache.org/jira/browse/ATLAS-3968
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Nixon Rodrigues
>Priority: Major
>
> On firing a request for /api/atlas/v2/types/businessmetadatadef/guid/ 
> as an unauthorised user, the following error message is displayed
> {code:java}
> {
> u'errorCode': u'ATLAS-403-00-001',
> u'errorMessage': u'hrt_20 is not authorized to perform read type bm_123'
> }
> {code}
> Since we are firing the request using guid, it will be better to mention the 
> guid instead of the type name



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


[jira] [Commented] (ATLAS-3965) Relationships with null values are missing in entity relationshipAttributes

2020-10-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3965:


Commit 877e2b1729f3628d844c32769c30a3c948d567a6 in atlas's branch 
refs/heads/master from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=877e2b1 ]

ATLAS-3965: Relationships with null values are missing in entity 
relationshipAttributes

Signed-off-by: Ashutosh Mestry 


> Relationships with null values are missing in entity relationshipAttributes
> ---
>
> Key: ATLAS-3965
> URL: https://issues.apache.org/jira/browse/ATLAS-3965
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Attachments: 
> 0002-ATLAS-3965-Relationships-with-null-values-are-missin.patch
>
>
> kafka_topic typedef has relationship attributes:
> {code:java}
> inputToProcesses
> pipeline
> schema
> model
> avroSchema
> meanings
> outputFromProcesses{code}
> When a kafka topic entity is created using import-kafka.sh script, the entity 
> doesn't have all relationship attributes :
> {code:java}
> "relationshipAttributes": {
> "inputToProcesses": [ ],
> "schema": [ ],
> "avroSchema": [ ],
> "meanings": [ ],
> "outputFromProcesses": [ ]}, {code}
> The missing ones are "pipeline" and "model" . 



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


[jira] [Commented] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-10-01 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3934:


Commit 4733b076c943c00d34f1cabad3aa73efa310b10f in atlas's branch 
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4733b07 ]

ATLAS-3934: Dockerfile: moved environment variables to .env file - #3

(cherry picked from commit ac573f33c72f5cf9b75b50453ad85dd3abadcb15)


> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3934.patch
>
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Commented] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-10-01 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3934:


Commit ac573f33c72f5cf9b75b50453ad85dd3abadcb15 in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ac573f3 ]

ATLAS-3934: Dockerfile: moved environment variables to .env file - #3


> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3934.patch
>
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Commented] (ATLAS-3953) JSON Files from Export API with "?" char for string with special chars

2020-10-01 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3953:


Commit 31b8bdb404978e46c5061a6a8423ed8fbb6d3893 in atlas's branch 
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=31b8bdb ]

ATLAS-3953: Export: ZipSink: Specify character endcoding when writing to ZIP 
file.

Change-Id: I2e3a2bad79f5cf4c91328ed9f64a454ded2acbf3


> JSON Files from Export API with "?" char for string with special chars 
> ---
>
> Key: ATLAS-3953
> URL: https://issues.apache.org/jira/browse/ATLAS-3953
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
> Environment: Apache Atlas 2.1.0 embedded HBASE and SOLR
>Reporter: Carlos Alberto Rocha Cardoso
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: 9fdc3ad0-46c2-430a-89c4-4a751d31c064.json, 
> ATLAS-3953-Export-ZipSink-Specify-character-endcodin.patch, 
> Asset_Imported.PNG, AtlasServer.PNG, 
> a5c148bf-5ab6-4c49-853e-855842102128.json, atlas_export.zip, path.zip
>
>
> The Export API returns a ZIP file with some JSON files describing Atlas 
> Entities and TypeDefs.
> I am having an issue where some special chars in JSON are being replaced by 
> "?" chars.
> An Entity name like "Distribuição" was exported in JSON file like 
> "Distribui??o". The special chars "çã" was replaced for the "??" chars.
> I tried to change the exported JSON file encoding and the request header for 
> Export API but without success.
> After analyzing the Atlas source code, especially the *splitAndWriteBytes* 
> method of the 
> *[ZipSink|https://github.com/apache/atlas/blob/cc601d7371fae1dbc16b55d1ca84f06b745700dc/repository/src/main/java/org/apache/atlas/repository/impexp/ZipSink.java]
>  class*, I thought if maybe the problem is because the *s.getBytes()* is 
> returning the JSON string to be written to ZIP with another encoding than 
> *UTF-8*, and maybe set the encode like *s.getBytes(StandardCharsets.UTF_8)* 
> could be a solution.
> It's my first contact with the Atlas source code, and I'm not a JAVA 
> programmer, so it's only a guess.
> I saw that it's possible to set the default to encode to the platform or JVM, 
> but how they said in this below discussion, perhaps this doesn't work 
> properly in all situations.
> [https://stackoverflow.com/questions/361975/setting-the-default-java-character-encoding]



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


[jira] [Commented] (ATLAS-3953) JSON Files from Export API with "?" char for string with special chars

2020-10-01 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3953:


Commit 9a605b6671b1719eebce04605f100e34c8f5afb0 in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9a605b6 ]

ATLAS-3953: Export: ZipSink: Specify character endcoding when writing to ZIP 
file.

Change-Id: I2e3a2bad79f5cf4c91328ed9f64a454ded2acbf3


> JSON Files from Export API with "?" char for string with special chars 
> ---
>
> Key: ATLAS-3953
> URL: https://issues.apache.org/jira/browse/ATLAS-3953
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
> Environment: Apache Atlas 2.1.0 embedded HBASE and SOLR
>Reporter: Carlos Alberto Rocha Cardoso
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: 9fdc3ad0-46c2-430a-89c4-4a751d31c064.json, 
> ATLAS-3953-Export-ZipSink-Specify-character-endcodin.patch, 
> Asset_Imported.PNG, AtlasServer.PNG, 
> a5c148bf-5ab6-4c49-853e-855842102128.json, atlas_export.zip, path.zip
>
>
> The Export API returns a ZIP file with some JSON files describing Atlas 
> Entities and TypeDefs.
> I am having an issue where some special chars in JSON are being replaced by 
> "?" chars.
> An Entity name like "Distribuição" was exported in JSON file like 
> "Distribui??o". The special chars "çã" was replaced for the "??" chars.
> I tried to change the exported JSON file encoding and the request header for 
> Export API but without success.
> After analyzing the Atlas source code, especially the *splitAndWriteBytes* 
> method of the 
> *[ZipSink|https://github.com/apache/atlas/blob/cc601d7371fae1dbc16b55d1ca84f06b745700dc/repository/src/main/java/org/apache/atlas/repository/impexp/ZipSink.java]
>  class*, I thought if maybe the problem is because the *s.getBytes()* is 
> returning the JSON string to be written to ZIP with another encoding than 
> *UTF-8*, and maybe set the encode like *s.getBytes(StandardCharsets.UTF_8)* 
> could be a solution.
> It's my first contact with the Atlas source code, and I'm not a JAVA 
> programmer, so it's only a guess.
> I saw that it's possible to set the default to encode to the platform or JVM, 
> but how they said in this below discussion, perhaps this doesn't work 
> properly in all situations.
> [https://stackoverflow.com/questions/361975/setting-the-default-java-character-encoding]



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


[jira] [Commented] (ATLAS-3964) Atlas UI displays large numbers incorrectly

2020-09-30 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3964:


Commit e497dcff7b72f00788c41bc60ca44794ebd16ce8 in atlas's branch 
refs/heads/branch-2.0 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e497dcf ]

ATLAS-3964: Atlas UI displayes large numbers incorrectly

Signed-off-by: kevalbhatt 
(cherry picked from commit 545afb53d0eb4154162f3887cea2bf4a4d26e752)


> Atlas UI displays large numbers incorrectly
> ---
>
> Key: ATLAS-3964
> URL: https://issues.apache.org/jira/browse/ATLAS-3964
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Attachments: details.doc
>
>
> In the case of a type that has an attribute of type Long, and it contains a 
> very large number, the Atlas UI does not show the correct number.  
> Steps to reproduce:
> From the command line:
>  # create an entity type which has a field of type long
>  # create an entity of this same type and the value of the field should be 
> "1085741226505763426"
>  # Atlas will respond with the created entity, you will see that the field 
> value is correct
>  # now open the Atlas website and search for this same entity; you will see 
> the value displayed is "1085741226505763500"



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


[jira] [Commented] (ATLAS-3964) Atlas UI displays large numbers incorrectly

2020-09-30 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3964:


Commit 545afb53d0eb4154162f3887cea2bf4a4d26e752 in atlas's branch 
refs/heads/master from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=545afb5 ]

ATLAS-3964: Atlas UI displayes large numbers incorrectly

Signed-off-by: kevalbhatt 


> Atlas UI displays large numbers incorrectly
> ---
>
> Key: ATLAS-3964
> URL: https://issues.apache.org/jira/browse/ATLAS-3964
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Attachments: details.doc
>
>
> In the case of a type that has an attribute of type Long, and it contains a 
> very large number, the Atlas UI does not show the correct number.  
> Steps to reproduce:
> From the command line:
>  # create an entity type which has a field of type long
>  # create an entity of this same type and the value of the field should be 
> "1085741226505763426"
>  # Atlas will respond with the created entity, you will see that the field 
> value is correct
>  # now open the Atlas website and search for this same entity; you will see 
> the value displayed is "1085741226505763500"



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


[jira] [Commented] (ATLAS-3950) Read Type Auth : Classification, Business metadata , Entity types are able to have attributes of type which are not permissible to read

2020-09-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3950:


Commit 37111415cb72459a718e8f6feb5b6a5c764dd14c in atlas's branch 
refs/heads/branch-2.0 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3711141 ]

ATLAS-3950 : Authorize for Read Type for Classification, Business metadata , 
Entity typesdef attributes.

Signed-off-by: nixonrodrigues 
(cherry picked from commit d4a50aadfc2e7076d8e5281f9be60fad4c5c232d)


> Read Type Auth : Classification, Business metadata , Entity types are able to 
> have attributes of type which are not permissible to read
> ---
>
> Key: ATLAS-3950
> URL: https://issues.apache.org/jira/browse/ATLAS-3950
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 3.0.0
>
>
> Steps to reproduce :-
> hrt_qa has :
> CRUD permissions on hive_table type
> CRUD permissions on all business_metadata type.
> hrt_qa creates a business metadata bm1
> hrt_qa is able to create an attribute for bm1 - say attrib1 which allows 
> Applicable types to be anything. UI displays only hive_table but through REST 
> , hrt_qa is able to add any type as Applicable type.
>  
> Same for classifications :
> hrt_qa has CRUD permissions on all classification types but read only for 
> hive_table entity type.
> Through REST , hrt_qa is able to add all types as entityTypes.
> Example REST call where allowed entity types are hive_table and hdfs_path :
>  
> {code:java}
> /api/atlas/v2/types/typedefs?type=classification
> { "classificationDefs":[
> { "name":"PII", "description":"PII", "superTypes":[ ], "attributeDefs":[ ], 
> "entityTypes":[ "hdfs_path", "hive_table" ], "category":"CLASSIFICATION", 
> "guid":"123456789" }
> ], "entityDefs":[
> ], "enumDefs":[
> ], "structDefs":[
> ]
>  }
>   
> {code}
>  
>  Call succeeds with 200 Ok.
>  
> For Entity type:
> Updating hive_table entity typedef with a new attribute of  type hdfs_path is 
> allowed.
>  
> Expected is , in all 3 cases of business metadata , classification and 
> entity, response to be authorization denied because hdfs_path type provided.



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


[jira] [Commented] (ATLAS-3950) Read Type Auth : Classification, Business metadata , Entity types are able to have attributes of type which are not permissible to read

2020-09-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3950:


Commit d4a50aadfc2e7076d8e5281f9be60fad4c5c232d in atlas's branch 
refs/heads/master from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d4a50aa ]

ATLAS-3950 : Authorize for Read Type for Classification, Business metadata , 
Entity typesdef attributes.

Signed-off-by: nixonrodrigues 


> Read Type Auth : Classification, Business metadata , Entity types are able to 
> have attributes of type which are not permissible to read
> ---
>
> Key: ATLAS-3950
> URL: https://issues.apache.org/jira/browse/ATLAS-3950
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 3.0.0
>
>
> Steps to reproduce :-
> hrt_qa has :
> CRUD permissions on hive_table type
> CRUD permissions on all business_metadata type.
> hrt_qa creates a business metadata bm1
> hrt_qa is able to create an attribute for bm1 - say attrib1 which allows 
> Applicable types to be anything. UI displays only hive_table but through REST 
> , hrt_qa is able to add any type as Applicable type.
>  
> Same for classifications :
> hrt_qa has CRUD permissions on all classification types but read only for 
> hive_table entity type.
> Through REST , hrt_qa is able to add all types as entityTypes.
> Example REST call where allowed entity types are hive_table and hdfs_path :
>  
> {code:java}
> /api/atlas/v2/types/typedefs?type=classification
> { "classificationDefs":[
> { "name":"PII", "description":"PII", "superTypes":[ ], "attributeDefs":[ ], 
> "entityTypes":[ "hdfs_path", "hive_table" ], "category":"CLASSIFICATION", 
> "guid":"123456789" }
> ], "entityDefs":[
> ], "enumDefs":[
> ], "structDefs":[
> ]
>  }
>   
> {code}
>  
>  Call succeeds with 200 Ok.
>  
> For Entity type:
> Updating hive_table entity typedef with a new attribute of  type hdfs_path is 
> allowed.
>  
> Expected is , in all 3 cases of business metadata , classification and 
> entity, response to be authorization denied because hdfs_path type provided.



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


[jira] [Commented] (ATLAS-3962) Include business metadata def header in typdefs headers API

2020-09-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3962:


Commit d7efa6e38021c7bc45210680bedf29b8aaa59609 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d7efa6e ]

ATLAS-3962 : Include business metadata def header in typdefs headers API

Change-Id: I52783f36c59509fefeb75f56f3391a7ea6a261ce
(cherry picked from commit 7ae0bea9680d78605e1362dfbea288518f0e50ff)


> Include business metadata def header in typdefs headers API
> ---
>
> Key: ATLAS-3962
> URL: https://issues.apache.org/jira/browse/ATLAS-3962
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> While trying to fetch headers of all types, data about business metadata is 
> not fetched via "*atlas/v2/types/typedefs/headers*"
> We could verify is there is business metadata in 
> "api/atlas/v2/types/typedefs?type=business_metadata" though



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


[jira] [Commented] (ATLAS-3952) Authorize Super And SubTypes and depend entityType for type-read access while creating Classificationdef

2020-09-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3952:


Commit f220bceab3fb8033a77c94a5f043550f995ce984 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f220bce ]

ATLAS-3952 :- Authorize Super And SubTypes and depend entityType for type-read 
access while creating Classificationdef

Change-Id: Ieb78c49615173db7eb1ce4911700799dfa1083bd
(cherry picked from commit 86e9149b031d62536fce6bb6fa815536d57144bc)


> Authorize Super And SubTypes and depend entityType for type-read access while 
> creating Classificationdef
> 
>
> Key: ATLAS-3952
> URL: https://issues.apache.org/jira/browse/ATLAS-3952
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3952.patch
>
>
> User is able to create a type with a super type though he doesn't have read 
> permission on super type , subtype



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


[jira] [Commented] (ATLAS-3962) Include business metadata def header in typdefs headers API

2020-09-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3962:


Commit 7ae0bea9680d78605e1362dfbea288518f0e50ff in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7ae0bea ]

ATLAS-3962 : Include business metadata def header in typdefs headers API

Change-Id: I52783f36c59509fefeb75f56f3391a7ea6a261ce


> Include business metadata def header in typdefs headers API
> ---
>
> Key: ATLAS-3962
> URL: https://issues.apache.org/jira/browse/ATLAS-3962
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> While trying to fetch headers of all types, data about business metadata is 
> not fetched via "*atlas/v2/types/typedefs/headers*"
> We could verify is there is business metadata in 
> "api/atlas/v2/types/typedefs?type=business_metadata" though



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


[jira] [Commented] (ATLAS-3952) Authorize Super And SubTypes and depend entityType for type-read access while creating Classificationdef

2020-09-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3952:


Commit 86e9149b031d62536fce6bb6fa815536d57144bc in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=86e9149 ]

ATLAS-3952 :- Authorize Super And SubTypes and depend entityType for type-read 
access while creating Classificationdef

Change-Id: Ieb78c49615173db7eb1ce4911700799dfa1083bd


> Authorize Super And SubTypes and depend entityType for type-read access while 
> creating Classificationdef
> 
>
> Key: ATLAS-3952
> URL: https://issues.apache.org/jira/browse/ATLAS-3952
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3952.patch
>
>
> User is able to create a type with a super type though he doesn't have read 
> permission on super type , subtype



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


[jira] [Commented] (ATLAS-3959) Upgrade Atlas to Spring Framework version 4.3.16.release

2020-09-28 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3959:


Commit 3a6c6bd085d71a4301c6184ad2478267de0f5a96 in atlas's branch 
refs/heads/branch-0.8 from chaitali borole
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3a6c6bd ]

ATLAS-3959 : Upgrade Atlas to Spring Framework version 4.3.16.release

Signed-off-by: nixonrodrigues 


> Upgrade Atlas to Spring Framework version 4.3.16.release
> 
>
> Key: ATLAS-3959
> URL: https://issues.apache.org/jira/browse/ATLAS-3959
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8.1
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 0.8.1
>
> Attachments: ATLAS-3959.patch
>
>
> Existing Spring version 4.3.8.release is vulnerable to CVE-2018-1270



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


[jira] [Commented] (ATLAS-3938) Import Hive Script: Support deletion of non existing database and table entities

2020-09-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3938:


Commit 1097d97c7e70f304ca1fb9bb9e9480a657ab5de4 in atlas's branch 
refs/heads/branch-0.8 from Pinal
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1097d97 ]

ATLAS-3938 : Deletion of non existing hive entities

Signed-off-by: nixonrodrigues 


> Import Hive Script:  Support deletion of non existing database and table 
> entities
> -
>
> Key: ATLAS-3938
> URL: https://issues.apache.org/jira/browse/ATLAS-3938
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> *Problem* : Whenever database or table is dropped in hive, and HiveHook is 
> not enabled, we dont have anyway to get the database and table sync with hive.
> *Workaround* : Added support to delete database and table entities present in 
> Atlas, but not in Hive.
> *Usage* : ./import-hive.sh -deleteNonExisting
> *NOTE : atlas.hook.hive.page.limit* property is added to configure the 
> pageSize/limit while fetching entities from Atlas



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


[jira] [Commented] (ATLAS-3949) Relationship search API, add parameter to get classification attributes in search results

2020-09-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3949:


Commit 9c1145e4d73a16f682c03fa85d29e2d758cefc5a in atlas's branch 
refs/heads/branch-2.0 from Pinal
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9c1145e ]

ATLAS-3949 : Relationship search API, add parameter to get classification 
attributes in search results

Signed-off-by: nixonrodrigues 
(cherry picked from commit ec39c1e6207d2f875b3dc9d5a8a9818c3c9c46a5)


> Relationship search API, add parameter to get classification attributes in 
> search results
> -
>
> Key: ATLAS-3949
> URL: https://issues.apache.org/jira/browse/ATLAS-3949
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> *Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
> Relationship search Api to get all attributes of the classification 
> associated to the entity.
> *Example Request api:* 
> /api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true
> *Example Response api:* 
> {code:java}
> {
>"queryType":"RELATIONSHIP",
>"entities":[
>   {
>  "typeName":"hive_table",
>  "attributes":{
> "createTime":160062660,
> "qualifiedName":"table@db1",
> "name":"table1"
>  },
>  "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
>  "status":"ACTIVE",
>  "displayText":"table1",
>  "classificationNames":[
> "Dimension"
>  ],
>  "classifications":[
> {
>"typeName":"Dimension",
>"entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
>"entityStatus":"ACTIVE",
>"propagate":true,
>"validityPeriods":[
>   
>],
>"removePropagationsOnEntityDelete":false
> }
>  ],
>  "meaningNames":[
> 
>  ],
>  "meanings":[
> 
>  ],
>  "isIncomplete":false,
>  "labels":[
> 
>  ]
>   }
>],
>"approximateCount":-1
> }
> {code}



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


[jira] [Commented] (ATLAS-3949) Relationship search API, add parameter to get classification attributes in search results

2020-09-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3949:


Commit ec39c1e6207d2f875b3dc9d5a8a9818c3c9c46a5 in atlas's branch 
refs/heads/master from Pinal
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ec39c1e ]

ATLAS-3949 : Relationship search API, add parameter to get classification 
attributes in search results

Signed-off-by: nixonrodrigues 


> Relationship search API, add parameter to get classification attributes in 
> search results
> -
>
> Key: ATLAS-3949
> URL: https://issues.apache.org/jira/browse/ATLAS-3949
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> *Improvement:* Adding boolean parameter 'includeClassificationAttributes' in 
> Relationship search Api to get all attributes of the classification 
> associated to the entity.
> *Example Request api:* 
> /api/atlas/v2/search/relationship?guid=\{guid}=tables=10=true
> *Example Response api:* 
> {code:java}
> {
>"queryType":"RELATIONSHIP",
>"entities":[
>   {
>  "typeName":"hive_table",
>  "attributes":{
> "createTime":160062660,
> "qualifiedName":"table@db1",
> "name":"table1"
>  },
>  "guid":"9893504f-095d-47e3-abf8-fd79069252f7",
>  "status":"ACTIVE",
>  "displayText":"table1",
>  "classificationNames":[
> "Dimension"
>  ],
>  "classifications":[
> {
>"typeName":"Dimension",
>"entityGuid":"9893504f-095d-47e3-abf8-fd79069252f7",
>"entityStatus":"ACTIVE",
>"propagate":true,
>"validityPeriods":[
>   
>],
>"removePropagationsOnEntityDelete":false
> }
>  ],
>  "meaningNames":[
> 
>  ],
>  "meanings":[
> 
>  ],
>  "isIncomplete":false,
>  "labels":[
> 
>  ]
>   }
>],
>"approximateCount":-1
> }
> {code}



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


[jira] [Commented] (ATLAS-3955) Read Type Auth, UI : detailsPage doesn't load for user who has read permission for entity but no read auth for entity's type

2020-09-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3955:


Commit 598a726fab52caa886741c7153459975efa7068d in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=598a726 ]

ATLAS-3955: Read Type Auth, UI : detailsPage doesn't load for user who has read 
permission for entity but no read auth for entity's type

(cherry picked from commit 23c33d14d0d8e11977c38377668030ae2bbe257b)


> Read Type Auth, UI : detailsPage doesn't load for user who has read 
> permission for entity but no read auth for entity's type
> 
>
> Key: ATLAS-3955
> URL: https://issues.apache.org/jira/browse/ATLAS-3955
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3955-1.patch, ATLAS-3955.patch
>
>
> -
> Simple scenario
> -
> 1 . hive_table employee is created.
> 2. USER has permissions to read the employee table entity
> 3. USER doesn't have permissions to read type hive_table
> 4. USER logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists 
> the hive_table entity "employee"
> 5. Clicking on it, UI throws following error in Console tab and UI keeps 
> loading.
> {code:java}
> DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot 
> read property 'toJSON' of undefined
> at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1)
> at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
> at N.d.reset (backbone-min.js?bust=1600212682027:1)
> at Object. (backbone.paginator.min.js?bust=1600212682027:1)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1) {code}



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


[jira] [Commented] (ATLAS-3955) Read Type Auth, UI : detailsPage doesn't load for user who has read permission for entity but no read auth for entity's type

2020-09-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3955:


Commit 23c33d14d0d8e11977c38377668030ae2bbe257b in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=23c33d1 ]

ATLAS-3955: Read Type Auth, UI : detailsPage doesn't load for user who has read 
permission for entity but no read auth for entity's type


> Read Type Auth, UI : detailsPage doesn't load for user who has read 
> permission for entity but no read auth for entity's type
> 
>
> Key: ATLAS-3955
> URL: https://issues.apache.org/jira/browse/ATLAS-3955
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3955-1.patch, ATLAS-3955.patch
>
>
> -
> Simple scenario
> -
> 1 . hive_table employee is created.
> 2. USER has permissions to read the employee table entity
> 3. USER doesn't have permissions to read type hive_table
> 4. USER logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists 
> the hive_table entity "employee"
> 5. Clicking on it, UI throws following error in Console tab and UI keeps 
> loading.
> {code:java}
> DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot 
> read property 'toJSON' of undefined
> at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1)
> at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
> at N.d.reset (backbone-min.js?bust=1600212682027:1)
> at Object. (backbone.paginator.min.js?bust=1600212682027:1)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1) {code}



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


[jira] [Commented] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-09-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3934:


Commit e41a4b45774ddd93d232a748d9e2e75bf188d68a in atlas's branch 
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e41a4b4 ]

ATLAS-3934: Dockerfile: updated default to build from local repo (instead of 
from github) - #2

(cherry picked from commit d0e246a7096d870b1bc6ee3dd46428bd3bf4b1e6)


> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3934.patch
>
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Commented] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-09-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3934:


Commit d0e246a7096d870b1bc6ee3dd46428bd3bf4b1e6 in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d0e246a ]

ATLAS-3934: Dockerfile: updated default to build from local repo (instead of 
from github) - #2


> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3934.patch
>
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Commented] (ATLAS-3947) Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES types

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3947:


Commit 74229d87043bc55a4dd83cad37db59031d624af5 in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Nixon 
Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=74229d8 ]

ATLAS-3947 : Skip authorization for read of _ALL_ENTITY_TYPES and 
_ALL_CLASSIFICATION_TYPES types

Change-Id: Iecd8ab427510cb37aaff99e420c25a579631dd4d


> Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES 
> types
> -
>
> Key: ATLAS-3947
> URL: https://issues.apache.org/jira/browse/ATLAS-3947
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3947.patch
>
>
> Skip authorization for read of _ALL_ENTITY_TYPES type of entity type  and 
> _ALL_CLASSIFICATION_TYPES type of classification type.
>  This are internally required by for system attributes search. 



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


[jira] [Commented] (ATLAS-3944) Logs of import scripts should go to Atlas default log directory

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3944:


Commit 62c682b344c245015bca4e3d6bf7f55b5394a5e2 in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=62c682b ]

ATLAS-3944: Logs of import scripts should go to Atlas default log directory

Signed-off-by: Ashutosh Mestry 


> Logs of import scripts should go to Atlas default log directory
> ---
>
> Key: ATLAS-3944
> URL: https://issues.apache.org/jira/browse/ATLAS-3944
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk, 2.1.0
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Fix For: trunk
>
> Attachments: 0001-Setting-default-log-directory-to-var-log-atlas.patch
>
>
> Import scripts like import-hbase.sh try to dump logs in a log directory 
> inside the base directory. Most of the users running import scripts have 
> read-only access to the base directory, this leads to the following error 
> exception.
> java.io.FileNotFoundException: 
> /opt/cloudera/parcels/CDH/lib/atlas/logs/import-hbase.log (No such file or 
> directory)
> Although there is a mechanism to set the log location to the desired 
> directory using env variable ATLAS_LOG_DIR, but by default, the script must 
> try to dump logs in Atlas default logs directory (/var/log/atlas)
>  



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


[jira] [Commented] (ATLAS-3911) UI: Type system management

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3911:


Commit b8956dfd00b788ef90b79612a36669f5c6106855 in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b8956df ]

ATLAS-3911: UI: Type system managment


> UI: Type system management
> --
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911-1.patch, ATLAS-3911-2.patch, 
> ATLAS-3911.patch, Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



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


[jira] [Commented] (ATLAS-3948) Entity Creation: Index Consistency: Java Patch Handler: Provide Option to Disable

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3948:


Commit eccc37623e7c3d43e1aa494f88a5ad155fe9c123 in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Ashutosh 
Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=eccc376 ]

ATLAS-3948: Entity Creation: Index Consistency: Java Patch Handler: Provide 
Option to Disable


> Entity Creation: Index Consistency: Java Patch Handler: Provide Option to 
> Disable
> -
>
> Key: ATLAS-3948
> URL: https://issues.apache.org/jira/browse/ATLAS-3948
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3948-index-consistency-conditional.patch
>
>
> *Background*
> The ATLAS-3907 provided ability to apply index consistency to existing 
> indexes via Java patch handler.
> However, when _atlas.graph.storage.consistency-lock.enabled=false_ this patch 
> still gets applied.
> *Solution*
> Check for the property in Java patch handler and avoid applying it if the 
> property is set to false.



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


[jira] [Commented] (ATLAS-3946) Filter TypeDefs in Metrics API and show data accordingly

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3946:


Commit 4bc1c04adeba25254fce924e318c26fc9b72a8dd in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Nixon 
Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4bc1c04 ]

ATLAS-3946 : Filter TypeDefs in Metrics API and show types data accordingly


> Filter TypeDefs in Metrics API and show data accordingly
> 
>
> Key: ATLAS-3946
> URL: https://issues.apache.org/jira/browse/ATLAS-3946
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Filter TypeDefs in Metrics API and show data accordingly, currently data is 
> shown for all types even if user do not have access to those types.



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


[jira] [Commented] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3934:


Commit 9b1d4c387fb56d08bfc86150b0cff7d071540109 in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Madhan 
Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9b1d4c3 ]

ATLAS-3934: docker scripts to build and run Apache Atlas in containers


> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3934.patch
>
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Commented] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3945:


Commit e6c382680d1a3fa3284b5c9a9026264fc5bd3957 in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e6c3826 ]

ATLAS-3945: UI: Entity details page, Show N/A for date if date value is 0 or 
null

Signed-off-by: Nikhil Bonte 


> UI: Entity details page,  Show N/A for date if date value is 0 or null
> --
>
> Key: ATLAS-3945
> URL: https://issues.apache.org/jira/browse/ATLAS-3945
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3945.patch
>
>




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


[jira] [Commented] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3827:


Commit ee80e6a675317f15a99429d509ffd49670d5df0d in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ee80e6a ]

ATLAS-3827: UI: Use moment date format instead of default date format.

Signed-off-by: Nikhil Bonte 


> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827-1.patch, ATLAS-3827.patch, 
> image-2020-09-16-17-11-33-386.png, image-2020-09-16-17-12-04-512.png, 
> new_date_format.png
>
>
>  
> UI configured to use the following date formats:
> {code:java}
>  /MM/DD
>  /MM/DD HH:mm:ss
>  MM/DD/ h:mm A z
> {code}



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


[jira] [Commented] (ATLAS-3911) UI: Type system management

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3911:


Commit c71ba1e851564993377c8156f90e47b5b3f471b0 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c71ba1e ]

ATLAS-3911: UI: Type system managment

(cherry picked from commit b8956dfd00b788ef90b79612a36669f5c6106855)


> UI: Type system management
> --
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911-1.patch, ATLAS-3911-2.patch, 
> ATLAS-3911.patch, Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



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


[jira] [Commented] (ATLAS-3939) Add build profile for berkeleydb-solr

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3939:


Commit 7690e51d10f008c1e13a4c85f9aa8821fee33f4a in atlas's branch 
refs/heads/dependabot/npm_and_yarn/dashboardv2/bootstrap-3.4.1 from Madhan 
Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7690e51 ]

ATLAS-3939: added profile berkeley-solr


> Add build profile for berkeleydb-solr
> -
>
> Key: ATLAS-3939
> URL: https://issues.apache.org/jira/browse/ATLAS-3939
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3939.patch
>
>
> Atlas supports a number of build profiles, like 
> external-hbase-sol/embedded-hbase-solr/embedded-cassandra-solr/berkeley-elasticsearch,
>  for various combinations of backend stores an index stores. This should be 
> extended to support berkeley-solr as well; this profile can be useful for 
> dev/testing of Atlas.



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


[jira] [Commented] (ATLAS-3911) UI: Type system management

2020-09-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3911:


Commit b8956dfd00b788ef90b79612a36669f5c6106855 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b8956df ]

ATLAS-3911: UI: Type system managment


> UI: Type system management
> --
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911-1.patch, ATLAS-3911-2.patch, 
> ATLAS-3911.patch, Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



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


[jira] [Commented] (ATLAS-3947) Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES types

2020-09-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3947:


Commit b1bbaee045c6d629351b6902e13bb36ffa493e6c in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b1bbaee ]

ATLAS-3947 : Skip authorization for read of _ALL_ENTITY_TYPES and 
_ALL_CLASSIFICATION_TYPES types

Change-Id: Iecd8ab427510cb37aaff99e420c25a579631dd4d
(cherry picked from commit 74229d87043bc55a4dd83cad37db59031d624af5)


> Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES 
> types
> -
>
> Key: ATLAS-3947
> URL: https://issues.apache.org/jira/browse/ATLAS-3947
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3947.patch
>
>
> Skip authorization for read of _ALL_ENTITY_TYPES type of entity type  and 
> _ALL_CLASSIFICATION_TYPES type of classification type.
>  This are internally required by for system attributes search. 



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


[jira] [Commented] (ATLAS-3946) Filter TypeDefs in Metrics API and show data accordingly

2020-09-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3946:


Commit cc13abc82987872c539badc1831af7d471b7259c in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=cc13abc ]

ATLAS-3946 : Filter TypeDefs in Metrics API and show types data accordingly

(cherry picked from commit 4bc1c04adeba25254fce924e318c26fc9b72a8dd)


> Filter TypeDefs in Metrics API and show data accordingly
> 
>
> Key: ATLAS-3946
> URL: https://issues.apache.org/jira/browse/ATLAS-3946
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Filter TypeDefs in Metrics API and show data accordingly, currently data is 
> shown for all types even if user do not have access to those types.



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


[jira] [Commented] (ATLAS-3947) Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES types

2020-09-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3947:


Commit 74229d87043bc55a4dd83cad37db59031d624af5 in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=74229d8 ]

ATLAS-3947 : Skip authorization for read of _ALL_ENTITY_TYPES and 
_ALL_CLASSIFICATION_TYPES types

Change-Id: Iecd8ab427510cb37aaff99e420c25a579631dd4d


> Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES 
> types
> -
>
> Key: ATLAS-3947
> URL: https://issues.apache.org/jira/browse/ATLAS-3947
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3947.patch
>
>
> Skip authorization for read of _ALL_ENTITY_TYPES type of entity type  and 
> _ALL_CLASSIFICATION_TYPES type of classification type.
>  This are internally required by for system attributes search. 



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


[jira] [Commented] (ATLAS-3946) Filter TypeDefs in Metrics API and show data accordingly

2020-09-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3946:


Commit 4bc1c04adeba25254fce924e318c26fc9b72a8dd in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4bc1c04 ]

ATLAS-3946 : Filter TypeDefs in Metrics API and show types data accordingly


> Filter TypeDefs in Metrics API and show data accordingly
> 
>
> Key: ATLAS-3946
> URL: https://issues.apache.org/jira/browse/ATLAS-3946
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Filter TypeDefs in Metrics API and show data accordingly, currently data is 
> shown for all types even if user do not have access to those types.



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


[jira] [Commented] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-09-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3934:


Commit 182c1bdb35d3817ddb82511da1c39acd971eedbc in atlas's branch 
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=182c1bd ]

ATLAS-3934: docker scripts to build and run Apache Atlas in containers

(cherry picked from commit 9b1d4c387fb56d08bfc86150b0cff7d071540109)


> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3934.patch
>
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Commented] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-09-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3934:


Commit 9b1d4c387fb56d08bfc86150b0cff7d071540109 in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9b1d4c3 ]

ATLAS-3934: docker scripts to build and run Apache Atlas in containers


> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3934.patch
>
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Commented] (ATLAS-3939) Add build profile for berkeleydb-solr

2020-09-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3939:


Commit 58ea1a8baaf163c973d77585b29ee192650cc863 in atlas's branch 
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=58ea1a8 ]

ATLAS-3939: added profile berkeley-solr

(cherry picked from commit 7690e51d10f008c1e13a4c85f9aa8821fee33f4a)


> Add build profile for berkeleydb-solr
> -
>
> Key: ATLAS-3939
> URL: https://issues.apache.org/jira/browse/ATLAS-3939
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3939.patch
>
>
> Atlas supports a number of build profiles, like 
> external-hbase-sol/embedded-hbase-solr/embedded-cassandra-solr/berkeley-elasticsearch,
>  for various combinations of backend stores an index stores. This should be 
> extended to support berkeley-solr as well; this profile can be useful for 
> dev/testing of Atlas.



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


[jira] [Commented] (ATLAS-3939) Add build profile for berkeleydb-solr

2020-09-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3939:


Commit 7690e51d10f008c1e13a4c85f9aa8821fee33f4a in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7690e51 ]

ATLAS-3939: added profile berkeley-solr


> Add build profile for berkeleydb-solr
> -
>
> Key: ATLAS-3939
> URL: https://issues.apache.org/jira/browse/ATLAS-3939
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3939.patch
>
>
> Atlas supports a number of build profiles, like 
> external-hbase-sol/embedded-hbase-solr/embedded-cassandra-solr/berkeley-elasticsearch,
>  for various combinations of backend stores an index stores. This should be 
> extended to support berkeley-solr as well; this profile can be useful for 
> dev/testing of Atlas.



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


[jira] [Commented] (ATLAS-3948) Entity Creation: Index Consistency: Java Patch Handler: Provide Option to Disable

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3948:


Commit a2ea7d302e1ef8d6e9dd6f88e25749233a40e0f6 in atlas's branch 
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a2ea7d3 ]

ATLAS-3948: Entity Creation: Index Consistency: Java Patch Handler: Provide 
Option to Disable


> Entity Creation: Index Consistency: Java Patch Handler: Provide Option to 
> Disable
> -
>
> Key: ATLAS-3948
> URL: https://issues.apache.org/jira/browse/ATLAS-3948
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3948-index-consistency-conditional.patch
>
>
> *Background*
> The ATLAS-3907 provided ability to apply index consistency to existing 
> indexes via Java patch handler.
> However, when _atlas.graph.storage.consistency-lock.enabled=false_ this patch 
> still gets applied.
> *Solution*
> Check for the property in Java patch handler and avoid applying it if the 
> property is set to false.



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


[jira] [Commented] (ATLAS-3948) Entity Creation: Index Consistency: Java Patch Handler: Provide Option to Disable

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3948:


Commit eccc37623e7c3d43e1aa494f88a5ad155fe9c123 in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=eccc376 ]

ATLAS-3948: Entity Creation: Index Consistency: Java Patch Handler: Provide 
Option to Disable


> Entity Creation: Index Consistency: Java Patch Handler: Provide Option to 
> Disable
> -
>
> Key: ATLAS-3948
> URL: https://issues.apache.org/jira/browse/ATLAS-3948
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3948-index-consistency-conditional.patch
>
>
> *Background*
> The ATLAS-3907 provided ability to apply index consistency to existing 
> indexes via Java patch handler.
> However, when _atlas.graph.storage.consistency-lock.enabled=false_ this patch 
> still gets applied.
> *Solution*
> Check for the property in Java patch handler and avoid applying it if the 
> property is set to false.



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


[jira] [Commented] (ATLAS-3944) Logs of import scripts should go to Atlas default log directory

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3944:


Commit 59a609a277971c246c7892a9e76d6a75e001d8a6 in atlas's branch 
refs/heads/branch-2.0 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=59a609a ]

ATLAS-3944: Logs of import scripts should go to Atlas default log directory

Signed-off-by: Ashutosh Mestry 


> Logs of import scripts should go to Atlas default log directory
> ---
>
> Key: ATLAS-3944
> URL: https://issues.apache.org/jira/browse/ATLAS-3944
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk, 2.1.0
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Fix For: trunk
>
> Attachments: 0001-Setting-default-log-directory-to-var-log-atlas.patch
>
>
> Import scripts like import-hbase.sh try to dump logs in a log directory 
> inside the base directory. Most of the users running import scripts have 
> read-only access to the base directory, this leads to the following error 
> exception.
> java.io.FileNotFoundException: 
> /opt/cloudera/parcels/CDH/lib/atlas/logs/import-hbase.log (No such file or 
> directory)
> Although there is a mechanism to set the log location to the desired 
> directory using env variable ATLAS_LOG_DIR, but by default, the script must 
> try to dump logs in Atlas default logs directory (/var/log/atlas)
>  



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


[jira] [Commented] (ATLAS-3944) Logs of import scripts should go to Atlas default log directory

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3944:


Commit 62c682b344c245015bca4e3d6bf7f55b5394a5e2 in atlas's branch 
refs/heads/master from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=62c682b ]

ATLAS-3944: Logs of import scripts should go to Atlas default log directory

Signed-off-by: Ashutosh Mestry 


> Logs of import scripts should go to Atlas default log directory
> ---
>
> Key: ATLAS-3944
> URL: https://issues.apache.org/jira/browse/ATLAS-3944
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk, 2.1.0
>Reporter: Deep Singh
>Assignee: Deep Singh
>Priority: Major
> Fix For: trunk
>
> Attachments: 0001-Setting-default-log-directory-to-var-log-atlas.patch
>
>
> Import scripts like import-hbase.sh try to dump logs in a log directory 
> inside the base directory. Most of the users running import scripts have 
> read-only access to the base directory, this leads to the following error 
> exception.
> java.io.FileNotFoundException: 
> /opt/cloudera/parcels/CDH/lib/atlas/logs/import-hbase.log (No such file or 
> directory)
> Although there is a mechanism to set the log location to the desired 
> directory using env variable ATLAS_LOG_DIR, but by default, the script must 
> try to dump logs in Atlas default logs directory (/var/log/atlas)
>  



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


[jira] [Commented] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3827:


Commit d6d590a14d9005a52e01ad923e2c07dacab28f49 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d6d590a ]

ATLAS-3827: UI: Use moment date format instead of default date format.

Signed-off-by: Nikhil Bonte 
(cherry picked from commit ee80e6a675317f15a99429d509ffd49670d5df0d)


> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827-1.patch, ATLAS-3827.patch, 
> image-2020-09-16-17-11-33-386.png, image-2020-09-16-17-12-04-512.png, 
> new_date_format.png
>
>
>  
> UI configured to use the following date formats:
> {code:java}
>  /MM/DD
>  /MM/DD HH:mm:ss
>  MM/DD/ h:mm A z
> {code}



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


[jira] [Commented] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3945:


Commit cab21a8cd821e02d352cb091405e0906af6312b2 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=cab21a8 ]

ATLAS-3945: UI: Entity details page, Show N/A for date if date value is 0 or 
null

Signed-off-by: Nikhil Bonte 
(cherry picked from commit e6c382680d1a3fa3284b5c9a9026264fc5bd3957)


> UI: Entity details page,  Show N/A for date if date value is 0 or null
> --
>
> Key: ATLAS-3945
> URL: https://issues.apache.org/jira/browse/ATLAS-3945
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3945.patch
>
>




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


[jira] [Commented] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3945:


Commit e6c382680d1a3fa3284b5c9a9026264fc5bd3957 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e6c3826 ]

ATLAS-3945: UI: Entity details page, Show N/A for date if date value is 0 or 
null

Signed-off-by: Nikhil Bonte 


> UI: Entity details page,  Show N/A for date if date value is 0 or null
> --
>
> Key: ATLAS-3945
> URL: https://issues.apache.org/jira/browse/ATLAS-3945
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3945.patch
>
>




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


[jira] [Commented] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-17 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3827:


Commit ee80e6a675317f15a99429d509ffd49670d5df0d in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ee80e6a ]

ATLAS-3827: UI: Use moment date format instead of default date format.

Signed-off-by: Nikhil Bonte 


> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827-1.patch, ATLAS-3827.patch, 
> image-2020-09-16-17-11-33-386.png, image-2020-09-16-17-12-04-512.png, 
> new_date_format.png
>
>
>  
> UI configured to use the following date formats:
> {code:java}
>  /MM/DD
>  /MM/DD HH:mm:ss
>  MM/DD/ h:mm A z
> {code}



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


[jira] [Commented] (ATLAS-3940) Upgrade snakeyaml to a version without CVE-2017-18640

2020-09-16 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3940:


Commit d330da8763242faa955bb665cb74c96c5b34e7a2 in atlas's branch 
refs/heads/branch-2.0 from Rahul Nandi
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d330da8 ]

ATLAS-3940 : Upgrade snakeyaml to a version without CVE-2017-18640 (#110)

(cherry picked from commit d555c02ba283312e2d9b014b5d68a17da3661525)


> Upgrade snakeyaml to a version without CVE-2017-18640 
> --
>
> Key: ATLAS-3940
> URL: https://issues.apache.org/jira/browse/ATLAS-3940
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Maven package cassandra-all has transitive dependency on 
> org.yaml:snakeyaml:1.11 which has 
> CVE-2017-18640:https://nvd.nist.gov/vuln/detail/CVE-2017-18640



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


[jira] [Commented] (ATLAS-3942) Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef while delete-type

2020-09-16 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3942:


Commit 51ca7b6918064c22fb196a530b0eb838b2d5d112 in atlas's branch 
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=51ca7b6 ]

ATLAS-3942: delete-type fails if the user doesn't have permission for type-read

Signed-off-by: nixonrodrigues 
(cherry picked from commit 1bfaf7add99e30130cabe20e9cedf2f90ca96e0d)


> Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef 
> while delete-type
> ---
>
> Key: ATLAS-3942
> URL: https://issues.apache.org/jira/browse/ATLAS-3942
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3942.patch
>
>
> delete-type is triggering read-type authz access internally called by method 
> {{getByName}}.
> Considering refactoring {{AtlasTypeDefGraphStore}} code to remove authz check 
> reading typedef internally.



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


[jira] [Commented] (ATLAS-3942) Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef while delete-type

2020-09-16 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3942:


Commit 1bfaf7add99e30130cabe20e9cedf2f90ca96e0d in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1bfaf7a ]

ATLAS-3942: delete-type fails if the user doesn't have permission for type-read

Signed-off-by: nixonrodrigues 


> Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef 
> while delete-type
> ---
>
> Key: ATLAS-3942
> URL: https://issues.apache.org/jira/browse/ATLAS-3942
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3942.patch
>
>
> delete-type is triggering read-type authz access internally called by method 
> {{getByName}}.
> Considering refactoring {{AtlasTypeDefGraphStore}} code to remove authz check 
> reading typedef internally.



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


[jira] [Commented] (ATLAS-3940) Upgrade snakeyaml to a version without CVE-2017-18640

2020-09-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3940:


Commit d555c02ba283312e2d9b014b5d68a17da3661525 in atlas's branch 
refs/heads/master from Rahul Nandi
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d555c02 ]

ATLAS-3940 : Upgrade snakeyaml to a version without CVE-2017-18640 (#110)



> Upgrade snakeyaml to a version without CVE-2017-18640 
> --
>
> Key: ATLAS-3940
> URL: https://issues.apache.org/jira/browse/ATLAS-3940
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Maven package cassandra-all has transitive dependency on 
> org.yaml:snakeyaml:1.11 which has 
> CVE-2017-18640:https://nvd.nist.gov/vuln/detail/CVE-2017-18640



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


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

2020-09-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3935:


Commit 4e422ce52cef9f7212186abeab52d37fba094488 in atlas's branch 
refs/heads/branch-2.0 from Mandar Ambawane
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4e422ce ]

ATLAS-3935 : Use Audit framework to capture audit entries for Import/Export 
operations

(cherry picked from commit 01e9ccef466643a01f97900b97e69772dd8c4ea9)


> 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
>
> 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-3935) Use Audit framework to capture audit entries for Import/Export operations

2020-09-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3935:


Commit 01e9ccef466643a01f97900b97e69772dd8c4ea9 in atlas's branch 
refs/heads/master from Mandar Ambawane
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=01e9cce ]

ATLAS-3935 : Use Audit framework to capture audit entries for Import/Export 
operations


> 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
>
> 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-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-09-03 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3925:


Commit 8b86c7a10590ce94aa82f8a1fa304065853223a8 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8b86c7a ]

ATLAS-3925: UI: (Regression) Properties with value Null not showing N/A #2

(cherry picked from commit 61b7a077bc541aad27ceadb8c55b4d568b376e3c)


> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925-1.patch, ATLAS-3925.patch, 
> image-2020-08-25-12-53-09-294.png, image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



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


[jira] [Commented] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-09-03 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3925:


Commit 61b7a077bc541aad27ceadb8c55b4d568b376e3c in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=61b7a07 ]

ATLAS-3925: UI: (Regression) Properties with value Null not showing N/A #2


> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925-1.patch, ATLAS-3925.patch, 
> image-2020-08-25-12-53-09-294.png, image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



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


[jira] [Commented] (ATLAS-3932) Upgrade Spring security , libpam4j and jna lib version

2020-09-03 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3932:


Commit fb2018966fb943ef24cfc9521aa77e62450d58e0 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fb20189 ]

ATLAS-3932 - Upgrade jna , spring.security and libpam4j versions

(cherry picked from commit 92c2ae30d27efcafbfea710f8e246cfb7487f35d)


> Upgrade Spring security , libpam4j and jna lib version
> --
>
> Key: ATLAS-3932
> URL: https://issues.apache.org/jira/browse/ATLAS-3932
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3932-Upgrade-jna-spring.security-and-libpam4j-.patch
>
>
> Upgrade jna lib version from 4.1.0 to 5.2.0
> Upgrade libpam4j lib version from 1.8 to 1.11
> and Upgrade Spring security  version from 4.2.16.RELEASE to  4.2.17.RELEASE



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


[jira] [Commented] (ATLAS-3932) Upgrade Spring security , libpam4j and jna lib version

2020-09-03 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3932:


Commit 92c2ae30d27efcafbfea710f8e246cfb7487f35d in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=92c2ae3 ]

ATLAS-3932 - Upgrade jna , spring.security and libpam4j versions


> Upgrade Spring security , libpam4j and jna lib version
> --
>
> Key: ATLAS-3932
> URL: https://issues.apache.org/jira/browse/ATLAS-3932
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3932-Upgrade-jna-spring.security-and-libpam4j-.patch
>
>
> Upgrade jna lib version from 4.1.0 to 5.2.0
> Upgrade libpam4j lib version from 1.8 to 1.11
> and Upgrade Spring security  version from 4.2.16.RELEASE to  4.2.17.RELEASE



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


[jira] [Commented] (ATLAS-3874) NotificationHookConsumer: Shell Entity Resolution When Multiple Consumers Process Same Entity

2020-09-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3874:


Commit 3468c2b4ac1175849ce119dcd69f5518b1d9a342 in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3468c2b ]

ATLAS-3874: NotificationHookConsumer: Concurrent Message Processing

Change-Id: Ia5ccc6aeea2b0c44493636243b7627d16ad32c8f
Signed-off-by: Sarath Subramanian 


> NotificationHookConsumer: Shell Entity Resolution When Multiple Consumers 
> Process Same Entity
> -
>
> Key: ATLAS-3874
> URL: https://issues.apache.org/jira/browse/ATLAS-3874
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
>
> *Background*
> Atlas has ability to consume messages from multiple hooks. When doing so, if 
> there are messages in multiple queue requesting creation of  the same entity, 
> then this case leads to a race condition. 
> *Steps to Duplicate*
> _Pre-requisites_
> Atlas should be configured to consume from 2 Kafka queues viz. _queue1_ and 
> _queue2_.
> _Steps:_
>  # Add a message in _queue1_ that references a non-existent entity.
>  # Add a message in _queue2_ that creates the entity in step 1.
> _Expected behavior_:
> Shell entity should get created in step 1 that is resolved into first class 
> entity in step 2.
> _Actual behavior:_
> Shell entity is not resolved. A duplicate entity with same _qualifiedName_ 
> gets created.
> *Root Cause*
> The _NotificationHookConsumer_ is not aware of messages processed by other 
> consumers there by leading to concurrent entity creation. 
>  



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


  1   2   3   4   5   6   7   8   9   10   >