Re: Dev cycle for changes to atlas dashboard

[Keval Bhatt]

Hi Melinda,

You can go to dashboardv3 folder and run dev proxy server instead of using
Atlas server for UI development.

Steps to run UI dev server.

   1. Go to dashboardv3
   2. run npm install
   3. npm start

and in the browser go to http://localhost:. this is the live server so
after file change, you need to refresh the browser.

Note: Internally it will use proxy to Atlas API server (
http://localhost:21000). You can change the proxy Ip =>
https://github.com/apache/atlas/blob/master/dashboardv3/gruntfile.js#L63

Thanks

[jira] [Commented] (ATLAS-3602) Provide option to Ignore relationship attribute mapping in getAndCacheEntity()

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3602:


Commit 28caa643dab596a195bb47d4e868cec2fedde411 in atlas's branch 
refs/heads/branch-2.0 from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=28caa64 ]

ATLAS-3602: Provide option to Ignore relationship attribute mapping in 
getAndCacheEntity()

(cherry picked from commit a6cdb608b21d8c4d1c843ca7d2d974fc2b65b93c)


> Provide option to Ignore relationship attribute mapping in getAndCacheEntity()
> --
>
> Key: ATLAS-3602
> URL: https://issues.apache.org/jira/browse/ATLAS-3602
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3602.001.patch
>
>
> Provide option to Ignore relationship attribute mapping in getAndCacheEntity()



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

[jira] [Commented] (ATLAS-3602) Provide option to Ignore relationship attribute mapping in getAndCacheEntity()

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3602:


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

ATLAS-3602: Provide option to Ignore relationship attribute mapping in 
getAndCacheEntity()


> Provide option to Ignore relationship attribute mapping in getAndCacheEntity()
> --
>
> Key: ATLAS-3602
> URL: https://issues.apache.org/jira/browse/ATLAS-3602
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3602.001.patch
>
>
> Provide option to Ignore relationship attribute mapping in getAndCacheEntity()



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

Re: Review Request 72069: ATLAS-3602: Provide option to Ignore relationship attribute mapping in getAndCacheEntity()

[Sarath Subramanian]

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

(Updated Feb. 3, 2020, 2:31 p.m.)


Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Mandar Ambawane, 
mayank jain, Nixon Rodrigues, and Sidharth Mishra.


Changes
---

renamed property


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


Repository: atlas


Description
---

Provide option to Ignore relationship attribute mapping in getAndCacheEntity()


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/AtlasConfiguration.java 6e726f25b 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
 01e339d23 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
 e427a59e7 


Diff: https://reviews.apache.org/r/72069/diff/4/

Changes: https://reviews.apache.org/r/72069/diff/3-4/


Testing
---

Manually validated and perf improvement seen during add/delete classifications


Thanks,

Sarath Subramanian

Re: Review Request 72069: ATLAS-3602: Provide option to Ignore relationship attribute mapping in getAndCacheEntity()

[Madhan Neethiraj]

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


Fix it, then Ship it!





repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
Lines 126 (patched)


- consider renaming IGNORE_RELATIONSHIP_ATTRIBUTES to 
ENTITY_CHANGE_NOTIFY_IGNORE_RELATIONSHIP_ATTRIBUTES, in EntityGraphMapper and 
AtlasConfiguration.
- also, consider updating the property name 
"atlas.ignore.relationship.attributes.for.entity.get.and.cache" to 
"atlas.entity.change.notify.ignore.relationship.attributes"


- Madhan Neethiraj


On Feb. 3, 2020, 8:55 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72069/
> ---
> 
> (Updated Feb. 3, 2020, 8:55 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Mandar Ambawane, 
> mayank jain, Nixon Rodrigues, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3602
> https://issues.apache.org/jira/browse/ATLAS-3602
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Provide option to Ignore relationship attribute mapping in getAndCacheEntity()
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasConfiguration.java 6e726f25b 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
>  01e339d23 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
>  e427a59e7 
> 
> 
> Diff: https://reviews.apache.org/r/72069/diff/3/
> 
> 
> Testing
> ---
> 
> Manually validated and perf improvement seen during add/delete classifications
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 72069: ATLAS-3602: Provide option to Ignore relationship attribute mapping in getAndCacheEntity()

[Sarath Subramanian]

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

(Updated Feb. 3, 2020, 12:55 p.m.)


Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Mandar Ambawane, 
mayank jain, Nixon Rodrigues, and Sidharth Mishra.


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


Repository: atlas


Description
---

Provide option to Ignore relationship attribute mapping in getAndCacheEntity()


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/AtlasConfiguration.java 6e726f25b 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
 01e339d23 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
 e427a59e7 


Diff: https://reviews.apache.org/r/72069/diff/3/

Changes: https://reviews.apache.org/r/72069/diff/2-3/


Testing
---

Manually validated and perf improvement seen during add/delete classifications


Thanks,

Sarath Subramanian

[jira] [Commented] (ATLAS-488) Atlas service scalability

[Zhengyi Liu (Jira)]

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

Zhengyi Liu commented on ATLAS-488:
---

Hey [~vmadugun], I am working on setting up an Atlas production env and I am 
curious about the progress of this task. Seems like we didn't put extra effort 
since last update and I am curious how would that block us from adopting Atlas 
and eventually ingest 40 million + entities. Is there an existing benchmark 
from the industry peers that prove the scalability of the existing solution? I 
can see how that would give people confidence even with current approach 
(single node with HA).

> Atlas service scalability
> -
>
> Key: ATLAS-488
> URL: https://issues.apache.org/jira/browse/ATLAS-488
> Project: Atlas
>  Issue Type: Improvement
>Reporter: venkata madugundu
>Priority: Major
>
> Requirement -- We are looking for ways to have Atlas service running in 
> multiple instances for Cloud deployment, and this requirement is kind of 
> crucial to the adoption of Atlas.
> On the dev discussion forum, I had discussed earlier (Jan 25th) on the 
> requirement to run multiple instances of Atlas service/runtime for horizontal 
> scale. Per answers that we got from Hemanth, Atlas has a current limitation 
> that only instance can be active at any given point of time for a couple of 
> reasons. Few reasons cited were ...
> 1) For performance reasons, the typesystem is cached in-memory. Type lookup 
> is needed for query evaluation, instance serialization/deserialization etc.,
> 2) Titan locks for Hbase transactions, causing performance degradation.
> Considering the above reasons, among them,
>  #1 can be mitigated in our scenarios. The types that we create are more or 
> less design-time application data-models (metamodels) and they do not change 
> at runtime. So if I were to pre-register types with Atlas before my cluster 
> is up, I am hoping #1 is not an issue. In the sense, how many ever Atlas 
> instances come up, all would have the same state, which would mean I am 
> guaranteed API correctness.
> I am not so sure how we can avoid #2. I neither understand the persistence 
> mapping of metadata to the graph(Atlas) and the mapping of graph to the Hbase 
> (Titan) to comment on whether #2 is really a problem for us in terms of 
> lock-contention. Atlas as REST API inherently does not offer any 
> "transaction" like facility to run a set of API for its end-users. Given 
> that, we are more likely to implement some kind of optimistic locking 
> strategy to avoid data inconsistencies.
> Are there are any other reasons, that you can think of why multiple Atlas 
> runtime instances cannot be talking to a single Hbase cluster for horizontal 
> scale ?



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

Re: Review Request 72069: ATLAS-3602: Provide option to Ignore relationship attribute mapping in getAndCacheEntity()

[Sarath Subramanian]

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

(Updated Feb. 3, 2020, 12:30 p.m.)


Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Mandar Ambawane, 
mayank jain, Nixon Rodrigues, and Sidharth Mishra.


Changes
---

addressed review comments.


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


Repository: atlas


Description
---

Provide option to Ignore relationship attribute mapping in getAndCacheEntity()


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
 01e339d23 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 dc4c399ae 


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

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


Testing
---

Manually validated and perf improvement seen during add/delete classifications


Thanks,

Sarath Subramanian

Re: Review Request 72046: ATLAS-3534 EntityREST changes to allow namespace attributes to be added, updated and deleted to an entity instance

[Mandar Ambawane]

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

(Updated Feb. 3, 2020, 7:44 p.m.)


Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
and Sarath Subramanian.


Changes
---

Addressed review comments. Added single API to create, update and delete 
Namespace attribtues.


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


Repository: atlas


Description
---

Created separate endpoints to associate Namespace attributes to entity


Diffs (updated)
-

  common/src/main/java/org/apache/atlas/repository/Constants.java 0b28243 
  intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 2054513 
  intg/src/main/java/org/apache/atlas/model/instance/AtlasEntity.java 1b033b9 
  intg/src/main/java/org/apache/atlas/type/AtlasNamespaceType.java a141d4a 
  intg/src/main/java/org/apache/atlas/type/AtlasTypeRegistry.java 97e27d0 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEntityStore.java
 928c70d 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
 25284e9 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
 e427a59 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 dc4c399 
  webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 6845121 


Diff: https://reviews.apache.org/r/72046/diff/9/

Changes: https://reviews.apache.org/r/72046/diff/8-9/


Testing
---

Basic testing is done.

Create NamespaceDef sports:

curl --location --request POST 
'http://localhost:21000/api/atlas/v2/types/typedefs' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic YWRtaW46YWRtaW4=' \
--data-raw '{
"namespaceDefs": [
{
"name": "sports",
"description": "Sample sports",
"serviceType": "NAMESPACES",
"typeVersion": "1.0",
"attributeDefs": [
{
"name": "sports_name",
"typeName": "string",
"options": {
"applicableEntityTypes": "[\"hdfs_path\", 
\"hive_table\"]",
"maxStrLength": "50"
},
"cardinality": "SINGLE",
"isIndexable": true,
"isOptional": true,
"includeInNotification": true,
"isUnique": false
},
{
"name": "no_of_players",
"typeName": "int",
"options": {
"applicableEntityTypes": "[\"hdfs_path\", 
\"hive_column\"]"
},
"cardinality": "SINGLE",
"isIndexable": true,
"isOptional": true,
"includeInNotification": true,
"isUnique": false
}
]
}
]
}'


Create NamespaceDef vehicle:

curl --location --request POST 
'http://localhost:21000/api/atlas/v2/types/typedefs' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic YWRtaW46YWRtaW4=' \
--data-raw '{
"namespaceDefs": [
{
"name": "vehicle",
"description": "Sample vehicle",
"serviceType": "NAMESPACES",
"typeVersion": "1.0",
"attributeDefs": [
{
"name": "vehicle_name",
"typeName": "string",
"options": {
"applicableEntityTypes": "[\"hdfs_path\", 
\"hive_table\"]",
"maxStrLength": "50"
},
"cardinality": "SINGLE",
"isIndexable": true,
"isOptional": true,
"includeInNotification": true,
"isUnique": false
},
{
"name": "no_of_wheels",
"typeName": "int",
"options": {
"applicableEntityTypes": "[\"hdfs_path\", 
\"hive_column\"]"
},
"cardinality": "SINGLE",
"isIndexable": true,
"isOptional": true,
"includeInNotification": true,
"isUnique": false
}
]
}
]
}'


Create hdfs_path entity:

curl --location --request POST 'http://localhost:21000/api/atlas/v2/entity' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic YWRtaW46YWRtaW4=' \
--data-raw '{
"entity": {
"guid": "-1",
"typeName": "hdfs_path",
"attributes": {
"clusterName": "cm",
"desc

[jira] [Updated] (ATLAS-3607) UI: changes to create namespace type definitions and define namespace attributes

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3607:
---
Attachment: ATLAS-3607.patch

> UI: changes to create namespace type definitions and define namespace 
> attributes
> 
>
> Key: ATLAS-3607
> URL: https://issues.apache.org/jira/browse/ATLAS-3607
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3607.patch
>
>




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

Re: Atlas Contributor Request

[Madhan Neethiraj]

Sourav,

Thanks for your interest in contributing to Apache Atlas. You have been added 
as a contributor. Welcome to Apache Atlas community!

Regards,
Madhan

On 2/3/20, 2:33 AM, "Sourav Banerjee"  
wrote:

Hi Atlas Team,

I am interested in contributing to Apache Atlas project, kindly add me as a
contributor.

My Jira id is sourav.banerjee

--
Thanks and Regards,
Sourav Banerjee

Re: Review Request 72069: ATLAS-3602: Provide option to Ignore relationship attribute mapping in getAndCacheEntity()

[Madhan Neethiraj]

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




repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
Lines 80 (patched)


- 'applicationProperties' seems to be referenced only in the constructor. 
If true, this doesn't have to be an instance member. Please review.
- consider replacing ApplicationProperties.get() with a constructor 
parameter "Configuration config" (i.e. use DI) - see DiscoveryREST.java for 
such usage



repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
Lines 81 (patched)


having 'ignoreRelationshipAttributes' as an instance member of 
AtlasInstanceConverter will cause all use of AtlasInstanceConverter to ignore 
relationship-attributes. Instead, consider localizing this to 
getAndCacheEntity(), with a parameter to this method and have the caller pass 
appropriate flag (from notification/audit modules).
  
  public AtlasEntity getAndCacheEntity(String guid) {
return getAndCacheEntity(guid, false); // current behaviour
  }
  
  public AtlasEntity getAndCacheEntity(String guid, boolean 
ignoreRelationshipAttributes) {
...
  }



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
Lines 576 (patched)


EntityGraphRetriever already has an instance member 
'ignoreRelationshipAttr'; method parameter 'ignoreRelationshipAttributes' here 
can be avoided by having the caller (AtlasInstanceConverter) use different 
instance of EntityGraphRetriever:

  class AtlasInstanceConverter {
private final EntityGraphRetriever entityGraphRetriever;
private final EntityGraphRetriever 
entityGraphRetrieverIgnoreRelationshipAttributes;

..

public AtlasInstanceConverter(...) {
  this.entityGraphRetriever = new 
EntityGraphRetriever(typeRegistry, false);
  this.entityGraphRetrieverIgnoreRelationshipAttributes = new 
EntityGraphRetriever(typeRegistry, true);
  ...
}
  }

Please review.


- Madhan Neethiraj


On Jan. 31, 2020, 7:23 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72069/
> ---
> 
> (Updated Jan. 31, 2020, 7:23 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Mandar Ambawane, 
> mayank jain, Nixon Rodrigues, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3602
> https://issues.apache.org/jira/browse/ATLAS-3602
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Provide option to Ignore relationship attribute mapping in getAndCacheEntity()
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
>  01e339d23 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
>  dc4c399ae 
> 
> 
> Diff: https://reviews.apache.org/r/72069/diff/1/
> 
> 
> Testing
> ---
> 
> Manually validated and perf improvement seen during add/delete classifications
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Updated] (ATLAS-3554) UI: changes to display/add/update/delete namespace attributes for entities in entity details page

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3554:
---
Summary: UI: changes to display/add/update/delete namespace attributes for 
entities in entity details page  (was: UI: changes to display namespace 
attributes for entities)

> UI: changes to display/add/update/delete namespace attributes for entities in 
> entity details page
> -
>
> Key: ATLAS-3554
> URL: https://issues.apache.org/jira/browse/ATLAS-3554
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>




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

[jira] [Created] (ATLAS-3607) UI: changes to create namespace type definitions and define namespace attributes

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3607:
--

 Summary: UI: changes to create namespace type definitions and 
define namespace attributes
 Key: ATLAS-3607
 URL: https://issues.apache.org/jira/browse/ATLAS-3607
 Project: Atlas
  Issue Type: Improvement
Reporter: Keval Bhatt
Assignee: Keval Bhatt






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

Atlas Contributor Request

[Sourav Banerjee]

Hi Atlas Team,

I am interested in contributing to Apache Atlas project, kindly add me as a
contributor.

My Jira id is sourav.banerjee

--
Thanks and Regards,
Sourav Banerjee

Re: Review Request 72076: ATLAS-3606 : Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal Shah]

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

(Updated Feb. 3, 2020, 11:53 a.m.)


Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

When we create table in hive, value of attributes cluster_name, owner, 
query_text is missing in the corresponding hive_process entity on Atlas


Diffs
-

  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/events/BaseHiveEvent.java
 60dc1147f 


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


Testing (updated)
---

1) CREATETABLE operation
2) CREATETABLE_AS_SELECT operation 
3) CREATEVIEW operation
4) ALTERVIEW_AS operation
5) IMPORT operation
6) EXPORT operation, here owner is N/A

tested by changing user in hive and then creating operation, the owner in 
hive_process is reflected


Thanks,

Pinal Shah

Review Request 72076: ATLAS-3606 : Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal Shah]

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

Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

When we create table in hive, value of attributes cluster_name, owner, 
query_text is missing in the corresponding hive_process entity on Atlas


Diffs
-

  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/events/BaseHiveEvent.java
 60dc1147f 


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


Testing
---

1) CREATETABLE operation
2) CREATETABLE_AS_SELECT operation 

tested by changing user in hive and then creating operation, the owner in 
hive_process is reflected


Thanks,

Pinal Shah

[jira] [Updated] (ATLAS-3606) Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal (Jira)]

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

Pinal updated ATLAS-3606:
-
Attachment: ATLAS-3606.patch

> Hive Hook: Missing HIVE_PROCESS attribute values
> 
>
> Key: ATLAS-3606
> URL: https://issues.apache.org/jira/browse/ATLAS-3606
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Attachments: ATLAS-3606.patch
>
>
> In Hive Producer, When hive_process entity gets created during many 
> operations eg. "CREATETABLE", "CREATETABLE_AS_SELECT "
> cluster_name, owner, query_text 
>  values are missing



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

[jira] [Updated] (ATLAS-3606) Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal (Jira)]

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

Pinal updated ATLAS-3606:
-
Attachment: (was: ATLAS-3606.patch)

> Hive Hook: Missing HIVE_PROCESS attribute values
> 
>
> Key: ATLAS-3606
> URL: https://issues.apache.org/jira/browse/ATLAS-3606
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> In Hive Producer, When hive_process entity gets created during many 
> operations eg. "CREATETABLE", "CREATETABLE_AS_SELECT "
> cluster_name, owner, query_text 
>  values are missing



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

[jira] [Updated] (ATLAS-3606) Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal (Jira)]

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

Pinal updated ATLAS-3606:
-
Attachment: ATLAS-3606.patch

> Hive Hook: Missing HIVE_PROCESS attribute values
> 
>
> Key: ATLAS-3606
> URL: https://issues.apache.org/jira/browse/ATLAS-3606
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Attachments: ATLAS-3606.patch
>
>
> In Hive Producer, When hive_process entity gets created during many 
> operations eg. "CREATETABLE", "CREATETABLE_AS_SELECT "
> cluster_name, owner, query_text 
>  values are missing



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

[jira] [Updated] (ATLAS-3606) Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal (Jira)]

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

Pinal updated ATLAS-3606:
-
Description: 
In Hive Producer, When hive_process entity gets created during many operations 
eg. "CREATETABLE", "CREATETABLE_AS_SELECT "
cluster_name, owner, query_text 
 values are missing

  was:
In Hive Producer, When hive_process entity gets created during many operations 
eg. CREATETABLE, CREATETABLE_AS_SELECT 
Cluster name, Owner, Query text 
values are missing


> Hive Hook: Missing HIVE_PROCESS attribute values
> 
>
> Key: ATLAS-3606
> URL: https://issues.apache.org/jira/browse/ATLAS-3606
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> In Hive Producer, When hive_process entity gets created during many 
> operations eg. "CREATETABLE", "CREATETABLE_AS_SELECT "
> cluster_name, owner, query_text 
>  values are missing



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

[jira] [Updated] (ATLAS-3606) Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal (Jira)]

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

Pinal updated ATLAS-3606:
-
Description: 
In Hive Producer, When hive_process entity gets created during many operations 
eg. CREATETABLE, CREATETABLE_AS_SELECT 
Cluster name, Owner, Query text 
values are missing

> Hive Hook: Missing HIVE_PROCESS attribute values
> 
>
> Key: ATLAS-3606
> URL: https://issues.apache.org/jira/browse/ATLAS-3606
> Project: Atlas
>  Issue Type: Bug
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> In Hive Producer, When hive_process entity gets created during many 
> operations eg. CREATETABLE, CREATETABLE_AS_SELECT 
> Cluster name, Owner, Query text 
> values are missing



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

[jira] [Created] (ATLAS-3606) Hive Hook: Missing HIVE_PROCESS attribute values

[Pinal (Jira)]

Pinal created ATLAS-3606:


 Summary: Hive Hook: Missing HIVE_PROCESS attribute values
 Key: ATLAS-3606
 URL: https://issues.apache.org/jira/browse/ATLAS-3606
 Project: Atlas
  Issue Type: Bug
Reporter: Pinal
Assignee: Pinal






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