[jira] [Updated] (ATLAS-2987) Update component versions of Atlas to use Hadoop3, HBase2 and Solr6

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2987:
--
Description: 
Update Component version of Atlas to the following:
 * Hadoop 3.0.0
 * HBase 2.0.0
 * Solr 6.6.1
 * Kafka 1.0.0
 * Zookeeper 3.4.6
 * Hive 3.0.0

  was:
Update Component version of Atlas to the followinf:
 * Hadoop 3.0.0
 * HBase 2.0.0
 * Solr 6.6.1
 * Kafka 1.0.0
 * Zookeeper 3.4.6
 * Hive 3.0.0


> Update component versions of Atlas to use Hadoop3, HBase2 and Solr6
> ---
>
> Key: ATLAS-2987
> URL: https://issues.apache.org/jira/browse/ATLAS-2987
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0
>
>
> Update Component version of Atlas to the following:
>  * Hadoop 3.0.0
>  * HBase 2.0.0
>  * Solr 6.6.1
>  * Kafka 1.0.0
>  * Zookeeper 3.4.6
>  * Hive 3.0.0



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

[jira] [Updated] (ATLAS-2987) Update component versions of Atlas to use Hadoop3, HBase2 and Solr6

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2987:
--
Description: 
Update Component version of Atlas to the following:
 * Hadoop 3.0.0
 * Hive 3.0.0
 * HBase 2.0.0
 * Solr 6.6.1
 * Kafka 1.0.0
 * Zookeeper 3.4.6

  was:
Update Component version of Atlas to the following:
 * Hadoop 3.0.0
 * HBase 2.0.0
 * Solr 6.6.1
 * Kafka 1.0.0
 * Zookeeper 3.4.6
 * Hive 3.0.0


> Update component versions of Atlas to use Hadoop3, HBase2 and Solr6
> ---
>
> Key: ATLAS-2987
> URL: https://issues.apache.org/jira/browse/ATLAS-2987
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0
>
>
> Update Component version of Atlas to the following:
>  * Hadoop 3.0.0
>  * Hive 3.0.0
>  * HBase 2.0.0
>  * Solr 6.6.1
>  * Kafka 1.0.0
>  * Zookeeper 3.4.6



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

[jira] [Created] (ATLAS-2987) Update component versions of Atlas to use Hadoop3, HBase2 and Solr6

[Sarath Subramanian (JIRA)]

Sarath Subramanian created ATLAS-2987:
-

 Summary: Update component versions of Atlas to use Hadoop3, HBase2 
and Solr6
 Key: ATLAS-2987
 URL: https://issues.apache.org/jira/browse/ATLAS-2987
 Project: Atlas
  Issue Type: Task
  Components:  atlas-core
Affects Versions: trunk
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.0.0


Update Component version of Atlas to the followinf:
 * Hadoop 3.0.0
 * HBase 2.0.0
 * Solr 6.6.1
 * Kafka 1.0.0
 * Zookeeper 3.4.6
 * Hive 3.0.0



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

[jira] [Created] (ATLAS-2986) REST calls during import operations include unnecessary doAs parameter

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-2986:
---

 Summary: REST calls during import operations include unnecessary 
doAs parameter
 Key: ATLAS-2986
 URL: https://issues.apache.org/jira/browse/ATLAS-2986
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.1.0, 0.8.3, 1.0.0, 0.8.2, 0.8.1
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


REST calls to Atlas server during import operations include doAs query 
parameter, which is unnecessary. This should be fixed to avoid sending doAs 
parameter, since the logged in username is same as the username sent in doAs 
parameter.

 



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

Review Request 69495: ATLAS-2986: updated AtlasClient to skip doAs query parameter when username is same as the logged in user

[Madhan Neethiraj]

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

Review request for atlas, Ashutosh Mestry, keval bhatt, Nixon Rodrigues, and 
Sarath Subramanian.


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


Repository: atlas


Description
---

updated AtlasClient to skip doAs query parameter when username is same as the 
logged in user


Diffs
-

  client/common/src/main/java/org/apache/atlas/security/SecureClientUtils.java 
550ef5a81 


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


Testing
---

- performed import-hive and verified that doAs parameter is not sent by 
AtlasClient in REST calls to Atlas server
- pre-commit tests run: 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/860/


Thanks,

Madhan Neethiraj

[jira] [Commented] (ATLAS-2951) Lineage Improvments

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat commented on ATLAS-2951:


[~kevalbhatt] [~abhib4] Can we please add screenshots for the "before" and 
"after" experience for each subtask so we can understand how the new behavior 
will get shown in the UI?

> Lineage Improvments
> ---
>
> Key: ATLAS-2951
> URL: https://issues.apache.org/jira/browse/ATLAS-2951
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
>




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

[jira] [Commented] (ATLAS-2976) UI : Show entity specific icon for the lineage node

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat commented on ATLAS-2976:


[~kevalbhatt] Can we please add screenshot for what this would look like in UI 
after this behavior change?

> UI : Show entity specific icon for the lineage node
> ---
>
> Key: ATLAS-2976
> URL: https://issues.apache.org/jira/browse/ATLAS-2976
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-2976-1.patch, ATLAS-2976-2.patch, 
> ATLAS-2976-3.patch, ATLAS-2976.patch
>
>




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

[jira] [Commented] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat commented on ATLAS-2983:


I don't think we should remove the capability to add entities from the UI as a 
convenience for customers that want to track metadata for entities from Kafka 
but do not have the ability run Atlas bridge/hook in those Kafka environments.

> Fixes and clean up for Atlas Kafka bridge utility
> -
>
> Key: ATLAS-2983
> URL: https://issues.apache.org/jira/browse/ATLAS-2983
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: ATLAS-2983.patch
>
>
> # Currently, import-kafka.sh script allows selective kafka topic import by 
> providing -t or --topic option, but the script only checks for the topics 
> which start with the topic name provided and does not support regular 
> expression based selective import. With the fix provided, regex patterns can 
> be used along with -t as well as -f (file based import) option
>  # When a bad import-kafka command is being fired, following usage is being 
> printed on the console. Here, option should be -t instead of -n. Have fixed 
> this minor issue, along with some more text changes
>  ** import-kafka.sh [*-n*  OR --topic ]
>  # Since we now have support for kakfa bridge and hbase hook/bridge, option 
> for creating entities for the following in Atlas UI could be removed 
>  ## hbase_table
>  ## hbase_column
>  ## hbase_column_family
>  ## kafka_topic
>  ## hbase_namespace



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

Re: Review Request 69494: ATLAS-2985 fixes for delete handlers and relationship store

[Madhan Neethiraj]

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




repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
Lines 106 (patched)


Couple of comments:

1. If the entity was already deleted in this request (i.e. 
requestContext.isDeletedEntity(guid) is true), further delete attempts should 
be skipped. 'if' condition here should be modified as:

  if ((softDelete && state == DELETED) || 
requestContext.isDeletedEntity(guid)) {
// skip
continue;
  }

2. Please make sure that deleting an already-deleted entity doesn't 
generate an entity-delete event. Else applications processing the events might 
end up with incorrect state - by deleting another active entity with the same 
qualifiedName (if exists); applications are likely to rely on matching an 
entity with qualifiedName, instead of guids.

Please review and update.



repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
Lines 151 (patched)


Consider rearranging the condition as below, for better readability:

  if (!isInternal && (softDelete && getState(edge) == DELETED))
  
Also, comment at line #106 about skipping events applies here as well.



repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
Lines 185 (patched)


Please review comments at line #106 for the change here as well.


- Madhan Neethiraj


On Nov. 30, 2018, 4:36 p.m., Graham Wallis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69494/
> ---
> 
> (Updated Nov. 30, 2018, 4:36 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2985: critical fixes for delete handlers and relationship dtore
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
>  c57e30ab5cdb34aee1cb13c463b1b0af827d2a2e 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/HardDeleteHandlerV1.java
>  edf1eed4c3efdd41f77155e51c8f2908b3dbbab2 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasRelationshipStoreV2.java
>  86cc98cda61d85954fd227501d691e3a3b542611 
> 
> 
> Diff: https://reviews.apache.org/r/69494/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with full run of Egeria CTS suite.
> 
> 
> Thanks,
> 
> Graham Wallis
> 
>

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

[Graham Wallis (JIRA)]

Graham Wallis created ATLAS-2985:


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






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

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

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2985:
--

Review is here: https://reviews.apache.org/r/69494/

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




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

Review Request 69494: ATLAS-2985 fixes for delete handlers and relationship store

[Graham Wallis]

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

Review request for atlas.


Repository: atlas


Description
---

ATLAS-2985: critical fixes for delete handlers and relationship dtore


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
 c57e30ab5cdb34aee1cb13c463b1b0af827d2a2e 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/HardDeleteHandlerV1.java
 edf1eed4c3efdd41f77155e51c8f2908b3dbbab2 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasRelationshipStoreV2.java
 86cc98cda61d85954fd227501d691e3a3b542611 


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


Testing
---

Tested with full run of Egeria CTS suite.


Thanks,

Graham Wallis

[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas

[Graham Wallis (JIRA)]

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

Graham Wallis updated ATLAS-1773:
-
Attachment: ATLAS-2985-2018-11-30.patch

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-11-14.patch, 
> ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



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

Re: Review Request 69435: ATLAS-2976 : UI : Show entity specific icon for the lineage node

[keval bhatt]

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

(Updated Nov. 30, 2018, 1:27 p.m.)


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


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


Repository: atlas


Description
---

Add Icon for specific entity and render in the Lineage


Diffs (updated)
-

  dashboardv2/gruntfile.js 1d54a8168 
  dashboardv2/package.json ca49142e2 
  dashboardv2/public/css/scss/graph.scss 37424d148 
  dashboardv2/public/css/scss/override.scss ca5d1e877 
  dashboardv2/public/css/scss/relationship.scss f3e98b622 
  dashboardv2/public/css/scss/theme.scss afec6f672 
  dashboardv2/public/img/entity-icon/avro/avro.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/avro/disabled/avro.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/default/db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/default/disabled/db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/default/disabled/process.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/default/disabled/table.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/default/process.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/default/table.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/falcon/disabled/falcon.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/falcon/falcon.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hadoop/disabled/hadoop.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hadoop/hadoop.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/disabled/hbase.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/disabled/hbase_column.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/disabled/hbase_column_family.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/disabled/hbase_table.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/hbase.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/hbase_column.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/hbase_column_family.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hbase/hbase_table.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/disabled/hive.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/disabled/hive_column.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/disabled/hive_column_lineage.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/disabled/hive_db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/disabled/hive_process.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/disabled/hive_storagedesc.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/disabled/hive_table.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/hive.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/hive_column.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/hive_column_lineage.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/hive_db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/hive_process.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/hive_storagedesc.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/hive/hive_table.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/kafka/disabled/jms_topic.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/kafka/disabled/kafka.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/kafka/jms_topic.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/kafka/kafka.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/disabled/rdbms.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/disabled/rdbms_column.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/disabled/rdbms_db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/disabled/rdbms_table.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/rdbms.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/rdbms_column.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/rdbms_db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/rdbms/rdbms_table.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/spark/spark.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/sqoop/disabled/sqoop.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/sqoop/disabled/sqoop_db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/sqoop/disabled/sqoop_process.png 
PRE-CREATION 
  dashboardv2/public/img/entity-icon/sqoop/sqoop.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/sqoop/sqoop_db.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/sqoop/sqoop_process.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/storm/disabled/storm.png PRE-CREATION 
  dashboardv2/public/img/entity-icon/storm/disabled/storm_bolt.png 

[jira] [Updated] (ATLAS-2976) UI : Show entity specific icon for the lineage node

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-2976:
---
Attachment: ATLAS-2976-3.patch

> UI : Show entity specific icon for the lineage node
> ---
>
> Key: ATLAS-2976
> URL: https://issues.apache.org/jira/browse/ATLAS-2976
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-2976-1.patch, ATLAS-2976-2.patch, 
> ATLAS-2976-3.patch, ATLAS-2976.patch
>
>




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