[jira] [Commented] (ATLAS-3218) UI : entity detail page columns sorting empty value check

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3218:


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

ATLAS-3218 : UI - entity detail page columns sorting empty value check

Signed-off-by: Sarath Subramanian 
(cherry picked from commit 4e4038f6e1dff1e5900a14cf306ea64817647b0a)


> UI : entity detail page columns sorting empty value check
> -
>
> Key: ATLAS-3218
> URL: https://issues.apache.org/jira/browse/ATLAS-3218
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3218.patch, rdbms_index_columns_Api_call.png
>
>
> In entity detail page if referredEntities are empty and the entity has column 
> attribute then UI show continues loader.
> {code}
> {
> "referredEntities": {},
> "entity": {
> "typeName": "rdbms_index",
> "attributes":
> {
> "qualifiedName": "rdbmsIndex1@cl1",
> "columns": [
> {
> "guid": "5360387a-e33d-4117-a7df-dd782558dd6e",
> "typeName": "rdbms_column"
> },
> {
> "guid": "eeba1f3d-455d-447c-be93-be6659c14289",
> "typeName": "rdbms_column"
> },
> {
> "guid": "9a369d9f-4e2c-462c-bff4-ab6775531cad",
> "typeName": "rdbms_column"
> }],
> "name": "rdbmsIndex1",
> "isUnique": true,
> 
> {code}



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

[jira] [Commented] (ATLAS-3196) UI : Lineage support for IE.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3196:


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

ATLAS-3196 UI : Lineage support for IE.

Signed-off-by: kevalbhatt 
(cherry picked from commit 8d30f75b0785a2704fe20dd8be5ff3afb8752ceb)


> UI : Lineage support for IE.
> 
>
> Key: ATLAS-3196
> URL: https://issues.apache.org/jira/browse/ATLAS-3196
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Attachments: ATLAS-3196.patch
>
>
> The current Lineage implementation is not working on IE browser.
> The functionality not working are zoom in, zoom out, panning, mouse zoom, 
> node search and reset graph.
> Change the implementation to show the lineage in IE.
>  



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

[jira] [Commented] (ATLAS-3213) UI : Png export not working in Safari Browser.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3213:


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

ATLAS-3213 UI : Png export not working in Safari Browser.

(cherry picked from commit da13d53a049eebd6de2fa34283f5ac01f184708d)


> UI : Png export not working in Safari Browser.
> --
>
> Key: ATLAS-3213
> URL: https://issues.apache.org/jira/browse/ATLAS-3213
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3213.patch
>
>
> The Lineage export is not functioning as desired in Safari browser,



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

[jira] [Updated] (ATLAS-3196) UI : Lineage support for IE.

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-3196:
---
Fix Version/s: 2.1.0
   1.2.0
   0.8.4

> UI : Lineage support for IE.
> 
>
> Key: ATLAS-3196
> URL: https://issues.apache.org/jira/browse/ATLAS-3196
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.1.0
>
> Attachments: ATLAS-3196.patch
>
>
> The current Lineage implementation is not working on IE browser.
> The functionality not working are zoom in, zoom out, panning, mouse zoom, 
> node search and reset graph.
> Change the implementation to show the lineage in IE.
>  



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

[jira] [Updated] (ATLAS-3218) UI : entity detail page columns sorting empty value check

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-3218:
---
Fix Version/s: 2.1.0
   1.2.0
   0.8.4

> UI : entity detail page columns sorting empty value check
> -
>
> Key: ATLAS-3218
> URL: https://issues.apache.org/jira/browse/ATLAS-3218
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.1.0
>
> Attachments: ATLAS-3218.patch, rdbms_index_columns_Api_call.png
>
>
> In entity detail page if referredEntities are empty and the entity has column 
> attribute then UI show continues loader.
> {code}
> {
> "referredEntities": {},
> "entity": {
> "typeName": "rdbms_index",
> "attributes":
> {
> "qualifiedName": "rdbmsIndex1@cl1",
> "columns": [
> {
> "guid": "5360387a-e33d-4117-a7df-dd782558dd6e",
> "typeName": "rdbms_column"
> },
> {
> "guid": "eeba1f3d-455d-447c-be93-be6659c14289",
> "typeName": "rdbms_column"
> },
> {
> "guid": "9a369d9f-4e2c-462c-bff4-ab6775531cad",
> "typeName": "rdbms_column"
> }],
> "name": "rdbmsIndex1",
> "isUnique": true,
> 
> {code}



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

[jira] [Updated] (ATLAS-3213) UI : Png export not working in Safari Browser.

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-3213:
---
Fix Version/s: (was: trunk)
   2.1.0
   1.2.0
   0.8.4

> UI : Png export not working in Safari Browser.
> --
>
> Key: ATLAS-3213
> URL: https://issues.apache.org/jira/browse/ATLAS-3213
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.1.0
>
> Attachments: ATLAS-3213.patch
>
>
> The Lineage export is not functioning as desired in Safari browser,



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

[jira] [Updated] (ATLAS-3218) UI : entity detail page columns sorting empty value check

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-3218:
---
Fix Version/s: (was: 0.8.4)

> UI : entity detail page columns sorting empty value check
> -
>
> Key: ATLAS-3218
> URL: https://issues.apache.org/jira/browse/ATLAS-3218
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.2.0, 2.1.0
>
> Attachments: ATLAS-3218.patch, rdbms_index_columns_Api_call.png
>
>
> In entity detail page if referredEntities are empty and the entity has column 
> attribute then UI show continues loader.
> {code}
> {
> "referredEntities": {},
> "entity": {
> "typeName": "rdbms_index",
> "attributes":
> {
> "qualifiedName": "rdbmsIndex1@cl1",
> "columns": [
> {
> "guid": "5360387a-e33d-4117-a7df-dd782558dd6e",
> "typeName": "rdbms_column"
> },
> {
> "guid": "eeba1f3d-455d-447c-be93-be6659c14289",
> "typeName": "rdbms_column"
> },
> {
> "guid": "9a369d9f-4e2c-462c-bff4-ab6775531cad",
> "typeName": "rdbms_column"
> }],
> "name": "rdbmsIndex1",
> "isUnique": true,
> 
> {code}



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

Re: [VOTE] Release Apache Atlas version 1.2.0

[Keval Bhatt]

Thanks, Nixon for putting a release together for 1.2.0.

I found a few UI commits which are good to include it.

   - ATLAS-3213  UI: Png
   export not working in Safari Browser.
   - ATLAS-3218  : UI -
   entity detail page columns sorting empty value check
   - ATLAS-3196  UI :
   Lineage support for IE.
   - ATLAS-3190 : UI:
   Allow user to refresh metric data inside popup


On Mon, May 27, 2019 at 6:26 PM Nixon Rodrigues <
nixon.rodrig...@freestoneinfotech.com> wrote:

> Atlas team,
>
> Apache Atlas 1.2.0 release candidate #0 is now available for a vote within
> dev community. Links to the release artifacts are given below. Please
> review and vote.
>
> The vote will be open for at least 72 hours or until necessary votes are
> reached.
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove (and reason why)
>
>
> Thanks,
> Nixon Rodrigues
>
>
> List of issues addressed in this release:
>
> https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC
>
> Git tag for the release:
> https://github.com/apache/atlas/tree/release-1.2.0-rc0
>
> Sources for the release:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz
>
> Source release verification:
>   PGP Signature:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz.asc
>   MD5 Hash:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz.md5
>   SHA512 Hash:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz.sha512
>
>  Keys to verify the signature of the release artifacts are available at:
> https://dist.apache.org/repos/dist/dev/atlas/KEYS
>

[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Saqeeb Shaikh (JIRA)]

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

Saqeeb Shaikh commented on ATLAS-3153:
--

Thanks for the patch [~bolke]. I have done basic validations with keycloak 
server, it looks good.

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

[jira] [Comment Edited] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Saqeeb Shaikh (JIRA)]

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

Saqeeb Shaikh edited comment on ATLAS-3153 at 5/28/19 12:01 PM:


Thanks for the patch [~bolke]. I have done basic validations with keycloak 
server, it looks good.

I am validating if this patch has some impact on current authentications 
methods supported by Atlas, I'll update you by tomorrow EOD.


was (Author: saqeeb.shaikh136):
Thanks for the patch [~bolke]. I have done basic validations with keycloak 
server, it looks good.

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

[jira] [Updated] (ATLAS-3190) UI : Allow user to refresh metric data inside popup

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-3190:
---
Fix Version/s: 1.2.0

> UI : Allow user to refresh metric data inside popup
> ---
>
> Key: ATLAS-3190
> URL: https://issues.apache.org/jira/browse/ATLAS-3190
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 1.2.0, 2.0.0, trunk
>
> Attachments: ATLAS-3190-1.patch, ATLAS-3190.patch, Screen Shot 
> 2019-05-03 at 4.15.25 PM.png
>
>




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

[jira] [Updated] (ATLAS-3190) UI : Allow user to refresh metric data inside popup

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-3190:
---
Fix Version/s: (was: 1.2.0)

> UI : Allow user to refresh metric data inside popup
> ---
>
> Key: ATLAS-3190
> URL: https://issues.apache.org/jira/browse/ATLAS-3190
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3190-1.patch, ATLAS-3190.patch, Screen Shot 
> 2019-05-03 at 4.15.25 PM.png
>
>




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

[jira] [Commented] (ATLAS-3218) UI : entity detail page columns sorting empty value check

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3218:


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

ATLAS-3218 : UI - entity detail page columns sorting empty value check

Signed-off-by: Sarath Subramanian 
(cherry picked from commit 4e4038f6e1dff1e5900a14cf306ea64817647b0a)


> UI : entity detail page columns sorting empty value check
> -
>
> Key: ATLAS-3218
> URL: https://issues.apache.org/jira/browse/ATLAS-3218
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.2.0, 2.1.0
>
> Attachments: ATLAS-3218.patch, rdbms_index_columns_Api_call.png
>
>
> In entity detail page if referredEntities are empty and the entity has column 
> attribute then UI show continues loader.
> {code}
> {
> "referredEntities": {},
> "entity": {
> "typeName": "rdbms_index",
> "attributes":
> {
> "qualifiedName": "rdbmsIndex1@cl1",
> "columns": [
> {
> "guid": "5360387a-e33d-4117-a7df-dd782558dd6e",
> "typeName": "rdbms_column"
> },
> {
> "guid": "eeba1f3d-455d-447c-be93-be6659c14289",
> "typeName": "rdbms_column"
> },
> {
> "guid": "9a369d9f-4e2c-462c-bff4-ab6775531cad",
> "typeName": "rdbms_column"
> }],
> "name": "rdbmsIndex1",
> "isUnique": true,
> 
> {code}



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

[jira] [Commented] (ATLAS-3213) UI : Png export not working in Safari Browser.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3213:


Commit 31b4d25a6f577fe11c1f88a6ee427734ba73ea32 in atlas's branch 
refs/heads/branch-1.0 from gutkaBinit
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=31b4d25 ]

ATLAS-3213 UI : Png export not working in Safari Browser.

(cherry picked from commit da13d53a049eebd6de2fa34283f5ac01f184708d)


> UI : Png export not working in Safari Browser.
> --
>
> Key: ATLAS-3213
> URL: https://issues.apache.org/jira/browse/ATLAS-3213
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.1.0
>
> Attachments: ATLAS-3213.patch
>
>
> The Lineage export is not functioning as desired in Safari browser,



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

[jira] [Commented] (ATLAS-3196) UI : Lineage support for IE.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3196:


Commit 7147f9d99baaf76a669cebb4f947fb905e08596c in atlas's branch 
refs/heads/branch-1.0 from gutkaBinit
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7147f9d ]

ATLAS-3196 UI : Lineage support for IE.

Signed-off-by: kevalbhatt 
(cherry picked from commit 8d30f75b0785a2704fe20dd8be5ff3afb8752ceb)


> UI : Lineage support for IE.
> 
>
> Key: ATLAS-3196
> URL: https://issues.apache.org/jira/browse/ATLAS-3196
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.1.0
>
> Attachments: ATLAS-3196.patch
>
>
> The current Lineage implementation is not working on IE browser.
> The functionality not working are zoom in, zoom out, panning, mouse zoom, 
> node search and reset graph.
> Change the implementation to show the lineage in IE.
>  



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

[jira] [Commented] (ATLAS-3190) UI : Allow user to refresh metric data inside popup

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3190:


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

ATLAS-3190: UI : Lineage File Changes pulled from this fix

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


> UI : Allow user to refresh metric data inside popup
> ---
>
> Key: ATLAS-3190
> URL: https://issues.apache.org/jira/browse/ATLAS-3190
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3190-1.patch, ATLAS-3190.patch, Screen Shot 
> 2019-05-03 at 4.15.25 PM.png
>
>




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

[jira] [Commented] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry commented on ATLAS-3177:


[~ssainath] Your observation is accurate. We use a combination of entity 
timestamp and request timestamp to determine the value of changeMarker. The 
lower of the 2 values is selected. That is the reason why the timestamp is set 
to value lower than the modificationTime stamp of entities.

This causes few entities to be re-exported during subsequent requests.But this 
this also prevents entities from being skipped. 

 

> Regression , Export : changeMarker is not set right - set to older value 
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes": 
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType": 
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM 
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25, 
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to 
> incremental export.
> Attaching the entity definition of db entity and the exported zip.



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

[jira] [Resolved] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry resolved ATLAS-3177.

Resolution: Invalid

> Regression , Export : changeMarker is not set right - set to older value 
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: trunk, 1.1.0
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes": 
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType": 
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM 
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25, 
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to 
> incremental export.
> Attaching the entity definition of db entity and the exported zip.



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

[jira] [Commented] (ATLAS-2985) Fix delete handlers and relationship store

[Alessandro Lollo (JIRA)]

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

Alessandro Lollo commented on ATLAS-2985:
-

Hi all,

is there a schedule for the resolution and release of this fix?

> Fix delete handlers and relationship store
> --
>
> Key: ATLAS-2985
> URL: https://issues.apache.org/jira/browse/ATLAS-2985
> Project: Atlas
>  Issue Type: Bug
>Reporter: Graham Wallis
>Assignee: Graham Wallis
>Priority: Critical
> Attachments: ATLAS-2985-2018-11-30.patch
>
>
> The problems this fixes are as follows:
>  * following a soft delete, a hard delete is not possible because the entity 
> or relationship will have status DELETED, and prior to this Jira and patch 
> the abstract delete handler skips the delete. 
>  * during a soft delete the modified-time, modified-by and version number 
> attributes on the entity or relationship should be updated, but 
> updateRelationship does not update system attributes - this Jira and patch 
> updates the system attributes that will need to be updated during a delete or 
> other update operations.
>  * also fixes a minor copy-paste debug logging error.



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

Re: Review Request 70708: ATLAS-3185: Create process execution for Impala integration

[Na Li via Review Board]

> On May 24, 2019, 8:14 p.m., Aadarsh Jajodia wrote:
> > addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
> > Lines 561-562 (patched)
> > 
> >
> > Maybe use long for both?

fixed


> On May 24, 2019, 8:14 p.m., Aadarsh Jajodia wrote:
> > addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
> > Lines 120 (patched)
> > 
> >
> > Change to processExecution != null

good catch!


- Na


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70708/#review215511
---


On May 23, 2019, 9:11 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70708/
> ---
> 
> (Updated May 23, 2019, 9:11 p.m.)
> 
> 
> Review request for atlas, Aadarsh Jajodia, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-3133 adds a new feature to track metadata for different executions of 
> the same process in Atlas. Need to add this in Impala integration
> 
> 
> Diffs
> -
> 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/AtlasImpalaHookContext.java
>  88faace 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
>  232a569 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
>  63c5f87 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
>  0dc520c 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
>  0138d88 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
>  033a518 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
>  86801e3 
> 
> 
> Diff: https://reviews.apache.org/r/70708/diff/1/
> 
> 
> Testing
> ---
> 
> Integration tests
> 
> 
> Thanks,
> 
> Na Li
> 
>

[jira] [Commented] (ATLAS-3219) Implemented new serviceType Rest API

[Diego Marino Monetti (JIRA)]

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

Diego Marino Monetti commented on ATLAS-3219:
-

I realized that I forgot to implement the V2 client part of these REST APIs. If 
you think adding these APIs for future releases could be useful I could 
implement them.

> Implemented new serviceType Rest API
> 
>
> Key: ATLAS-3219
> URL: https://issues.apache.org/jira/browse/ATLAS-3219
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
> Environment: all
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This pull request supersedes the pull request ATLAS-3180.
> The new basic attribute serviceType, introduced by Atlas Team, has no use if 
> it is not searchable ina any way. This pull request solves this problem by 
> adding the following REST APIs.
> GET / typedef / servicetype / \{servicetype}
> GET / typedefs / headers? Servicetype = \{serviceType}
> GET / typedefs? Servicetype = \{servicetype}
> GET / enumdef / servicetype / \{servicetype}
> GET / entitydef / servicetype / \{servicetype}
> GET / structdef / servicetype / \{servicetype}
> GET / relationshipdef / servicetype / \{servicetype}
> DELETE / typedef / servicetype / \{servicetype}
> The APIs were tested on ATLAS 2.0 and on the new SNAPSHOT 3.0



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

Re: Review Request 70708: ATLAS-3185: Create process execution for Impala integration

[Sarath Subramanian]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70708/#review215546
---


Fix it, then Ship it!





addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
Lines 23 (patched)


nit: unused imports, consider removing them.



addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
Lines 565 (patched)


cast startTime as string value; same for line #568



addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
Line 114 (original), 114 (patched)


surround with LOG.isDebugEnabled(); same for line #121


- Sarath Subramanian


On May 23, 2019, 2:11 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70708/
> ---
> 
> (Updated May 23, 2019, 2:11 p.m.)
> 
> 
> Review request for atlas, Aadarsh Jajodia, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-3133 adds a new feature to track metadata for different executions of 
> the same process in Atlas. Need to add this in Impala integration
> 
> 
> Diffs
> -
> 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/AtlasImpalaHookContext.java
>  88faace 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
>  232a569 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
>  63c5f87 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
>  0dc520c 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
>  0138d88 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
>  033a518 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
>  86801e3 
> 
> 
> Diff: https://reviews.apache.org/r/70708/diff/1/
> 
> 
> Testing
> ---
> 
> Integration tests
> 
> 
> Thanks,
> 
> Na Li
> 
>

[jira] [Commented] (ATLAS-3234) Add option in Precommit-Atlas to build and run tests on git pull request

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3234:


Commit 14eb91a7d9638d6659d801e702b3f277cec2427d in atlas's branch 
refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=14eb91a ]

ATLAS-3234: Add option in Precommit-Atlas to build and run tests on git pull 
request


> Add option in Precommit-Atlas to build and run tests on git pull request
> 
>
> Key: ATLAS-3234
> URL: https://issues.apache.org/jira/browse/ATLAS-3234
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3234.001.patch
>
>
> [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test]
> Add option to provide git pull request id to build and run tests on git pull 
> requests.



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

[jira] [Updated] (ATLAS-3234) Add option in Precommit-Atlas to build and run tests on git pull request

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3234:
--
Fix Version/s: 2.1.0

> Add option in Precommit-Atlas to build and run tests on git pull request
> 
>
> Key: ATLAS-3234
> URL: https://issues.apache.org/jira/browse/ATLAS-3234
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3234.001.patch
>
>
> [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test]
> Add option to provide git pull request id to build and run tests on git pull 
> requests.



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

[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian commented on ATLAS-3153:
---

[~bolke] can you attach the design doc in the JIRA.

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Bolke de Bruin (JIRA)]

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

Bolke de Bruin commented on ATLAS-3153:
---

[~sarath.ku...@gmail.com] sure, can you explain what you would like to see in 
the design doc? Both OpenID connect and spring security are well understood. 
The roles / groups might be something as they can be obtained from keycloak 
instead of UGI. That’s also pretty straightforward. 

Can you give me some guidance?

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian commented on ATLAS-3153:
---

[~bolke], like Srikanth mentiioned - " a design doc for the use case and the 
arch. and configs needed for Atlas to consume OpenID asserted credentials? 
Perhaps an interaction diagram to explain how this feature will work, the 
actual flow, and configs needed (for example how the user/group mappings are 
fetched) "

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

Re: Review Request 70708: ATLAS-3185: Create process execution for Impala integration

[Na Li via Review Board]

> On May 28, 2019, 5:58 p.m., Sarath Subramanian wrote:
> > addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
> > Lines 23 (patched)
> > 
> >
> > nit: unused imports, consider removing them.

done


> On May 28, 2019, 5:58 p.m., Sarath Subramanian wrote:
> > addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
> > Lines 565 (patched)
> > 
> >
> > cast startTime as string value; same for line #568

directly casting it to long does not work. I change the type to "Long", and 
call its.toString() instead


> On May 28, 2019, 5:58 p.m., Sarath Subramanian wrote:
> > addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
> > Line 114 (original), 114 (patched)
> > 
> >
> > surround with LOG.isDebugEnabled(); same for line #121

see comment at 
https://stackoverflow.com/questions/105852/conditional-logging-with-minimal-cyclomatic-complexity/105908#105908
 and 
`https://stackoverflow.com/questions/963492/in-log4j-does-checking-isdebugenabled-before-logging-improve-performance`

`Better yet is to use a more up-to-date logging framework where the log 
statements take a format specification and a list of arguments to be 
substituted by the logger—but "lazily," only if the logger is enabled.` 
that is what I did. The overhead only happens if debug logging is enabled. So I 
don't need to check  `LOG.isDebugEnabled()`


- Na


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70708/#review215546
---


On May 23, 2019, 9:11 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70708/
> ---
> 
> (Updated May 23, 2019, 9:11 p.m.)
> 
> 
> Review request for atlas, Aadarsh Jajodia, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-3133 adds a new feature to track metadata for different executions of 
> the same process in Atlas. Need to add this in Impala integration
> 
> 
> Diffs
> -
> 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/AtlasImpalaHookContext.java
>  88faace 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
>  232a569 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
>  63c5f87 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
>  0dc520c 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
>  0138d88 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
>  033a518 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
>  86801e3 
> 
> 
> Diff: https://reviews.apache.org/r/70708/diff/1/
> 
> 
> Testing
> ---
> 
> Integration tests
> 
> 
> Thanks,
> 
> Na Li
> 
>

[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Bolke de Bruin (JIRA)]

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

Bolke de Bruin commented on ATLAS-3153:
---

[~sarath.ku...@gmail.com] as mentioned this is already part of the PR? Isn’t 
the twiki used for this?

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

[jira] [Commented] (ATLAS-2974) Docker build: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin...

[Xinran Tinney (JIRA)]

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

Xinran Tinney commented on ATLAS-2974:
--

[~dmigo] what OS did you try this on? I have tried again on Ubuntu 18.04 and it 
can build an image successfully using the existing Dockerfile under 
atlas/dev-support/atlas-docker.

> Docker build: Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin...
> --
>
> Key: ATLAS-2974
> URL: https://issues.apache.org/jira/browse/ATLAS-2974
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dmitry Goryunov
>Priority: Major
> Attachments: tmp
>
>
> Version: commit 945de013f5466ffcf71d16c6ec1772fdee83e2f6 (Also reproducable 
> with 1.1.0-rc2)
>  
> Runnign command:
> {code:java}
> docker build -t atlas_docker .
> {code}
> Breaks at some point with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce 
> (enforce-versions) on project apache-atlas: Some Enforcer rules have failed. 
> Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :apache-atlas
> The command '/bin/sh -c mvn clean install -DskipTests 
> -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1
> {code}
> The complete logs are attached.



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

[jira] [Created] (ATLAS-3240) Switch all 'http' urls to 'https' in maven settings

[Sarath Subramanian (JIRA)]

Sarath Subramanian created ATLAS-3240:
-

 Summary: Switch all 'http' urls to 'https' in maven settings
 Key: ATLAS-3240
 URL: https://issues.apache.org/jira/browse/ATLAS-3240
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 1.2.0, 2.1.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 1.2.0, 2.1.0






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

[jira] [Assigned] (ATLAS-2974) Docker build: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin...

[Xinran Tinney (JIRA)]

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

Xinran Tinney reassigned ATLAS-2974:


Assignee: Xinran Tinney

> Docker build: Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin...
> --
>
> Key: ATLAS-2974
> URL: https://issues.apache.org/jira/browse/ATLAS-2974
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dmitry Goryunov
>Assignee: Xinran Tinney
>Priority: Major
> Attachments: tmp
>
>
> Version: commit 945de013f5466ffcf71d16c6ec1772fdee83e2f6 (Also reproducable 
> with 1.1.0-rc2)
>  
> Runnign command:
> {code:java}
> docker build -t atlas_docker .
> {code}
> Breaks at some point with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce 
> (enforce-versions) on project apache-atlas: Some Enforcer rules have failed. 
> Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :apache-atlas
> The command '/bin/sh -c mvn clean install -DskipTests 
> -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1
> {code}
> The complete logs are attached.



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

[jira] [Updated] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Bolke de Bruin (JIRA)]

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

Bolke de Bruin updated ATLAS-3153:
--
Attachment: openid_connect_atlas.md

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
> Attachments: openid_connect_atlas.md
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

[Bolke de Bruin (JIRA)]

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

Bolke de Bruin commented on ATLAS-3153:
---

[~sarath.ku...@gmail.com] I have added the file. Mostly copied from the PR with 
some additions.

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
> Attachments: openid_connect_atlas.md
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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

[jira] [Commented] (ATLAS-2974) Docker build: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin...

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2974:


Just as a FYI I was able to build the docker image ok off master.

The maven enforcer plugin checks various conditions for the build. If you look 
further up the log from that ERROR there should be a message with more info. 
Perhaps worth posting the log as a gist or similar?

Typical checks would be for maven version & java version (the atlas top level 
pom checks for maven > 3.5 & java > 1.8.0-151, - but since this docker build 
runs the atlas build within a container that should be pretty fixed (though 
updates are applied), so I'm not sure why you see different results? Did you 
change anything in the Dockerfile? Switch the compiler version for example (it 
was failing with some versions of the J9 jvm)

> Docker build: Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin...
> --
>
> Key: ATLAS-2974
> URL: https://issues.apache.org/jira/browse/ATLAS-2974
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dmitry Goryunov
>Assignee: Xinran Tinney
>Priority: Major
> Attachments: tmp
>
>
> Version: commit 945de013f5466ffcf71d16c6ec1772fdee83e2f6 (Also reproducable 
> with 1.1.0-rc2)
>  
> Runnign command:
> {code:java}
> docker build -t atlas_docker .
> {code}
> Breaks at some point with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce 
> (enforce-versions) on project apache-atlas: Some Enforcer rules have failed. 
> Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :apache-atlas
> The command '/bin/sh -c mvn clean install -DskipTests 
> -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1
> {code}
> The complete logs are attached.



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

Re: Review Request 70708: ATLAS-3185: Create process execution for Impala integration

[Na Li via Review Board]

> On May 24, 2019, 8:14 p.m., Aadarsh Jajodia wrote:
> > addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
> > Lines 201-205 (patched)
> > 
> >
> > Can we also add a unit test which produces more than one execution?

added new test with multiple process executions


- Na


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70708/#review215511
---


On May 28, 2019, 9:19 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70708/
> ---
> 
> (Updated May 28, 2019, 9:19 p.m.)
> 
> 
> Review request for atlas, Aadarsh Jajodia, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-3133 adds a new feature to track metadata for different executions of 
> the same process in Atlas. Need to add this in Impala integration
> 
> 
> Diffs
> -
> 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/ImpalaLineageTool.java
>  7c9abc8 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/AtlasImpalaHookContext.java
>  88faace 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaIdentifierParser.java
>  b9d6cbb 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
>  232a569 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
>  c7604ba 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
>  3071576 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
>  0138d88 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
>  033a518 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
>  86801e3 
>   
> addons/impala-bridge/src/test/resources/impalaMultipleInsertIntoAsSelect1.json
>  PRE-CREATION 
>   
> addons/impala-bridge/src/test/resources/impalaMultipleInsertIntoAsSelect2.json
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/70708/diff/2/
> 
> 
> Testing
> ---
> 
> Integration tests
> 
> 
> Thanks,
> 
> Na Li
> 
>

[jira] [Commented] (ATLAS-3185) Create process execution for Impala integration

[Na Li (JIRA)]

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

Na Li commented on ATLAS-3185:
--

pre-commit for patch 2 is at 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1143/

> Create process execution for Impala integration
> ---
>
> Key: ATLAS-3185
> URL: https://issues.apache.org/jira/browse/ATLAS-3185
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Na Li
>Assignee: Na Li
>Priority: Major
> Attachments: ATLAS-3185.002.patch
>
>
> [ATLAS-3133|https://issues.apache.org/jira/browse/ATLAS-3133] adds a new 
> feature to track metadata for different executions of the same process in 
> Atlas. Need to add this in Impala integration



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

[jira] [Updated] (ATLAS-3185) Create process execution for Impala integration

[Na Li (JIRA)]

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

Na Li updated ATLAS-3185:
-
Attachment: ATLAS-3185.002.patch

> Create process execution for Impala integration
> ---
>
> Key: ATLAS-3185
> URL: https://issues.apache.org/jira/browse/ATLAS-3185
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Na Li
>Assignee: Na Li
>Priority: Major
> Attachments: ATLAS-3185.002.patch
>
>
> [ATLAS-3133|https://issues.apache.org/jira/browse/ATLAS-3133] adds a new 
> feature to track metadata for different executions of the same process in 
> Atlas. Need to add this in Impala integration



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

Re: Review Request 70708: ATLAS-3185: Create process execution for Impala integration

[Na Li via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70708/
---

(Updated May 28, 2019, 9:19 p.m.)


Review request for atlas, Aadarsh Jajodia, Madhan Neethiraj, and Sarath 
Subramanian.


Repository: atlas


Description
---

ATLAS-3133 adds a new feature to track metadata for different executions of the 
same process in Atlas. Need to add this in Impala integration


Diffs (updated)
-

  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/ImpalaLineageTool.java
 7c9abc8 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/AtlasImpalaHookContext.java
 88faace 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaIdentifierParser.java
 b9d6cbb 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
 232a569 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
 c7604ba 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
 3071576 
  
addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
 0138d88 
  
addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
 033a518 
  
addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
 86801e3 
  
addons/impala-bridge/src/test/resources/impalaMultipleInsertIntoAsSelect1.json 
PRE-CREATION 
  
addons/impala-bridge/src/test/resources/impalaMultipleInsertIntoAsSelect2.json 
PRE-CREATION 


Diff: https://reviews.apache.org/r/70708/diff/2/

Changes: https://reviews.apache.org/r/70708/diff/1-2/


Testing
---

Integration tests


Thanks,

Na Li

Re: Review Request 70708: ATLAS-3185: Create process execution for Impala integration

[Sarath Subramanian]

> On May 28, 2019, 10:58 a.m., Sarath Subramanian wrote:
> > addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
> > Line 114 (original), 114 (patched)
> > 
> >
> > surround with LOG.isDebugEnabled(); same for line #121
> 
> Na Li wrote:
> see comment at 
> https://stackoverflow.com/questions/105852/conditional-logging-with-minimal-cyclomatic-complexity/105908#105908
>  and 
> `https://stackoverflow.com/questions/963492/in-log4j-does-checking-isdebugenabled-before-logging-improve-performance`
> 
> `Better yet is to use a more up-to-date logging framework where the log 
> statements take a format specification and a list of arguments to be 
> substituted by the logger—but "lazily," only if the logger is enabled.` 
> that is what I did. The overhead only happens if debug logging is 
> enabled. So I don't need to check  `LOG.isDebugEnabled()`

this is to keep it consistent with other Log.debug statements.


- Sarath


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70708/#review215546
---


On May 28, 2019, 2:19 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70708/
> ---
> 
> (Updated May 28, 2019, 2:19 p.m.)
> 
> 
> Review request for atlas, Aadarsh Jajodia, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-3133 adds a new feature to track metadata for different executions of 
> the same process in Atlas. Need to add this in Impala integration
> 
> 
> Diffs
> -
> 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/ImpalaLineageTool.java
>  7c9abc8 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/AtlasImpalaHookContext.java
>  88faace 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaIdentifierParser.java
>  b9d6cbb 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
>  232a569 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
>  c7604ba 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
>  3071576 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
>  0138d88 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
>  033a518 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
>  86801e3 
>   
> addons/impala-bridge/src/test/resources/impalaMultipleInsertIntoAsSelect1.json
>  PRE-CREATION 
>   
> addons/impala-bridge/src/test/resources/impalaMultipleInsertIntoAsSelect2.json
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/70708/diff/2/
> 
> 
> Testing
> ---
> 
> Integration tests
> 
> 
> Thanks,
> 
> Na Li
> 
>

[jira] [Created] (ATLAS-3241) AtlasClientV2Test.java invalid directory

[Diego Marino Monetti (JIRA)]

Diego Marino Monetti created ATLAS-3241:
---

 Summary: AtlasClientV2Test.java invalid directory
 Key: ATLAS-3241
 URL: https://issues.apache.org/jira/browse/ATLAS-3241
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
 Environment: All
Reporter: Diego Marino Monetti
 Fix For: trunk, 2.1.0, 3.0.0, 2.0.0


AtlasClientV2Test.java should have the following path
{quote}client/client-v2 /src/test 
/java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
{quote}
instead has
{quote}client/client-v2 
/src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
{quote}
Bug or, for some strange reason, intentional ?



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

[jira] [Commented] (ATLAS-3241) AtlasClientV2Test.java invalid directory

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-3241:
-

[~Zep] - this is not intentional. Should be fixed.

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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

[jira] [Commented] (ATLAS-3241) AtlasClientV2Test.java invalid directory

[Diego Marino Monetti (JIRA)]

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

Diego Marino Monetti commented on ATLAS-3241:
-

I will pull request now

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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

[GitHub] [atlas] ZepHakase22 opened a new pull request #57: ATLAS-3241: FIX:Invalid path for AtlasClientV2Test.java

[GitBox]

ZepHakase22 opened a new pull request #57: ATLAS-3241: FIX:Invalid path for 
AtlasClientV2Test.java
URL: https://github.com/apache/atlas/pull/57
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (ATLAS-3241) AtlasClientV2Test.java invalid directory

[Diego Marino Monetti (JIRA)]

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

Diego Marino Monetti commented on ATLAS-3241:
-

Done

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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

[GitHub] [atlas] mneethiraj commented on issue #54: ATLAS-3219: New REST APIs for serviceType.

[GitBox]

mneethiraj commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496745311
 
 
   @ZepHakase22  - instead of adding new REST endpoints (for 
/servicetype/{serviceType}), I suggest to recognize "serviceType" parameter in 
FilterUtil.getPredicateFromSearchFilter(SearchFilter filter) so that all 
methods that use SearchFilter will apply this filter.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [atlas] ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.

[GitBox]

ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496748406
 
 
   It was exactly what I did but it works only for 
   
   > GET / typedefs? serviceype = {servicetype}
   
   how you can see here in the code. But if you want to maintain compatibility 
with the other REST APIs, that is how the ones for guid and name are made, you 
need to work in another way, because these APIs refer to the cache.
   
   Furthermore, DELETE, obviously needs a separate code.
   
   public static Predicate getPredicateFromSearchFilter(SearchFilter 
searchFilter) {
   List predicates = new ArrayList<>();
   
   final String   type = 
searchFilter.getParam(SearchFilter.PARAM_TYPE);
   final String   name = 
searchFilter.getParam(SearchFilter.PARAM_NAME);
   final String   supertype= 
searchFilter.getParam(SearchFilter.PARAM_SUPERTYPE);
   final StringserviceType  = 
searchFilter.getParam(SearchFilter.PARAM_SERVICETYPE);
   
   final String   notSupertype = 
searchFilter.getParam(SearchFilter.PARAM_NOT_SUPERTYPE);
   final StringnotServiceType = 
searchFilter.getParam(SearchFilter.PARAM_NOT_SERVICETYPE);
   final List notNames = 
searchFilter.getParams(SearchFilter.PARAM_NOT_NAME);
   
   // Add filter for the type/category
   if (StringUtils.isNotBlank(type)) {
   predicates.add(getTypePredicate(type));
   }
   
   // Add filter for the name
   if (StringUtils.isNotBlank(name)) {
   predicates.add(getNamePredicate(name));
   }
   
   //Add filter for the serviceType
   if(StringUtils.isNotBlank(serviceType)) {
predicates.add(getServiceTypePredicate(serviceType));
   }
   
   // Add filter for the supertype
   if (StringUtils.isNotBlank(supertype)) {
   predicates.add(getSuperTypePredicate(supertype));
   }
   
   // Add filter for the supertype negation
   if (StringUtils.isNotBlank(notSupertype)) {
   predicates.add(new 
NotPredicate(getSuperTypePredicate(notSupertype)));
   }
   
   // Add filter for the serviceType negation
   // NOTE: Creating code for the exclusion of multiple service types 
is currently useless. 
   // In fact the getSearchFilter in TypeREST.java uses the 
HttpServletRequest.getParameter(key) 
   // that if the key takes more values it takes only the first the 
value. Could be usefull
   // to change the getSearchFilter to use getParameterValues instead 
of getParameter.
   if (StringUtils.isNotBlank(notServiceType)) {
   predicates.add(new 
NotPredicate(getServiceTypePredicate(notServiceType)));
   }
   
   
   // Add filter for the type negation
   if (CollectionUtils.isNotEmpty(notNames)) {
   for (String notName : notNames) {
   predicates.add(new NotPredicate(getNamePredicate(notName)));
   }
   }
   
   return PredicateUtils.allPredicate(predicates);
   }
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [atlas] ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.

[GitBox]

ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496750150
 
 
   In my opinion you are right because I can't understand why we a cache for 
the name, a cache for the guid and now also a cache for the serviceType. I did 
this only to mantain the compatibility with the existing code. 
   We could change all the code to have only a generic cache and filtering this 
cache to resolve the REST APIs. If you want I could better study the code and 
propose a global comprehensive review of that code.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [atlas] ZepHakase22 edited a comment on issue #54: ATLAS-3219: New REST APIs for serviceType.

[GitBox]

ZepHakase22 edited a comment on issue #54: ATLAS-3219: New REST APIs for 
serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496750150
 
 
   In my opinion you are right because I can't understand why we have a cache 
for the name, a cache for the guid and now also a cache for the serviceType. I 
did this only to mantain the compatibility with the existing code. 
   We could change all the code to have only a generic cache and filtering this 
cache to resolve the REST APIs. If you want I could better study the code and 
propose a global comprehensive review of that code.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [atlas] ZepHakase22 edited a comment on issue #54: ATLAS-3219: New REST APIs for serviceType.

[GitBox]

ZepHakase22 edited a comment on issue #54: ATLAS-3219: New REST APIs for 
serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496750150
 
 
   @mneethiraj -In my opinion you are right because I can't understand why we 
have a cache for the name, a cache for the guid and now also a cache for the 
serviceType. I did this only to mantain the compatibility with the existing 
code. 
   We could change all the code to have only a generic cache and filtering this 
cache to resolve the REST APIs. If you want I could better study the code and 
propose a global comprehensive review of that code.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [atlas] ZepHakase22 edited a comment on issue #54: ATLAS-3219: New REST APIs for serviceType.

[GitBox]

ZepHakase22 edited a comment on issue #54: ATLAS-3219: New REST APIs for 
serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496748406
 
 
   @mneethiraj - It was exactly what I did but it works only for 
   
   > GET / typedefs? serviceype = {servicetype}
   
   how you can see here in the code. But if you want to maintain compatibility 
with the other REST APIs, that is how the ones for guid and name are made, you 
need to work in another way, because these APIs refer to the cache.
   
   Furthermore, DELETE, obviously needs a separate code.
   
   public static Predicate getPredicateFromSearchFilter(SearchFilter 
searchFilter) {
   List predicates = new ArrayList<>();
   
   final String   type = 
searchFilter.getParam(SearchFilter.PARAM_TYPE);
   final String   name = 
searchFilter.getParam(SearchFilter.PARAM_NAME);
   final String   supertype= 
searchFilter.getParam(SearchFilter.PARAM_SUPERTYPE);
   final StringserviceType  = 
searchFilter.getParam(SearchFilter.PARAM_SERVICETYPE);
   
   final String   notSupertype = 
searchFilter.getParam(SearchFilter.PARAM_NOT_SUPERTYPE);
   final StringnotServiceType = 
searchFilter.getParam(SearchFilter.PARAM_NOT_SERVICETYPE);
   final List notNames = 
searchFilter.getParams(SearchFilter.PARAM_NOT_NAME);
   
   // Add filter for the type/category
   if (StringUtils.isNotBlank(type)) {
   predicates.add(getTypePredicate(type));
   }
   
   // Add filter for the name
   if (StringUtils.isNotBlank(name)) {
   predicates.add(getNamePredicate(name));
   }
   
   //Add filter for the serviceType
   if(StringUtils.isNotBlank(serviceType)) {
predicates.add(getServiceTypePredicate(serviceType));
   }
   
   // Add filter for the supertype
   if (StringUtils.isNotBlank(supertype)) {
   predicates.add(getSuperTypePredicate(supertype));
   }
   
   // Add filter for the supertype negation
   if (StringUtils.isNotBlank(notSupertype)) {
   predicates.add(new 
NotPredicate(getSuperTypePredicate(notSupertype)));
   }
   
   // Add filter for the serviceType negation
   // NOTE: Creating code for the exclusion of multiple service types 
is currently useless. 
   // In fact the getSearchFilter in TypeREST.java uses the 
HttpServletRequest.getParameter(key) 
   // that if the key takes more values it takes only the first the 
value. Could be usefull
   // to change the getSearchFilter to use getParameterValues instead 
of getParameter.
   if (StringUtils.isNotBlank(notServiceType)) {
   predicates.add(new 
NotPredicate(getServiceTypePredicate(notServiceType)));
   }
   
   
   // Add filter for the type negation
   if (CollectionUtils.isNotEmpty(notNames)) {
   for (String notName : notNames) {
   predicates.add(new NotPredicate(getNamePredicate(notName)));
   }
   }
   
   return PredicateUtils.allPredicate(predicates);
   }
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (ATLAS-3242) Package impala hook libraries in atlas-distro module

[Sarath Subramanian (JIRA)]

Sarath Subramanian created ATLAS-3242:
-

 Summary: Package impala hook libraries in atlas-distro module
 Key: ATLAS-3242
 URL: https://issues.apache.org/jira/browse/ATLAS-3242
 Project: Atlas
  Issue Type: Task
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.1.0


Package impala hook libraries in atlas-distro module 



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

Review Request 70742: ATLAS-3242: Package impala hook libraries in atlas-distro module

[Sarath Subramanian]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70742/
---

Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, Na Li, Le Ma, and 
Madhan Neethiraj.


Bugs: ATLAS-3242
https://issues.apache.org/jira/browse/ATLAS-3242


Repository: atlas


Description
---

Package impala hook libraries in atlas-distro module


Diffs
-

  addons/impala-bridge/pom.xml a133b3426 
  distro/pom.xml e2225b81a 
  distro/src/main/assemblies/atlas-impala-hook-package.xml PRE-CREATION 


Diff: https://reviews.apache.org/r/70742/diff/1/


Testing
---

Validated that the final packaging contains impala hook libraries

Precommit - in progress.


Thanks,

Sarath Subramanian

Re: Review Request 70742: ATLAS-3242: Package impala hook libraries in atlas-distro module

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70742/#review215564
---


Ship it!




Ship It!

- Madhan Neethiraj


On May 29, 2019, 4:54 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70742/
> ---
> 
> (Updated May 29, 2019, 4:54 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, Na Li, Le Ma, and 
> Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-3242
> https://issues.apache.org/jira/browse/ATLAS-3242
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Package impala hook libraries in atlas-distro module
> 
> 
> Diffs
> -
> 
>   addons/impala-bridge/pom.xml a133b3426 
>   distro/pom.xml e2225b81a 
>   distro/src/main/assemblies/atlas-impala-hook-package.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/70742/diff/1/
> 
> 
> Testing
> ---
> 
> Validated that the final packaging contains impala hook libraries
> 
> Precommit - in progress.
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: [VOTE] Release Apache Atlas version 1.2.0

[Nixon Rodrigues]

Thanks Keval for the feedback.

I will put out new release candidate for voting with this commits today.

Regards,
Nixon Rodrigues



On Tue, May 28, 2019 at 5:15 PM Keval Bhatt  wrote:

> Thanks, Nixon for putting a release together for 1.2.0.
>
> I found a few UI commits which are good to include it.
>
>- ATLAS-3213  UI: Png
>export not working in Safari Browser.
>- ATLAS-3218  : UI -
>entity detail page columns sorting empty value check
>- ATLAS-3196  UI :
>Lineage support for IE.
>- ATLAS-3190 : UI:
>Allow user to refresh metric data inside popup
>
>
> On Mon, May 27, 2019 at 6:26 PM Nixon Rodrigues <
> nixon.rodrig...@freestoneinfotech.com> wrote:
>
> > Atlas team,
> >
> > Apache Atlas 1.2.0 release candidate #0 is now available for a vote
> within
> > dev community. Links to the release artifacts are given below. Please
> > review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove (and reason why)
> >
> >
> > Thanks,
> > Nixon Rodrigues
> >
> >
> > List of issues addressed in this release:
> >
> >
> https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC
> >
> > Git tag for the release:
> > https://github.com/apache/atlas/tree/release-1.2.0-rc0
> >
> > Sources for the release:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz
> >
> > Source release verification:
> >   PGP Signature:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz.asc
> >   MD5 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz.md5
> >   SHA512 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc0/apache-atlas-1.2.0-sources.tar.gz.sha512
> >
> >  Keys to verify the signature of the release artifacts are available at:
> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> >
>

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

[Umesh Padashetty (JIRA)]

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

Umesh Padashetty updated ATLAS-3239:

Attachment: ATLAS-3239-1.patch

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



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

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

[Umesh Padashetty (JIRA)]

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

Umesh Padashetty updated ATLAS-3239:

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

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



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

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

[Umesh Padashetty (JIRA)]

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

Umesh Padashetty updated ATLAS-3239:

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

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

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


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



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

[jira] [Updated] (ATLAS-3240) Update 'http' urls to 'https' in maven settings

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3240:
--
Summary: Update 'http' urls to 'https' in maven settings  (was: Switch all 
'http' urls to 'https' in maven settings)

> Update 'http' urls to 'https' in maven settings
> ---
>
> Key: ATLAS-3240
> URL: https://issues.apache.org/jira/browse/ATLAS-3240
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.2.0, 2.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 1.2.0, 2.1.0
>
>




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

Review Request 70743: ATLAS-3240: Update 'http' urls to 'https' in maven settings

[Sarath Subramanian]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/70743/
---

Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, Sridhar K, Na Li, 
Le Ma, and Madhan Neethiraj.


Bugs: ATLAS-3240
https://issues.apache.org/jira/browse/ATLAS-3240


Repository: atlas


Description
---

Update 'http' urls to 'https' in maven settings


Diffs
-

  addons/falcon-bridge-shim/pom.xml c6909ab32 
  addons/falcon-bridge/pom.xml 936cf220d 
  addons/hbase-bridge-shim/pom.xml e1271c4ff 
  addons/hbase-bridge/pom.xml f69b0831f 
  addons/hbase-testing-util/pom.xml 091842277 
  addons/hdfs-model/pom.xml cd09b537f 
  addons/hive-bridge-shim/pom.xml b6a41af02 
  addons/hive-bridge/pom.xml abc524637 
  addons/impala-bridge-shim/pom.xml 7144b1e68 
  addons/impala-bridge/pom.xml a133b3426 
  addons/impala-hook-api/pom.xml 1deff38e0 
  addons/kafka-bridge/pom.xml 203cd429a 
  addons/sqoop-bridge-shim/pom.xml 2ab7f3e24 
  addons/sqoop-bridge/pom.xml 3ecdb531f 
  addons/storm-bridge-shim/pom.xml 5c5bdc8ac 
  addons/storm-bridge/pom.xml 1fa95fed6 
  authorization/pom.xml e3faf76db 
  build-tools/pom.xml 9cc77749e 
  client/client-v1/pom.xml de0a1db0b 
  client/client-v2/pom.xml 6006a6c59 
  client/common/pom.xml 89faa362f 
  client/pom.xml 8d59c3a6d 
  common/pom.xml 7f222088d 
  dashboardv2/pom.xml 9eed61c99 
  distro/pom.xml e2225b81a 
  docs/pom.xml ae3f4820f 
  graphdb/api/pom.xml 7a375967d 
  graphdb/common/pom.xml 68a1e90d8 
  graphdb/graphdb-impls/pom.xml 6ca8d69ef 
  graphdb/janus-hbase2/pom.xml 3f61be9f4 
  graphdb/janus/pom.xml 0446fe4ae 
  graphdb/pom.xml 5565c78a8 
  intg/pom.xml 920935543 
  notification/pom.xml 7863eba95 
  plugin-classloader/pom.xml f8325cccf 
  pom.xml c0123a4f0 
  repository/pom.xml e2dbdef04 
  server-api/pom.xml c3d4e22cd 
  test-tools/pom.xml 63d83fdf5 
  tools/atlas-index-repair/pom.xml 042eb96b7 
  tools/classification-updater/pom.xml a93d566fc 
  webapp/pom.xml f8777140b 


Diff: https://reviews.apache.org/r/70743/diff/1/


Testing
---

Build successfull

precommit in progress.


Thanks,

Sarath Subramanian

[jira] [Commented] (ATLAS-3242) Package impala hook libraries in atlas-distro module

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3242:


Commit 10e7be0fca1be50d750f484ecb0e23a35bcdf24b in atlas's branch 
refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=10e7be0 ]

ATLAS-3242: Package impala hook libraries in atlas-distro module


> Package impala hook libraries in atlas-distro module
> 
>
> Key: ATLAS-3242
> URL: https://issues.apache.org/jira/browse/ATLAS-3242
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
>
> Package impala hook libraries in atlas-distro module 



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

[jira] [Resolved] (ATLAS-3242) Package impala hook libraries in atlas-distro module

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian resolved ATLAS-3242.
---
Resolution: Fixed

> Package impala hook libraries in atlas-distro module
> 
>
> Key: ATLAS-3242
> URL: https://issues.apache.org/jira/browse/ATLAS-3242
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
>
> Package impala hook libraries in atlas-distro module 



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

[jira] [Commented] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Sharmadha Sainath (JIRA)]

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

Sharmadha Sainath commented on ATLAS-3177:
--

[~ashutoshm] , But changeMarker is always set to value even older than the 
entity's creation timestamp.I tried quite many times. Due to this , incremental 
export is not adding any value. 

> Regression , Export : changeMarker is not set right - set to older value 
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes": 
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType": 
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM 
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25, 
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to 
> incremental export.
> Attaching the entity definition of db entity and the exported zip.



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

[jira] [Comment Edited] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Sharmadha Sainath (JIRA)]

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

Sharmadha Sainath edited comment on ATLAS-3177 at 5/29/19 6:31 AM:
---

[~ashutoshm] , But changeMarker is always set to value even older than the 
entity's creation timestamp.I tried quite many times. Due to this , incremental 
export is not adding any value. 

Also could you please explain what is request timestamp ? Is it the latest time 
stamp the entity was accessed / requested ?


was (Author: ssainath):
[~ashutoshm] , But changeMarker is always set to value even older than the 
entity's creation timestamp.I tried quite many times. Due to this , incremental 
export is not adding any value. 

> Regression , Export : changeMarker is not set right - set to older value 
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes": 
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType": 
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM 
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25, 
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to 
> incremental export.
> Attaching the entity definition of db entity and the exported zip.



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