Re: Review Request 70880: ATLAS-3290: Impala Hook should get database name and table name from vertex metadata

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/70880/#review215957 --- Ship it! Ship It! - Ashutosh Mestry On June 18, 2019, 10:38

[jira] [Commented] (ATLAS-3290) Impala Hook should get database name and table name from vertex metadata

[ https://issues.apache.org/jira/browse/ATLAS-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867103#comment-16867103 ] Na Li commented on ATLAS-3290: -- pre-commit test at

[jira] [Updated] (ATLAS-3290) Impala Hook should get database name and table name from vertex metadata

[ https://issues.apache.org/jira/browse/ATLAS-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated ATLAS-3290: - Attachment: ATLAS-3290.001.patch > Impala Hook should get database name and table name from vertex metadata >

Review Request 70880: ATLAS-3290: Impala Hook should get database name and table name from vertex metadata

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/70880/ --- Review request for atlas, madhan and Sarath Subramanian. Repository: atlas

[jira] [Updated] (ATLAS-3290) Impala Hook should get database name and table name from vertex metadata

[ https://issues.apache.org/jira/browse/ATLAS-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated ATLAS-3290: - Summary: Impala Hook should get database name and table name from vertex metadata (was: Impala Hook: Get

[jira] [Updated] (ATLAS-3290) Impala Hook: Get database name and table name from vertex metadata

[ https://issues.apache.org/jira/browse/ATLAS-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated ATLAS-3290: - Description: The column name in Impala lineage record may not contain its database name and its table name.

[jira] [Created] (ATLAS-3290) Impala Hook: Get database name and table name from vertex metadata

Na Li created ATLAS-3290: Summary: Impala Hook: Get database name and table name from vertex metadata Key: ATLAS-3290 URL: https://issues.apache.org/jira/browse/ATLAS-3290 Project: Atlas Issue

[jira] [Commented] (ATLAS-3277) Add default atlas conf path in the import-* scripts

[ https://issues.apache.org/jira/browse/ATLAS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866972#comment-16866972 ] ASF subversion and git services commented on ATLAS-3277: Commit

[jira] [Commented] (ATLAS-3277) Add default atlas conf path in the import-* scripts

[ https://issues.apache.org/jira/browse/ATLAS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866966#comment-16866966 ] Madhan Neethiraj commented on ATLAS-3277: - +1 for the patch. Thanks [~vishal.suvagia]! > Add

[jira] [Commented] (ATLAS-3277) Add default atlas conf path in the import-* scripts

[ https://issues.apache.org/jira/browse/ATLAS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866926#comment-16866926 ] Vishal Suvagia commented on ATLAS-3277: --- Updated patch to improvise conditional logic. > Add

[jira] [Updated] (ATLAS-3277) Add default atlas conf path in the import-* scripts

[ https://issues.apache.org/jira/browse/ATLAS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated ATLAS-3277: -- Attachment: ATLAS-3277.01.patch > Add default atlas conf path in the import-* scripts >

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

[ https://issues.apache.org/jira/browse/ATLAS-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866719#comment-16866719 ] Bolke de Bruin commented on ATLAS-3153: --- Sure will do. We should have some overlap :) > Support

Scaling Apache Atlas Horizontally

Hello, We are facing some scalability and latency issues with Apache Atlas. Today we have Atlas installed as single node. Some of simple get entity calls (with lots of relationships) are taking lot of time. In our data, we have lot of deep relationships. Current state: 1. Atlas + JanusGraph

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

[ https://issues.apache.org/jira/browse/ATLAS-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866366#comment-16866366 ] Saqeeb Shaikh commented on ATLAS-3153: -- [~bolke], Can we have webx session to understand the issue

[GitHub] [atlas] arempter commented on issue #58: [ATLAS-3261] Set kafka user as current principal for Ranger Authorization

arempter commented on issue #58: [ATLAS-3261] Set kafka user as current principal for Ranger Authorization URL: https://github.com/apache/atlas/pull/58#issuecomment-502993992 @mneethiraj is there something more that should be done here?

[GitHub] [atlas] chaitalicod closed pull request #30: ATLAS-3001 :- Fix AtlasClientV2.updateClassifications() throws serialization error due to wrong status code set in API

chaitalicod closed pull request #30: ATLAS-3001 :- Fix AtlasClientV2.updateClassifications() throws serialization error due to wrong status code set in API URL: https://github.com/apache/atlas/pull/30 This is an automated

[GitHub] [atlas] chaitalicod commented on issue #30: ATLAS-3001 :- Fix AtlasClientV2.updateClassifications() throws serialization error due to wrong status code set in API

chaitalicod commented on issue #30: ATLAS-3001 :- Fix AtlasClientV2.updateClassifications() throws serialization error due to wrong status code set in API URL: https://github.com/apache/atlas/pull/30#issuecomment-502975184 got committed to master, closing PR

Fwd: [ANNOUNCE] Apache Atlas 1.2.0 released

Hi All, The Apache Atlas team is happy to announce the release of Apache Atlas - version 1.2.0. Atlas is a scalable and extensible set of core foundational governance services – enabling enterprises to effectively and efficiently meet their compliance requirements within Hadoop and allows