[jira] [Assigned] (ATLAS-1789) Fix Findbugs problems

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-1789:


Assignee: (was: Jan Hentschel)

> Fix Findbugs problems
> -
>
> Key: ATLAS-1789
> URL: https://issues.apache.org/jira/browse/ATLAS-1789
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jan Hentschel
>Priority: Minor
>
> This is an umbrella ticket for fixing the Findbugs errors throughout the 
> different modules.



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

[jira] [Commented] (ATLAS-3114) Issue with concurrent bulk inserts for entities

[Nallapati, Sreenivasulu (JIRA)]

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

Nallapati, Sreenivasulu commented on ATLAS-3114:


Hi [~lma], 

We were attaching the list of child entity ids to parent entity(Ex. columns to 
table). Whereas you are attaching the parent id to the child entity (Ex. table 
to column). 

Did you use the model that we attached - with this model we are not able to see 
the relationships between entities.  

or If you have created different model, please share the model

 

Thanks

Sreeni

> Issue with concurrent bulk inserts for entities
> ---
>
> Key: ATLAS-3114
> URL: https://issues.apache.org/jira/browse/ATLAS-3114
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ayush Nigam
>Assignee: chaitali borole
>Priority: Major
> Attachments: ATLAS-3114.patch, AtlasClientV2Test.java, Error.txt, 
> model.json
>
>
> We have a model with tables having attribute 'columns'  in which we are 
> attaching list of object ids for all columns once these are created. We are 
> using clientV2 java APIs.
> We are doing bulk operation for columns and parallelizing the tables.
> Sometimes the issue is that bulk creation for columns is successful,i.e. 
> atlas don't throw any exception but we get some columns as created,some as 
> updated,whereas as none of the columns existed before.Even it misses out some 
> entities while creating.Some are created and some are just silently missed 
> without throwing an exception.
> So to sum up issue is there for concurrent bulk create/update calls.It works 
> for concurrent single entity create/update calls.
>  



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

Re: Review Request 70505: CDPD-252:parse metadata/Lineage files generated by Impala

[Na Li via Review Board]

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




addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageVertex.java
Lines 27 (patched)


can you make the type to be Integer? So it is consistent with the id type 
ion LineageEdge "private List sources;"


- Na Li


On April 18, 2019, 8:33 p.m., Xinran Tinney wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70505/
> ---
> 
> (Updated April 18, 2019, 8:33 p.m.)
> 
> 
> Review request for atlas and Na Li.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> the code is implemented in Java.
> 
> 1) It takes Impala file location and file name prefix as input. 
> 2) It reads its own record-keeping file to get the offset of the Impala file 
> it has already read. Then read the new records from Impala file, update the 
> record-keeping file to append the new offset of the Impala file.
> 3) It parses the new records from Impala file into internal data structure as 
> output.
> 4) If the Impala file name has changed, start a new file for record-keeping 
> and remove the old record-keeping file.
> 5) Implemented unit test to verify the behavior.
> 
> 
> Diffs
> -
> 
>   addons/impala-bridge/impala1.txt PRE-CREATION 
>   addons/impala-bridge/impala2.txt PRE-CREATION 
>   addons/impala-bridge/pom.xml PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/ImpalaBridge.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageEdge.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageQuery.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageVertex.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/bridge/TestImpalaBridge.java
>  PRE-CREATION 
>   pom.xml 76341388b 
> 
> 
> Diff: https://reviews.apache.org/r/70505/diff/1/
> 
> 
> Testing
> ---
> 
> unit testing and mvn clean install -DskipTests
> 
> 
> Thanks,
> 
> Xinran Tinney
> 
>

Re: Review Request 70505: CDPD-252:parse metadata/Lineage files generated by Impala

[Na Li via Review Board]

> On April 19, 2019, 3:27 p.m., Na Li wrote:
> > addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageVertex.java
> > Lines 27 (patched)
> > 
> >
> > can you make the type to be Integer? So it is consistent with the id 
> > type ion LineageEdge "private List sources;"
> 
> Xinran Tinney wrote:
> Thre are 3 elements in LieageVetext 
> private String id;
> private String vertexType;
> private String vertexId;
> 
> The one in private List sources is using the first one "id", I 
> can not make vertexId an Integer because it is not a number. e.g. 
> "vertexId":"db_1.view_1.count"
> 
> Xinran Tinney wrote:
> Do you mean the change "id" to Integer?

sorry. I meant "id" should be Integer. vertexId should be String


- Na


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


On April 18, 2019, 8:33 p.m., Xinran Tinney wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70505/
> ---
> 
> (Updated April 18, 2019, 8:33 p.m.)
> 
> 
> Review request for atlas and Na Li.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> the code is implemented in Java.
> 
> 1) It takes Impala file location and file name prefix as input. 
> 2) It reads its own record-keeping file to get the offset of the Impala file 
> it has already read. Then read the new records from Impala file, update the 
> record-keeping file to append the new offset of the Impala file.
> 3) It parses the new records from Impala file into internal data structure as 
> output.
> 4) If the Impala file name has changed, start a new file for record-keeping 
> and remove the old record-keeping file.
> 5) Implemented unit test to verify the behavior.
> 
> 
> Diffs
> -
> 
>   addons/impala-bridge/impala1.txt PRE-CREATION 
>   addons/impala-bridge/impala2.txt PRE-CREATION 
>   addons/impala-bridge/pom.xml PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/ImpalaBridge.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageEdge.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageQuery.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageVertex.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/bridge/TestImpalaBridge.java
>  PRE-CREATION 
>   pom.xml 76341388b 
> 
> 
> Diff: https://reviews.apache.org/r/70505/diff/1/
> 
> 
> Testing
> ---
> 
> unit testing and mvn clean install -DskipTests
> 
> 
> Thanks,
> 
> Xinran Tinney
> 
>

Re: Review Request 70505: CDPD-252:parse metadata/Lineage files generated by Impala

[Na Li via Review Board]

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




addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageQuery.java
Lines 31 (patched)


Your code does not work for this lineage record. That is why it is critical 
to finish "Collect the lineage records for all operations that Impala generate 
lineage records" before you can claim you are done with this jira!

{  
   "1554132988258":{  
  "query_id":"544e8c5ab3b6a634:650a9d9e",
  "session_id":"044dbeb34e24aa5d:ad43167db6878180",
  "start_time":"2019-04-01 08:36:27.842860",
  "authorization_failure":false,
  "status":"",
  "user":"imp...@gce.cloudera.com",
  "impersonator":null,
  "statement_type":"CREATE_TABLE",
  "network_address":":::172.31.114.111:41200",
  "sql_statement":"CREATE EXTERNAL TABLE IF NOT EXISTS 
db_atlqkltata.tbl_atlqkltata_1(col_tbl_atlqkltata_1_id 
INT,col_tbl_atlqkltata_1_name STRING,col_tbl_atlqkltata_1_street 
STRING,col_tbl_atlqkltata_1_city STRING,col_tbl_atlqkltata_1_state 
STRING,col_tbl_atlqkltata_1_zipcode INT)",
  "catalog_objects":[  
 {  
"name":"db_atlqkltata.tbl_atlqkltata_1",
"object_type":"TABLE",
"privilege":"CREATE"
 }
  ]
   }
}


- Na Li


On April 19, 2019, 3:51 p.m., Xinran Tinney wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70505/
> ---
> 
> (Updated April 19, 2019, 3:51 p.m.)
> 
> 
> Review request for atlas and Na Li.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> the code is implemented in Java.
> 
> 1) It takes Impala file location and file name prefix as input. 
> 2) It reads its own record-keeping file to get the offset of the Impala file 
> it has already read. Then read the new records from Impala file, update the 
> record-keeping file to append the new offset of the Impala file.
> 3) It parses the new records from Impala file into internal data structure as 
> output.
> 4) If the Impala file name has changed, start a new file for record-keeping 
> and remove the old record-keeping file.
> 5) Implemented unit test to verify the behavior.
> 
> 
> Diffs
> -
> 
>   addons/impala-bridge/impala1.txt PRE-CREATION 
>   addons/impala-bridge/impala2.txt PRE-CREATION 
>   addons/impala-bridge/pom.xml PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/ImpalaBridge.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageEdge.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageQuery.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/bridge/LineageVertex.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/bridge/TestImpalaBridge.java
>  PRE-CREATION 
>   pom.xml 76341388b 
> 
> 
> Diff: https://reviews.apache.org/r/70505/diff/2/
> 
> 
> Testing
> ---
> 
> unit testing and mvn clean install -DskipTests
> 
> 
> Thanks,
> 
> Xinran Tinney
> 
>

[jira] [Updated] (ATLAS-3110) Add a bulk api to get entities by unique attributes

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3110:
--
Fix Version/s: trunk
   2.0.0

> Add a bulk api to get entities by unique attributes
> ---
>
> Key: ATLAS-3110
> URL: https://issues.apache.org/jira/browse/ATLAS-3110
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Ayush Nigam
>Assignee: Ayush Nigam
>Priority: Minor
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3110(1).patch
>
>
> Add a bulk api to get entities by unique attributes,currently there is bulk 
> api for guids only



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

[jira] [Updated] (ATLAS-3090) PC Framework: Improve Existing Producer Consumer Framework

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3090:
--
Fix Version/s: 2.0.0

> PC Framework: Improve Existing Producer Consumer Framework
> --
>
> Key: ATLAS-3090
> URL: https://issues.apache.org/jira/browse/ATLAS-3090
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3090-Improvements-to-PC-framework.patch
>
>
> *Background*
> Existing producer-consumer (PC) framework lacks:
>  * Restarting tasks.
>  * Results accumulation.
>  * Waiting for all tasks to complete.
> *Solution Guidance*
> Additional methods to include:
>  * _drain_: Complete execution of existing tasks.
>  * _submit_: Resubmit tasks.
>  * _checkAndSubmit_: Check if tasks are available before submissions.
>  * _getResults_: Get accumulated results.



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

[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:
--
Fix Version/s: trunk

> Update component versions of Atlas to use Hadoop3, HBase2 and Solr7
> ---
>
> 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, trunk
>
> Attachments: 
> 0001-ATLAS-2987-Update-component-versions-of-Atlas-to-use.patch
>
>
> Update Component version of Atlas to the following:
>  * Hadoop 3.1.1
>  * Hive 3.1.0
>  * HBase 2.0.2
>  * Solr 7.5.0
>  * Kafka 2.0.0
>  * Zookeeper 3.4.6



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

[jira] [Updated] (ATLAS-3057) Index Repair Tool: Add JanusGraph-Specific Index Repair Tool

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3057:
--
Fix Version/s: trunk

> Index Repair Tool: Add JanusGraph-Specific Index Repair Tool
> 
>
> Key: ATLAS-3057
> URL: https://issues.apache.org/jira/browse/ATLAS-3057
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Ashutosh Mestry
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3057-Atlas-Index-Repair-tool-for-JanusGraph.patch, 
> ATLAS-3057-Atlas-Index-Repair-tool-for-JanusGraph.patch
>
>
> *Background*
> For Atlas version that uses _HBase_ and _Solr_, occasionally if Solr is down 
> and entities get created, then there is no record of the created entities 
> within Solr. Basic search does not indicate presence of such entities.
> *Solution*
> Index Repair Tool (which was present in branch-0.8) should be implemented for 
> JanusGraph.
> *Implementation Guidance*
>  * Create Java-based implementation rather than Groovy script that needs 
> graphdb-specific shell to be installed. 
>  * Use JanusGraph APIs for restore instead of custom per-vertex logic.
>  * Investigate possibility of using MapReduce for higher throughput.



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

[jira] [Updated] (ATLAS-3026) Column level lineage show the invalid icon for the process

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3026:
--
Fix Version/s: 2.0.0
   1.2.0

> Column level lineage show the invalid icon for the process
> --
>
> Key: ATLAS-3026
> URL: https://issues.apache.org/jira/browse/ATLAS-3026
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3026.patch
>
>




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

[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3027:
--
Fix Version/s: 2.0.0
   1.2.0

> UI : Metric modal Improvements
> --
>
> Key: ATLAS-3027
> URL: https://issues.apache.org/jira/browse/ATLAS-3027
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3027.patch
>
>
> Following point need to improve
>  * Count column should be right-aligned
>  * Show 'Total Active Entities’ and ‘Total Deleted Entities'
>  * Increase the modal height



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

[jira] [Updated] (ATLAS-3020) ClientV2: DeleteClassifications Invokes Incorrect REST Call

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3020:
--
Fix Version/s: 2.0.0

> ClientV2: DeleteClassifications Invokes Incorrect REST Call
> ---
>
> Key: ATLAS-3020
> URL: https://issues.apache.org/jira/browse/ATLAS-3020
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.1.0, 0.8.4, 2.0.0, trunk
>
> Attachments: ATLAS-3020-Atlas-Client-Delete-Classifications-API.patch
>
>
> *Background*
> Existing _AtlasClientV2.deleteClassifications_ invokes incorrect REST API. 
> *Solution*
> The method should invoke the correct REST API.



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

[jira] [Updated] (ATLAS-3029) API: Retrieve Classification Events from Audits

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3029:
--
Fix Version/s: 1.2.0

> API: Retrieve Classification Events from Audits
> ---
>
> Key: ATLAS-3029
> URL: https://issues.apache.org/jira/browse/ATLAS-3029
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-intg
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-3020-Audit-APIs-for-classification-updates-master.patch
>
>
> *Use Cases*
> 1. In the case where user looses data within Atlas, they can get it ingested 
> by using tool like _import-hive_. With this approach, the user does not get 
> the classifications and the entities associated with them.
> 2. In case where classifications were inadvertently removed from entities.
> *Solution*
> In the scenarios above, currently there isn't a way to know the 
> classification operations performed.
> A REST API that would get this information from Atlas' Audit tables would 
> benefit the user.
> *Approach Guidance*
>  * REST endpoint: Use Atlas' Audit Repository to fetch the audit events. This 
> API should accept a timestamp range so that useful audit events can be 
> fetched.
>  * REST endpoint: Re-play the audit events to update Atlas.



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

[jira] [Updated] (ATLAS-2927) Update lineage query for Process entities

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2927:
--
Fix Version/s: 2.0.0

> Update lineage query for Process entities
> -
>
> Key: ATLAS-2927
> URL: https://issues.apache.org/jira/browse/ATLAS-2927
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: 
> 0001-ATLAS-2927-Update-lineage-query-for-Process-entities-branch-0.8.patch
>
>
> Currently lineage query for process entities generates lineage based on the 
> number of hops on process entities. Lineage should be generated based on the 
> hops on DataSet entities.



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

[jira] [Updated] (ATLAS-2900) Regression: Export Connected Generates Incorrect Content

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2900:
--
Fix Version/s: 2.0.0

> Regression: Export Connected Generates Incorrect Content
> 
>
> Key: ATLAS-2900
> URL: https://issues.apache.org/jira/browse/ATLAS-2900
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 0.8.3, trunk
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.0.0, 0.8.3, 2.0.0, trunk
>
> Attachments: 
> ATLAS-2900-Export-connected-addressed-case-where-imp.patch, uPqvN.zip
>
>
> *Steps to Duplicate*
> Using Beeline, create the following entities in Hive.
> {code:java}
> create database stocks; 
> use stocks; 
> create table daily (dt string, open string, high string, low string, close 
> string, volume string, adj_close string); 
> create view daily_rpt as select * from daily;
> {code}
> Perform export with following options:
> {code:java}
> { 
> "itemsToExport": [ { "typeName": "hive_table", "uniqueAttributes": { 
> "qualifiedName": "stocks.daily@cl1" } } ], 
> "options": { "fetchType": "connected" } 
> }
> {code}
> Expected result: Exported output should be 'import' able in another Atlas 
> instance where the database with same guid is already present.
> Actual result: 
> On Importing the attached zip file , request fails with
> {code:java}
> 2018-09-26 23:02:50,705 INFO  - [pool-2-thread-18 - 
> 84ea8d84-ead8-428d-a4db-4451812dd241:] ~ ==> import(user=admin, 
> from=10.22.16.153, request=AtlasImportRequest{options={}}) (ImportService:89)
> 2018-09-26 23:02:50,864 INFO  - [pool-2-thread-18 - 
> 84ea8d84-ead8-428d-a4db-4451812dd241:] ~ bulkImport(): progress: 14% (of 7) - 
> entity:last-imported:hive_table:[1]:(d7773c32-ce56-4d8a-96c1-5a4aa97e982e) 
> (AtlasEntityStoreV1:146)
> 2018-09-26 23:02:50,865 ERROR - [pool-2-thread-18 - 
> 84ea8d84-ead8-428d-a4db-4451812dd241:] ~ getNextEntityWithExtInfo 
> (ZipSource:213)
> org.apache.atlas.exception.AtlasBaseException: Error converting file to JSON.
>   at 
> org.apache.atlas.repository.impexp.ZipSource.convertFromJson(ZipSource.java:177)
>   at 
> org.apache.atlas.repository.impexp.ZipSource.getEntityWithExtInfo(ZipSource.java:139)
>   at 
> org.apache.atlas.repository.impexp.ZipSource.getNextEntityWithExtInfo(ZipSource.java:211)
>   at 
> org.apache.atlas.repository.store.graph.v1.BulkImporterImpl$EntityImportStreamWithResidualList.getNextEntityWithExtInfo(BulkImporterImpl.java:183)
>   at 
> org.apache.atlas.repository.store.graph.v1.BulkImporterImpl.bulkImport(BulkImporterImpl.java:72)
>   at 
> org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:213)
>   at 
> org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:100)
>   at 
> org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:390)
>   at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> 

[jira] [Updated] (ATLAS-2520) Use JanusGraph traversal over gremlin script

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2520:
--
Fix Version/s: 2.0.0

> Use JanusGraph traversal over gremlin script 
> -
>
> Key: ATLAS-2520
> URL: https://issues.apache.org/jira/browse/ATLAS-2520
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: 
> 0001-ATLAS-2520-Introduce-JanusGraphTraversal-to-deprecat.patch, Screen Shot 
> 2018-06-05 at 6.16.42 PM.png, Screen Shot 2018-06-05 at 6.19.33 PM.png
>
>
> Currently lot of code in Atlas follow a concept of GremlinQueryProvider which 
> gives TP2 and TP3 queries depending on the graph backend being used. Since 
> Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to 
> remove TP2 related queries/abstractions and use the GraphTraversal Java API 
> provided by JanusGraph.
>  
> PRO: Lot of unused code can be removed, more expressive Graph 
> querying/traversal.
> CONS: Decommissioning TP2 completely is a major engineering effort



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

[jira] [Updated] (ATLAS-2942) Audit tab changes to display proper data on detail modal view

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2942:
--
Fix Version/s: 2.0.0

> Audit tab changes to display proper data on detail modal view
> -
>
> Key: ATLAS-2942
> URL: https://issues.apache.org/jira/browse/ATLAS-2942
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8.2
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2942_Master.patch, ATLAS-2942_branch_0.8.patch
>
>




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

[jira] [Updated] (ATLAS-2943) Export: Operation Fails if No Options are Specified

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2943:
--
Fix Version/s: 2.0.0
   1.2.0

> Export: Operation Fails if No Options are Specified
> ---
>
> Key: ATLAS-2943
> URL: https://issues.apache.org/jira/browse/ATLAS-2943
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, 0.8.3, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0, trunk
>
> Attachments: ATLAS-2943-Export-options-null-check-added.patch
>
>
> *Pre-requisites*
>  * Create database (say stocks), tables from beeline. 
> *Steps to Duplicate*
> Attempt an export using these parameters:
> {code:java}
> { "itemsToExport": [ { "typeName": "hive_db", "uniqueAttributes": { 
> "qualifiedName": "stocks@cl1" }} ] }
> {code}
> *Expected results*: Export should succeed with default options.
> *Actual results:* Export fails with the following exception:
> {code:java}
> 2018-10-28 16:03:54,311 ERROR - [pool-2-thread-9 - 
> e63a2ebe-2480-4a60-b5f8-12595effdd9d:hrt_qa:POST/api/atlas/admin/export] ~ 
> Operation failed:  (ExportService:116)
> java.lang.NullPointerException
>   at 
> org.apache.atlas.repository.impexp.AuditsWriter.isReplicationOptionSet(AuditsWriter.java:74)
>   at 
> org.apache.atlas.repository.impexp.AuditsWriter.access$200(AuditsWriter.java:44)
>   at 
> org.apache.atlas.repository.impexp.AuditsWriter$ExportAudits.add(AuditsWriter.java:150)
>   
> {code}



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

[jira] [Updated] (ATLAS-2934) Utility to detect incorrect entity state

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2934:
--
Fix Version/s: 1.2.0

> Utility to detect incorrect entity state
> 
>
> Key: ATLAS-2934
> URL: https://issues.apache.org/jira/browse/ATLAS-2934
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2934.patch
>
>
> Data of an Atlas entity data is stored in one or more graph vertices, 
> connected by edges. In addition to vertices for each entity classification, 
> Atlas has classification-names cached in a entity vertex property as well - 
> for use in entity-searches. An utility to detect and repair any 
> inconsistencies of this cached data will be handy in troubleshooting and 
> fixing issues.



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

[jira] [Updated] (ATLAS-3112) Allow Indexing of array attributes (LIST or SET) in indexing store

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3112:
--
Fix Version/s: (was: 2.0.0)

> Allow Indexing of array attributes (LIST or SET) in indexing store
> --
>
> Key: ATLAS-3112
> URL: https://issues.apache.org/jira/browse/ATLAS-3112
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>
> Array attributes with cardinality LIST or SET is not indexed in the indexing 
> store. To allow index query to search on array attributes, array attributes 
> needs to be indexed.



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

[jira] [Resolved] (ATLAS-3112) Allow Indexing of array attributes (LIST or SET) in indexing store

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian resolved ATLAS-3112.
---
Resolution: Invalid

> Allow Indexing of array attributes (LIST or SET) in indexing store
> --
>
> Key: ATLAS-3112
> URL: https://issues.apache.org/jira/browse/ATLAS-3112
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>
> Array attributes with cardinality LIST or SET is not indexed in the indexing 
> store. To allow index query to search on array attributes, array attributes 
> needs to be indexed.



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

[jira] [Updated] (ATLAS-3046) Classification Updater: Types Not Derived from Referenceable are Not Handled

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3046:
--
Fix Version/s: trunk
   2.0.0

> Classification Updater: Types Not Derived from Referenceable are Not Handled
> 
>
> Key: ATLAS-3046
> URL: https://issues.apache.org/jira/browse/ATLAS-3046
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.1.0, 2.0.0, trunk
>
> Attachments: ATLAS-3046-Classification-Updater-Unique-name-fix.patch, 
> ATLAS-3046-Part-3.-Updated-case-for-handling-deleted.patch
>
>
> *Background*
> The classification updater tool released to help users re-tag entities that 
> were present in an Atlas instance does not handle types that are not derived 
> from _Referencable_.
> *Steps to Duplicate*
>  * Create a type that that is not derived from the _Referencable._
>  * Execute the _prepare_ step_._ 
> Expected Results: Prepare completes successfully.
> Actual Results: Following error is displayed:
> ```
> Processing: db_1000_1@cl1
>  Processed: 13
>  Error writing: java.lang.NullPointerException
>  Done!
> ```



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

[jira] [Updated] (ATLAS-3061) UI: Search Term is not working

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3061:
--
Fix Version/s: trunk
   2.0.0

> UI: Search Term is not working
> --
>
> Key: ATLAS-3061
> URL: https://issues.apache.org/jira/browse/ATLAS-3061
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3061.patch
>
>




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

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

[Sarath Subramanian (JIRA)]

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

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

> 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
>Assignee: Umesh Padashetty
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> 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)

[jira] [Updated] (ATLAS-2970) UI: Show counts besides the Type and Classification dropdown list in search

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2970:
--
Fix Version/s: 1.2.0

> UI: Show counts besides the Type and Classification dropdown list in search
> ---
>
> Key: ATLAS-2970
> URL: https://issues.apache.org/jira/browse/ATLAS-2970
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2970.patch, ATLAS-2970_1.patch
>
>




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

[jira] [Updated] (ATLAS-2968) Update model files to include service-type for each entityDef

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2968:
--
Fix Version/s: 2.0.0
   1.2.0

> Update model files to include service-type for each entityDef
> -
>
> Key: ATLAS-2968
> URL: https://issues.apache.org/jira/browse/ATLAS-2968
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Kapildeo Nayak
>Assignee: Kapildeo Nayak
>Priority: Major
> Fix For: 1.2.0, 2.0.0, trunk
>
> Attachments: 
> 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch
>
>
> Adding the service-type value to each typedef’s options param.



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

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

[Sarath Subramanian (JIRA)]

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

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

> 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
>
> Attachments: ATLAS-2951_branch-0.8.patch, 
> New_Lineage_detailpage_layout.png, New_way_to_select_filter.png, 
> Old_Lineage_detailpage_layout.png, depth_change.png, hide_process_view.png, 
> old_default_view.png, show_process_view.png
>
>




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

[jira] [Updated] (ATLAS-2892) TypeREST: Provide REST Endpoint that Deletes Type Given Type Name

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2892:
--
Fix Version/s: 2.0.0

> TypeREST: Provide REST Endpoint that Deletes Type Given Type Name
> -
>
> Key: ATLAS-2892
> URL: https://issues.apache.org/jira/browse/ATLAS-2892
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8.2, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.2, 2.0.0, trunk
>
> Attachments: 
> ATLAS-2892-Additional-TypesREST-endpoint-for-deletin.patch, 
> ATLAS-2892-deleteTagMaster.patch
>
>
> *Background*
> Existing Type REST API for deleting type takes _AtlasTypesDef_ as parameter. 
> This is useful for bulk delete. For single type delete it will be helpful to 
> have a REST endpoint that performs type delete by taking name of the time.
> *Approach Guideline*
>  * Update _TypesREST_.
>  * Add new method.
>  * Continue to use _typesdefStore.deleteTypesDef_



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

[jira] [Updated] (ATLAS-2909) Export Process: ChangeMarker Remains Stuck at a Point

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2909:
--
Fix Version/s: 2.0.0

> Export Process: ChangeMarker Remains Stuck at a Point
> -
>
> Key: ATLAS-2909
> URL: https://issues.apache.org/jira/browse/ATLAS-2909
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.2, 0.8.3, 2.0.0
>
> Attachments: 
> ATLAS-2909-ChangeMarker-updated-during-initializatio.patch
>
>
> *Pre-requisites*
>  - Fresh installation of a build. This can be done by truncating atlas_titan 
> and ATLAS_ENTITY_AUDIT_EVENTS tables.
>  - Create some entities within Atlas either by 'Create New Entity' UI option 
> or via Beeline/Hive.
> *Steps to Duplicate*
>  * Perform export few times (more than 1) of the created entities using the 
> following options and commands.
>  * Observe the server logs (_application.log)_
> _export-options.json_
> {code:java}
> {
> "itemsToExport": [
> { "typeName": "hdfs_path", "uniqueAttributes": { "path": 
> "/warehouse/hr/" }}
> ],
> "options": {
> "fetchType": "incremental",
> "matchType": "startsWith",
> "skipLineage": true,
> "replicatedTo": "clMain2"
> }
> }
> {code}
> CURL
> {code:java}
> curl -X POST -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache" -d @../docs/export-options-skip-lineage.json 
> http://localhost:21000/api/atlas/admin/export > ../docs/hr-1.zip
> {code}
>  
> *Expected Results*
> Each export operation will display _changeMarker_ with new value.
> *Observed Results*
> Each export operation displays the same _changeMarker_ value.
> *Variation*
> Restart Atlas. Perform few exports. The value of _changeMarker_ now changes 
> for each export.



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

[jira] [Updated] (ATLAS-2906) Import Process: Transforms: Handling Custom Attributes Does Not Update

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2906:
--
Fix Version/s: 2.0.0
   1.2.0

> Import Process: Transforms: Handling Custom Attributes Does Not Update
> --
>
> Key: ATLAS-2906
> URL: https://issues.apache.org/jira/browse/ATLAS-2906
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-2906-Allow-transforms-to-be-applied-when-entit.patch
>
>
> *Background*
> The new transform framework looks at the entity holistically and computes 
> attributes as it sees fit.
> Updating the _hive_storagedesc.location_ if entity-level transform is 
> present, does not apply the transform.
> *Steps* *to Duplicate*
>  * Attempt to import a zip file with the following transform.
> {code:java}
> { "options": { "transformers": "[{\"conditions\":{\"__entity\":\"topLevel: 
> \"},\"action\":{\"__entity\":\"ADD_CLASSIFICATION: 
> mycluster0_replicated\"}},{\"action\":{\"__entity.replicatedTo\":\"CLEAR:\",\"__entity.replicatedFrom\":\"CLEAR:\"}},{\"conditions\":{\"hive_db.clusterName\":\"EQUALS:
>  mycluster0\"},\"action\":{\"hive_db.clusterName\":\"SET: 
> mycluster1\"}},{\"conditions\":{\"hive_storagedesc.location\":\"STARTS_WITH_IGNORE_CASE:
>  
> hdfs://localhost.localdomain\"},\"action\":{\"hive_storagedesc.location\":\"REPLACE_PREFIX:
>  = :hdfs://localhost.localdomain=hdfs://mycluster1\"}}]", "replicatedFrom": 
> "SFO$clx" } }
> {code}
> Locate any entity of type _hive_storagedesc_ and note the _location._ It does 
> not apply the updated location.
> *Root Cause*
>  * The new transform framework re-computes the location based on cached data.
>  * Solution: Prevent caching of this attribute so that it honors the 
> externally set transformation.



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

[jira] [Updated] (ATLAS-2909) Export Process: ChangeMarker Remains Stuck at a Point

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2909:
--
Fix Version/s: 1.2.0

> Export Process: ChangeMarker Remains Stuck at a Point
> -
>
> Key: ATLAS-2909
> URL: https://issues.apache.org/jira/browse/ATLAS-2909
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.2, 0.8.3, 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-2909-ChangeMarker-updated-during-initializatio.patch
>
>
> *Pre-requisites*
>  - Fresh installation of a build. This can be done by truncating atlas_titan 
> and ATLAS_ENTITY_AUDIT_EVENTS tables.
>  - Create some entities within Atlas either by 'Create New Entity' UI option 
> or via Beeline/Hive.
> *Steps to Duplicate*
>  * Perform export few times (more than 1) of the created entities using the 
> following options and commands.
>  * Observe the server logs (_application.log)_
> _export-options.json_
> {code:java}
> {
> "itemsToExport": [
> { "typeName": "hdfs_path", "uniqueAttributes": { "path": 
> "/warehouse/hr/" }}
> ],
> "options": {
> "fetchType": "incremental",
> "matchType": "startsWith",
> "skipLineage": true,
> "replicatedTo": "clMain2"
> }
> }
> {code}
> CURL
> {code:java}
> curl -X POST -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache" -d @../docs/export-options-skip-lineage.json 
> http://localhost:21000/api/atlas/admin/export > ../docs/hr-1.zip
> {code}
>  
> *Expected Results*
> Each export operation will display _changeMarker_ with new value.
> *Observed Results*
> Each export operation displays the same _changeMarker_ value.
> *Variation*
> Restart Atlas. Perform few exports. The value of _changeMarker_ now changes 
> for each export.



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

[jira] [Updated] (ATLAS-2888) Export & Import Process: Change Marker Removed Inadvertently

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2888:
--
Fix Version/s: 2.0.0
   1.2.0

> Export & Import Process: Change Marker Removed Inadvertently
> 
>
> Key: ATLAS-2888
> URL: https://issues.apache.org/jira/browse/ATLAS-2888
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2888-Change-marker-fix-for-server-name.2.patch, 
> ATLAS-2888-REPL_DETAILS-entry-missing.patch
>
>
> *Background*
> When using _replicatedTo_ and _replicatedFrom_ options in _Export_ and 
> _Import_ requests, the _AtlasServer_ stores a marker indicating the next 
> starting point for export to being.
> *Steps to Duplicate*
>  * Setup _export-options.json_ as follows:
> {{_{_}}{{_"itemsToExport": [_}}{{_{ "typeName": "hive_db", 
> "uniqueAttributes": \{ "qualifiedName": "stocks@cl1" 
> }}_}}{{_],_}}{{_"options": {_}}{{_"fetchType": 
> "incremental",_}}{{_"skipLineage": true,_}}{{_"changeMarker": 
> 0,_}}{{_"replicatedTo": "SFO$clMain"_}}{{_}_}}{{_}_}} * Perform export using 
> Export REST calls.
>  * Update _export-options.json_ with the _changeMarker_ from the _Atlas' 
> application.log._
>  * Notice the _AtlasServer_ entry for _clMain_. It is updated with 
> _changeMarker_ value from log.
>  * Perform export using Export REST API.
>  * Export will happen with no entities exported (since nothing was changed in 
> the database). Atlas' application.log indicates new change maker.
> _Expected results:_ _AtlasServer_ for _clMain_ should continue displaying 
> _REPL_DETAILS_ entry.
> _Observed results:_ _AtlasServer_ _for_ _clMain_ displays properties with 
> _REPL_DETAILS_ entry removed. 
> *Root Cause*
> Within _AuditsWriter_, the entry for _clMain_ is saved 2 times. First without 
> the change marker and then if export operation has entities exported, the 
> server entity is saved with the change marker.
> If no entities, exist the server entry remains without the _REPL_DETAILS_ 
> entry present.
> *Possible Fix*
> Save the target server entry only once.



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

[jira] [Updated] (ATLAS-2897) Import Process: Handle Import of Empty Zip Elegantly

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2897:
--
Fix Version/s: 2.0.0
   1.2.0

> Import Process: Handle Import of Empty Zip Elegantly
> 
>
> Key: ATLAS-2897
> URL: https://issues.apache.org/jira/browse/ATLAS-2897
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2897-Better-handling-of-empty-zip-files.3.patch, 
> ATLAS-2897-Elegant-handling-of-empty-zip-files.patch
>
>
> *Background*
> Existing implementation of _ZipSource_ always assumes that the zip that is 
> being passed has valid data. It starts serializing the data and that is where 
> it encounters serialization error. This case can be handled in a more elegant 
> way.
> *Approach Guidance*
>  * In _ZipSource_ ctor, detect case for empty file, throw error message 
> accordingly.
>  * Handle the case where requested _ZipEntry_ is not found.



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

[jira] [Updated] (ATLAS-2905) Generate lineage information for process entities

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2905:
--
Fix Version/s: 2.0.0

> Generate lineage information for process entities
> -
>
> Key: ATLAS-2905
> URL: https://issues.apache.org/jira/browse/ATLAS-2905
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: 
> 0001-ATLAS-2905-Generate-lineage-information-for-process.1-branch-0.8.patch, 
> 0001-ATLAS-2905-Generate-lineage-information-for-process.1.patch
>
>
> Currently lineage information is generated only for DataSet entities and its 
> derivatives. Lineage information should also be generated for Process 
> entities and in UI lineage tab should be enabled for any process entities and 
> lineage rendered.



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

[jira] [Updated] (ATLAS-1950) Import Transform option using supertype instead of a specific type

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-1950:
--
Fix Version/s: 2.0.0
   1.2.0

> Import Transform option using supertype instead of a specific type
> --
>
> Key: ATLAS-1950
> URL: https://issues.apache.org/jira/browse/ATLAS-1950
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-1950.patch
>
>
> Users can provide a tranforms option while import to replace @cl1 in 
> hive_table to @cl2 using the following JSON.
> {code}
> {
> "options": {
> "transforms": "{ \"hive_table\": { \"qualifiedName\": [ 
> \"replace:@cl1:@cl2\" ] } }"
> }
> }
> {code}
> It would be easy to specify a super type like 'Asset' to transform all types 
> in the export items which inherit from the super type to have "@cl1" replaced 
> with "@cl2" like
> {code}
> {
> "options": {
> "transforms": "{ \"Asset\": { \"qualifiedName\": [ 
> \"replace:@cl1:@cl2\" ] } }"
> }
> }
> {code}



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

[jira] [Updated] (ATLAS-2907) UI: Generate lineage information for process entities

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2907:
--
Fix Version/s: 2.0.0

> UI: Generate lineage information for process entities
> -
>
> Key: ATLAS-2907
> URL: https://issues.apache.org/jira/browse/ATLAS-2907
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
> Attachments: ATLAS-2907.patch
>
>




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

[jira] [Updated] (ATLAS-2797) Atlas Cluster Entity

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2797:
--
Fix Version/s: 2.0.0
   1.2.0

> Atlas Cluster Entity
> 
>
> Key: ATLAS-2797
> URL: https://issues.apache.org/jira/browse/ATLAS-2797
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2797-Atlas-Cluster.patch
>
>
> Background
>  
> In cases where Atlas data is synchronized to other Atlas clusters, it is 
> necessary to store some information about the nature of operation.
>  
> REST APIs to access this entity should be available as these can be used to 
> fetch data about the cluster entity.
>  
> Use cases:
>  * Scenario: Data generated by Export operation on one cluster (say cl1) can 
> be used to Import into another cluster (say cl2). This operation will result 
> in data such at AtlasImportResult that can be used later for performing 
> subsequent operations or for audits. The AtlasCluster entity will be a good 
> home for this data. REST APIs on AtlasCluster can be used for retrieveing 
> this data.
>  
> Approach guidance:
>  * Create AtlasCluster entity.
>  * Create ClusterService that will use the OGM framework within Atlas to aid 
> with save and load operations



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

[jira] [Assigned] (ATLAS-3152) Create Bulk Delete Api on Unique Attributes

[Ayush Nigam (JIRA)]

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

Ayush Nigam reassigned ATLAS-3152:
--

Assignee: Ayush Nigam

> Create Bulk Delete Api on Unique Attributes
> ---
>
> Key: ATLAS-3152
> URL: https://issues.apache.org/jira/browse/ATLAS-3152
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Ayush Nigam
>Assignee: Ayush Nigam
>Priority: Major
>




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

[jira] [Updated] (ATLAS-3077) Handle java patches in patch framework

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3077:
--
Fix Version/s: trunk
   2.0.0

> Handle java patches in patch framework 
> ---
>
> Key: ATLAS-3077
> URL: https://issues.apache.org/jira/browse/ATLAS-3077
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk
>
>
> We have Atlas typedef patches available to update out of box type 
> definitions. This JIRA will introduce a new java patch framework to handle 
> changes to the graph database not specific to type changes.
> For e.g. In case of migration, to add/update property keys in vertices - java 
> patch framework can be used, which will be run at the atlas startup time 
> during bootstrap.



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

[jira] [Updated] (ATLAS-3075) Add tag propagation details in relationship notification message

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3075:
--
Fix Version/s: trunk

> Add tag propagation details in relationship notification message
> 
>
> Key: ATLAS-3075
> URL: https://issues.apache.org/jira/browse/ATLAS-3075
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: 
> ATLAS-3075-Add-tag-propagation-details-in-relationsh.patch
>
>
> Current relationship notifications does not contain "propagateTags" detail.
> Add tag propagation details in notification message.



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

[jira] [Updated] (ATLAS-3089) Refactor: Move Producer Consumer Framework to intg Project for Use Across Modules

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3089:
--
Fix Version/s: 2.0.0

> Refactor: Move Producer Consumer Framework to intg Project for Use Across 
> Modules
> -
>
> Key: ATLAS-3089
> URL: https://issues.apache.org/jira/browse/ATLAS-3089
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
>
> *Background*
> The producer-consumer framework that is used in migration import resides in 
> graphdb/janus module.
> Any module other module that considers using it will have to take on 
> additional dependency that will break existing abstractions.
> *Solution*
> The framework is isolated enough to be made part of the _intg_ module.



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

[jira] [Updated] (ATLAS-2814) Export & Import Process: Add Data to AtlasCluster About Last Successful Import

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2814:
--
Fix Version/s: 2.0.0
   1.2.0

> Export & Import Process: Add Data to AtlasCluster About Last Successful Import
> --
>
> Key: ATLAS-2814
> URL: https://issues.apache.org/jira/browse/ATLAS-2814
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2814-Cluster-stores-replication-details.patch
>
>
> *Background*
> Scenario: Couple of Atlas clusters are setup such that incremental export and 
> import is setup via some custom program. Example, Cluster _cl1_ exports does 
> incremental export and the output is imported into cluster _cl2_.
> It may be worth while to maintain some information about the last successful 
> import. This way the next incremental export will have correct parameters for 
> its export.
> *Approach Guidance*
>  * Create a new model, say _AtlasSyncInfo_, that stores information about top 
> level entity used for export and the timestamp that should be used for 
> subsequent incremental export.
>  * Utilize _AtlasCluster_'s _additionalInfo_ fields to store serialized 
> version of _AtlasSyncInfo_.
>  * Provide REST APIs for retrieval of this information.



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

[jira] [Updated] (ATLAS-2918) Update JanusGraph version to 0.3.1

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2918:
--
Fix Version/s: 2.0.0
   1.2.0

> Update JanusGraph version to 0.3.1
> --
>
> Key: ATLAS-2918
> URL: https://issues.apache.org/jira/browse/ATLAS-2918
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0, 1.2.0, 2.0.0
>
> Attachments: 0001-Update-JanusGraph-version-to-0.3.1-master-01.patch
>
>
> Janusgraph community has released their latest version:
> [https://github.com/JanusGraph/janusgraph/releases/tag/v0.3.1]
> This JIRA will update janus version to 0.3.1 in atlas source.
>  



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

[jira] [Updated] (ATLAS-2920) Update JanusGraph Solr clients to use all zookeeper entries

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2920:
--
Fix Version/s: 2.0.0

> Update JanusGraph Solr clients to use all zookeeper entries
> ---
>
> Key: ATLAS-2920
> URL: https://issues.apache.org/jira/browse/ATLAS-2920
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
>
> Update JanusGraph Solr clients to use all zookeeper entries



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

[jira] [Created] (ATLAS-3152) Create Bulk Delete Api on Unique Attributes

[Ayush Nigam (JIRA)]

Ayush Nigam created ATLAS-3152:
--

 Summary: Create Bulk Delete Api on Unique Attributes
 Key: ATLAS-3152
 URL: https://issues.apache.org/jira/browse/ATLAS-3152
 Project: Atlas
  Issue Type: Improvement
Reporter: Ayush Nigam






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

[jira] [Updated] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2827:
--
Fix Version/s: 2.0.0

> Unable to persist vertex when indexed string attribute is really long
> -
>
> Key: ATLAS-2827
> URL: https://issues.apache.org/jira/browse/ATLAS-2827
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8.1, 0.8.2, 1.0.0, trunk
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
>
> Titan/Janus  creates an inverted index key which exceeds the row length 
> restriction imposed by HBase hence the vertex fails to persist with backend 
> exception.
>  
> Solution:
> In the entity graph mapping, before persisting the  vertex we need to trim 
> down the value (although it'll cause data loss) to avoid Atlas becoming non 
> functional for such edge cases.



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

[jira] [Updated] (ATLAS-2890) Fix intermittent UT and IT failures for atlas in apache CI

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2890:
--
Fix Version/s: 2.0.0

> Fix intermittent UT and IT failures for atlas in apache CI
> --
>
> Key: ATLAS-2890
> URL: https://issues.apache.org/jira/browse/ATLAS-2890
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: 
> 0001-ATLAS-2890-Fix-intermittent-UT-and-IT-failures-for-a.patch
>
>
> We see intermittent test failures in 
> [https://builds.apache.org/view/A/view/Atlas/]
> This Jira addresses fixes for these intermittent failures in branch-0.8, 
> branch-1.0 and master



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

[jira] [Resolved] (ATLAS-3151) incorrect return type for AtlasClientV2.getRelationshipByGuid()

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3151.
-
   Resolution: Fixed
Fix Version/s: 2.0.0
   1.2.0

> incorrect return type for AtlasClientV2.getRelationshipByGuid()
> ---
>
> Key: ATLAS-3151
> URL: https://issues.apache.org/jira/browse/ATLAS-3151
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.1.0, 2.0.0
>Reporter: Madhan Neethiraj
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
>
> Reported by jxzhao via [https://github.com/apache/atlas/pull/42.]
> AtlasClientV2.getRelationshipByGuid() method returns AtlasRelationship; 
> however the REST API from Atlas server returns AtlasRelationshipWithExtInfo. 
> The client should be updated to match the server API.



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

[jira] [Updated] (ATLAS-3128) UI: Create entity is not working after new relationship attribute introduce

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3128:
--
Fix Version/s: trunk
   2.0.0

> UI: Create entity is not working after new relationship attribute introduce
> ---
>
> Key: ATLAS-3128
> URL: https://issues.apache.org/jira/browse/ATLAS-3128
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.2.0, 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3128-1.patch, ATLAS-3128-2.patch, ATLAS-3128.patch
>
>




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

[jira] [Updated] (ATLAS-3132) Data Patch Fx: Improve Data Patching Performance

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3132:
--
Fix Version/s: 2.0.0

> Data Patch Fx: Improve Data Patching Performance
> 
>
> Key: ATLAS-3132
> URL: https://issues.apache.org/jira/browse/ATLAS-3132
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
>
> *Background*
> The Java patch framework (now called data patching framework) introduced 
> recently performs patching at the rate of 1 million entities per 15 hrs. This 
> can be improved.
> *Proposed Solution*
>  * Use the Producer-Consumer framework to spawn multiple workers to perform 
> concurrent updates to entity vertices.
>  * Use _AtlasGraph_ in bulk loading mode to further gain performance.
>  * Perform duplicate data checks during processing.
> *Projected Performance Improvement*
>  * Based on various tests, these give increased throughput. New rate can be 
> ~300K entities per 5 mins.



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

[jira] [Resolved] (ATLAS-3132) Data Patch Fx: Improve Data Patching Performance

[Sarath Subramanian (JIRA)]

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

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

> Data Patch Fx: Improve Data Patching Performance
> 
>
> Key: ATLAS-3132
> URL: https://issues.apache.org/jira/browse/ATLAS-3132
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
>
> *Background*
> The Java patch framework (now called data patching framework) introduced 
> recently performs patching at the rate of 1 million entities per 15 hrs. This 
> can be improved.
> *Proposed Solution*
>  * Use the Producer-Consumer framework to spawn multiple workers to perform 
> concurrent updates to entity vertices.
>  * Use _AtlasGraph_ in bulk loading mode to further gain performance.
>  * Perform duplicate data checks during processing.
> *Projected Performance Improvement*
>  * Based on various tests, these give increased throughput. New rate can be 
> ~300K entities per 5 mins.



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

[jira] [Updated] (ATLAS-3143) PatchFx: Improve Memory Usage

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3143:
--
Fix Version/s: 2.0.0

> PatchFx: Improve Memory Usage
> -
>
> Key: ATLAS-3143
> URL: https://issues.apache.org/jira/browse/ATLAS-3143
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3143-PatchFx-Memory-usage-improvement.patch
>
>
> *Background*
> Existing implementation of _UniqueAttributePatch_ creates numerous short 
> lived objects. This causes memory to build up and puts load on GC.
> *Solution*
> Remove usage of short lived objects.



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

[jira] [Updated] (ATLAS-3031) UI : Allow user to export the lineage in PNG or JPEG format

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3031:
--
Fix Version/s: trunk
   2.0.0

> UI : Allow user to export the lineage in PNG or JPEG format
> ---
>
> Key: ATLAS-3031
> URL: https://issues.apache.org/jira/browse/ATLAS-3031
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3031.patch
>
>




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

[jira] [Updated] (ATLAS-3066) UI : Various table layout improvements

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3066:
--
Fix Version/s: trunk
   2.0.0

> UI : Various table layout improvements
> --
>
> Key: ATLAS-3066
> URL: https://issues.apache.org/jira/browse/ATLAS-3066
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3066.patch
>
>
> Following are the Improvements to be made:
> # When value for a particular key is not available rather than showing the 
> box, show *N/A* (for property table and Relationship table view).
> # Under the schema tab if data from *attribute* collection is not available 
> then fetch the data from *relationshipAttribute* collection.
> # Under the audit tab if there is no data then show the table which shows *No 
> Records Found *
> # For columns and parameters under the *Properties Tab* changing the limits 
> to prettify the display of JSON data.
> # Removing the boxes for display if the value has a single entry.



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

[jira] [Updated] (ATLAS-2979) Added service type dropdown to filter entitydef type.

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2979:
--
Fix Version/s: 1.2.0

> Added service type dropdown to filter entitydef type.
> -
>
> Key: ATLAS-2979
> URL: https://issues.apache.org/jira/browse/ATLAS-2979
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2979.patch, ATLAS-2979_1.patch, 
> ATLAS-2979_FINAL.patch, ATLAS-2979_FINAL.patch, 
> ATLAS-2979_UI_Improvement.patch, return-serviceType-in-api-header.patch
>
>




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

[jira] [Updated] (ATLAS-2919) Install ATLAS into Azure Virtual Machine

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2919:
--
Fix Version/s: 2.0.0
   1.2.0

> Install ATLAS into Azure Virtual Machine
> 
>
> Key: ATLAS-2919
> URL: https://issues.apache.org/jira/browse/ATLAS-2919
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mahender Shankesi
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: application.log
>
>
> I'm trying to install Atlas into my Azure Virtual Machine. I have followed 
> the steps from the below location.
> [https://atlas.apache.org/InstallationSteps.html]
> I'm able to start atlas_start but when I execute curl command I got the below 
> error
> $ curl -u admin:admin 
> [http://myip:21000/api/atlas/admin/version|http://10.41.64.19:21000/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21000: Connection refused
> $ curl -u admin:admin 
> [https://myip/api/atlas/admin/version|https://10.41.64.19:21443/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21443: Connection refused
> I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my ip. 
> None of them seems to be working.
>  
> $ netstat -a | grep 21000
> netstat -a | grep 21443
> Didn't return anything
>  
> Debug further and found that Cassandra is an issue. I reached out to dev team 
> and I got below response
> {color:#22}"This looks like an issue with the packaging, a wrong version 
> of netty is getting pulled in. ll try to find the source and update the 
> thread" {color}
>  
> {color:#22}I'm attaching the application log for this ticket. {color}
>  
> {color:#22}For better transparency and visibility I'm creating a Jira 
> ticket so that if anyone else has the same issue they can also look into 
> it.{color}
>  
>  
>  



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

[jira] [Resolved] (ATLAS-2919) Install ATLAS into Azure Virtual Machine

[Sarath Subramanian (JIRA)]

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

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

> Install ATLAS into Azure Virtual Machine
> 
>
> Key: ATLAS-2919
> URL: https://issues.apache.org/jira/browse/ATLAS-2919
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mahender Shankesi
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: application.log
>
>
> I'm trying to install Atlas into my Azure Virtual Machine. I have followed 
> the steps from the below location.
> [https://atlas.apache.org/InstallationSteps.html]
> I'm able to start atlas_start but when I execute curl command I got the below 
> error
> $ curl -u admin:admin 
> [http://myip:21000/api/atlas/admin/version|http://10.41.64.19:21000/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21000: Connection refused
> $ curl -u admin:admin 
> [https://myip/api/atlas/admin/version|https://10.41.64.19:21443/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21443: Connection refused
> I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my ip. 
> None of them seems to be working.
>  
> $ netstat -a | grep 21000
> netstat -a | grep 21443
> Didn't return anything
>  
> Debug further and found that Cassandra is an issue. I reached out to dev team 
> and I got below response
> {color:#22}"This looks like an issue with the packaging, a wrong version 
> of netty is getting pulled in. ll try to find the source and update the 
> thread" {color}
>  
> {color:#22}I'm attaching the application log for this ticket. {color}
>  
> {color:#22}For better transparency and visibility I'm creating a Jira 
> ticket so that if anyone else has the same issue they can also look into 
> it.{color}
>  
>  
>  



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

[jira] [Updated] (ATLAS-2922) REST API: Fetch Lineage with Schema Results in Error

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2922:
--
Fix Version/s: 2.0.0
   1.2.0

> REST API: Fetch Lineage with Schema Results in Error
> 
>
> Key: ATLAS-2922
> URL: https://issues.apache.org/jira/browse/ATLAS-2922
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0, trunk
>
> Attachments: 
> ATLAS-2922-Multiplicity-computation-updated-for-SET-.patch
>
>
> *Pre-requisites*
> From beeline create the table and view.
> _create table daily (c1 string, c2 string, c3 string, c4 string);_
> _create view daily_rpt as select * from daily;_
> Hive-specific entities get created.
> Get the GUID of the column entity.
> *Steps to duplicate*
> Use the following CURL call:
> {code:java}
> curl -X GET -u admin:admin123 -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache" http://localhost:21000/api/atlas/lineage/ above>/schema
> {code}
> _Expected output:_ REST API executes correctly and lineage schema is 
> displayed.
> _Actual output:_ Following error is displayed
> _transfer closed with outstanding read data remaining_
> Part of JSON output is displayed.
> Server logs show serialization error:
> {code:java}
> com.fasterxml.jackson.core.JsonGenerationException: Can not write a field 
> name, expecting a value
>   at 
> com.fasterxml.jackson.core.JsonGenerator._reportError(JsonGenerator.java:1961)
>   at 
> com.fasterxml.jackson.core.json.UTF8JsonGenerator.writeFieldName(UTF8JsonGenerator.java:238)
>   at 
> com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:725)
>   at 
> com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:719)
>   at 
> com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:155)
>   at 
> com.fasterxml.jackson.databind.ser.impl.IndexedListSerializer.serializeContents(IndexedListSerializer.java:119)
>   at
> {code}



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

[jira] [Updated] (ATLAS-2924) Use encoded property name in getEncodedProperty() and setEncodedProperty() methods

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2924:
--
Fix Version/s: 2.0.0

> Use encoded property name in getEncodedProperty() and setEncodedProperty() 
> methods
> --
>
> Key: ATLAS-2924
> URL: https://issues.apache.org/jira/browse/ATLAS-2924
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0, trunk
>
> Attachments: 
> 0001-ATLAS-2924-Use-encoded-property-name-in-getEncodedPr-branch-0.8.patch, 
> 0001-ATLAS-2924-Use-encoded-property-name-in-getEncodedPr-master.patch
>
>
> Use encoded property name in all access to getEncodedProperty() and 
> setEncodedProperty() methods



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

[jira] [Updated] (ATLAS-2923) Newly Added 'Options' to AtlasAttributeDef is Not Available in AttributeDefinition

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2923:
--
Fix Version/s: 2.0.0
   1.2.0

> Newly Added 'Options' to AtlasAttributeDef is Not Available in 
> AttributeDefinition
> --
>
> Key: ATLAS-2923
> URL: https://issues.apache.org/jira/browse/ATLAS-2923
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0, trunk
>
> Attachments: ATLAS-2923-Options-copied-to-AttributeDefinition.patch
>
>
> *Background*
> The newly added _options_ is not present if v1 REST APIs are used.
> *Root cause*
> The copy function present in _AttributeDefinition_ does not include copying 
> options field.



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

[jira] [Updated] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2921:
--
Fix Version/s: 2.0.0
   1.2.0

> Atlas hive-bridge import-hive.sh returns 0 in case of java error
> 
>
> Key: ATLAS-2921
> URL: https://issues.apache.org/jira/browse/ATLAS-2921
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: László Dénes Terjéki
>Priority: Minor
> Fix For: 1.2.0, 2.0.0
>
> Attachments: 
> 0001-ATLAS-2921-Update-import-scripts-exit-status-in-case.patch, 
> ATLAS-2921.000.patch, ATLAS-2921.001.patch
>
>
> When the import-hive.sh runs the java which has an error than the status code 
> is saved but only used for an echo message. Later the script exits with 0 
> code instead of the error code.



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

[jira] [Updated] (ATLAS-3131) UI : Stats Popup Improvements

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3131:
--
Fix Version/s: trunk
   2.0.0

> UI : Stats Popup Improvements
> -
>
> Key: ATLAS-3131
> URL: https://issues.apache.org/jira/browse/ATLAS-3131
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Binit Gutka
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3131-3.patch, ATLAS-3131-4.patch, 
> ATLAS-3131.patch, ATLAS-3131_1.patch, ATLAS-3131_2.patch
>
>




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

[jira] [Updated] (ATLAS-3105) UI : Distorted image is downloaded, for certain conditions

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3105:
--
Fix Version/s: trunk
   2.0.0

> UI : Distorted image is downloaded, for certain conditions 
> ---
>
> Key: ATLAS-3105
> URL: https://issues.apache.org/jira/browse/ATLAS-3105
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3105.patch, download (18).png
>
>
> When a node is dragged the downloaded image does not appear to cover all the 
> nodes. 
> Example attached



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

[jira] [Updated] (ATLAS-3103) UI : Render Schema Table from relationship attributes node in the entity API

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3103:
--
Fix Version/s: trunk
   2.0.0

> UI : Render Schema Table from relationship attributes node in the entity API
> 
>
> Key: ATLAS-3103
> URL: https://issues.apache.org/jira/browse/ATLAS-3103
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Binit Gutka
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3103.patch
>
>




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

[jira] [Updated] (ATLAS-3092) Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3092:
--
Fix Version/s: trunk
   2.0.0

> Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader
> ---
>
> Key: ATLAS-3092
> URL: https://issues.apache.org/jira/browse/ATLAS-3092
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shawn Weeks
>Assignee: Ramesh Mani
>Priority: Minor
> Fix For: 2.0.0, trunk
>
> Attachments: 
> 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently when the AtlasPluginClassLoader is deactivated it sets the current 
> threads class loader to class loader that was active when the class was 
> instantiated. In applications like Hive where a single thread may be shared 
> among multiple sessions each with its own class loader this is breaking class 
> loading for UDFs. The deactivate method should set the current threads class 
> loader back to the class loader that was set when activate was called.



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

[jira] [Updated] (ATLAS-3101) UI Regression : Unable to search by _CLASSIFIED

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3101:
--
Fix Version/s: trunk
   2.0.0

> UI Regression : Unable to search by _CLASSIFIED
> ---
>
> Key: ATLAS-3101
> URL: https://issues.apache.org/jira/browse/ATLAS-3101
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3101.patch
>
>
> On selecting _CLASSIFIED in classifications dropdown , "Search" button is not 
> enabled.
> After selecting _CLASSIFIED in classifications dropdown, selecting a type 
> (say hive_table) from types list , clears the _CLASSIFIED in classifications.
> CC : [~kevalbhatt]



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

[jira] [Updated] (ATLAS-3048) API: Retrieve Audits for Classification Operations: Add support for Entities Not Derived from Referenceable

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3048:
--
Fix Version/s: trunk
   2.0.0

> API: Retrieve Audits for Classification Operations: Add support for Entities 
> Not Derived from Referenceable
> ---
>
> Key: ATLAS-3048
> URL: https://issues.apache.org/jira/browse/ATLAS-3048
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3048-Remove-use-of-hard-coded-qualifiedName.patch
>
>
> **Support entities not derived from _Referencable_. Get unique attribute from 
> the entity type.



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

[jira] [Updated] (ATLAS-3015) Tool: Associate Classifications to Entities based on QualifiedName

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3015:
--
Fix Version/s: trunk
   2.0.0

> Tool: Associate Classifications to Entities based on QualifiedName
> --
>
> Key: ATLAS-3015
> URL: https://issues.apache.org/jira/browse/ATLAS-3015
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nikhil Bonte
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: 0001-ATLAS-3015.patch, 
> ATLAS-3015-Classification-Updater-tool-master.patch
>
>
> *Background*
> Situation: A setup where Atlas classifications associated with entities the 
> data is subsequently erased and all data is lost. Entities are then 
> re-created using _import-hive.sh_. With this approach, the entities are 
> created within Atlas but there is no easy way to associate classifications to 
> these entities.
> *Solution and Approach Guidance*
>  # Before erasing Atlas database, create file with classifications and 
> entity-classification mapping.
>  # Erase the database.
>  # Create entities using appropriate means, say _import-hive.sh_.
>  # Read the file from step 1 and update Atlas.
> The tool should:
>  * Use _AtlasClient_ REST APIs.
>  * External and can be executed against a known Atlas instance.
>  



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

[jira] [Updated] (ATLAS-2810) Add notifications from RelationshipStore

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2810:
--
Fix Version/s: trunk
   2.0.0

> Add notifications from RelationshipStore
> 
>
> Key: ATLAS-2810
> URL: https://issues.apache.org/jira/browse/ATLAS-2810
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Graham Wallis
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-2810-Relationship-notifications.patch, 
> ATLAS-2810-Relationship-notifications.patch
>
>
> The Entity Store provides notifications but the Relationship Store doesn't.



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

[jira] [Updated] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2967:
--
Fix Version/s: 1.2.0

> Save and restore homeId into AtlasRelationship instances
> 
>
> Key: ATLAS-2967
> URL: https://issues.apache.org/jira/browse/ATLAS-2967
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Graham Wallis
>Assignee: Graham Wallis
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2967-2018-11-19.patch
>
>
> In order to save homeId system attribute into a saved AtlasRelationship and 
> retrieve it when reading the relationship, need to update 
> EntityGraphRetriever and AtlasRelationshipStoreV2



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

[jira] [Updated] (ATLAS-2971) Atlas fails to start if there is a empty pid file

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2971:
--
Fix Version/s: 2.0.0
   1.2.0

> Atlas fails to start if there is a empty pid file
> -
>
> Key: ATLAS-2971
> URL: https://issues.apache.org/jira/browse/ATLAS-2971
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sandeep Nemuri
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2971.001.patch
>
>
> Atlas fails to start with below error if the pid file is empty.
>  
> {code:java}
> ~]$ touch /var/run/atlas/atlas.pid
> ~]$ source 
> /usr/hdp/current/atlas-server/conf/atlas-env.sh;/usr/hdp/current/atlas-server/bin/atlas_start.py
>  
> Exception: invalid literal for int() with base 10: '' 
> Traceback (most recent call last): 
> File "/usr/hdp/current/atlas-server/bin/atlas_start.py", line 163, in 
>  
> returncode = main() 
> File "/usr/hdp/current/atlas-server/bin/atlas_start.py", line 105, in main 
> if mc.exist_pid((int)(pid)): 
> ValueError: invalid literal for int() with base 10: '' 
> {code}
>  



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

[jira] [Updated] (ATLAS-2959) Update metrics query to use index query instead of graph query for faster response

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2959:
--
Fix Version/s: 2.0.0

> Update metrics query to use index query instead of graph query for faster 
> response
> --
>
> Key: ATLAS-2959
> URL: https://issues.apache.org/jira/browse/ATLAS-2959
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.1.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.2.0, 2.0.0, trunk
>
>
> Update metrics query to use index query instead of graph query for faster 
> response



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

[jira] [Resolved] (ATLAS-2968) Update model files to include service-type for each entityDef

[Sarath Subramanian (JIRA)]

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

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

> Update model files to include service-type for each entityDef
> -
>
> Key: ATLAS-2968
> URL: https://issues.apache.org/jira/browse/ATLAS-2968
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Kapildeo Nayak
>Assignee: Kapildeo Nayak
>Priority: Major
> Fix For: 1.2.0, 2.0.0, trunk
>
> Attachments: 
> 0001-ATLAS-2968-Update-model-files-to-include-service-typ.patch
>
>
> Adding the service-type value to each typedef’s options param.



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

[jira] [Updated] (ATLAS-2839) Export & Import Process: Documentation

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2839:
--
Fix Version/s: 2.0.0
   1.2.0

> Export & Import Process: Documentation
> --
>
> Key: ATLAS-2839
> URL: https://issues.apache.org/jira/browse/ATLAS-2839
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2839-Export-Import-New-Features-Documentation.patch
>
>
> *Background*
> Existing documentation is not updated with the new improvements made to 
> _Export_ and _Import_ process.
> There are also some updates that need to be made to existing APIs for 
> accuracy.
> *Scope*
>  * Document new _options_.
>  * Document REST API updates made to _AtlasClient_.
>  * Rectify typos in existing documentation.



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

[jira] [Updated] (ATLAS-2957) Fix and enable disabled StormHook Integrations Tests

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2957:
--
Fix Version/s: 2.0.0

> Fix and enable disabled StormHook Integrations Tests
> 
>
> Key: ATLAS-2957
> URL: https://issues.apache.org/jira/browse/ATLAS-2957
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.2.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.2.0, 2.0.0, trunk
>
>
> Fix and enable disabled StormHook Integrations Tests



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

[jira] [Updated] (ATLAS-2938) Enable EntityGraphMapper to update entity version

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2938:
--
Fix Version/s: 1.2.0

> Enable EntityGraphMapper to update entity version 
> --
>
> Key: ATLAS-2938
> URL: https://issues.apache.org/jira/browse/ATLAS-2938
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Graham Wallis
>Assignee: Graham Wallis
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
>




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

[jira] [Updated] (ATLAS-2936) Enable Atlas to store provenance type information

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2936:
--
Fix Version/s: 1.2.0

> Enable Atlas to store provenance type information
> -
>
> Key: ATLAS-2936
> URL: https://issues.apache.org/jira/browse/ATLAS-2936
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Graham Wallis
>Assignee: Graham Wallis
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
>




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

[jira] [Updated] (ATLAS-2875) Implement clear attribute value transformer for Atlas Entity Transformer

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2875:
--
Fix Version/s: 2.0.0
   1.2.0

> Implement clear attribute value transformer for Atlas Entity Transformer
> 
>
> Key: ATLAS-2875
> URL: https://issues.apache.org/jira/browse/ATLAS-2875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
>
> *Condition :*  "hive_table.replicatedTo", "HAS_VALUE:"
> *Action   :*  "hive_table.replicatedTo", "CLEAR:"
>  
> *Condition :*  null
> *Action   :*  "hive_table.replicatedTo", "CLEAR:"



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

[jira] [Updated] (ATLAS-2870) Import Service: Update AddClassification Transform to Support Scope

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2870:
--
Fix Version/s: 2.0.0
   1.2.0

> Import Service: Update AddClassification Transform to Support Scope
> ---
>
> Key: ATLAS-2870
> URL: https://issues.apache.org/jira/browse/ATLAS-2870
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-2870-Improvement-to-AddClassification-transfor.2.patch
>
>
> *Background*
> Existing implementation of _AddClassification_ transform does not allow for 
> restricting addition of classification.
> *Approach*
>  * Add new parameter to _addClassification_ transform, say _topLevel_. This 
> will add the transform only to top level entity. Add methods so that filters 
> can be added to this at runtime.
>  * Not having this parameter, will fallback to the original behavior.
>  * Update _ImportTransform__Shaper_ to use the 
> _ImportResult.getExportResult().getRequest()_ to use to add the required 
> filters to the transform.



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

[jira] [Updated] (ATLAS-2864) Export Process: Incremental: Improve Approach for Fetching Changed Entities

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2864:
--
Fix Version/s: 2.0.0
   1.2.0

> Export Process: Incremental: Improve Approach for Fetching Changed Entities
> ---
>
> Key: ATLAS-2864
> URL: https://issues.apache.org/jira/browse/ATLAS-2864
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-2864-Improved-incremental-export-queries-to-re.patch
>
>
> *Background*
> Existing approach for getting modified entities tends to iterate through the 
> entire set of entities and then filter. This results in no benefit in terms 
> of time and effort for incremental export. It does benefit Import, where 
> smaller set is imported.
> *Approach*
>  * User Gremlin queries to fetch entities that match criteria.
>  * Modify existing logic that does deep traversal to support this new logic.
>  



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

[jira] [Updated] (ATLAS-2869) Export Service: Hdfs Path Export Should Optionally Create Requested Entity and then Proceed With Export

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2869:
--
Fix Version/s: 2.0.0
   1.2.0

> Export Service: Hdfs Path Export Should Optionally Create Requested Entity 
> and then Proceed With Export
> ---
>
> Key: ATLAS-2869
> URL: https://issues.apache.org/jira/browse/ATLAS-2869
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.2, 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-2869-Hdfs_path-if-requested-are-created-and-th.patch
>
>
> *Background*
> Attempting to export entities of type _hdfs_path_, often fails since entities 
> need to be created manually. It would help the user if these requested 
> entities are created and then exported.
> *Approach*
>  * Detect the request type. 
>  * Create _hdfs_path_ entity.
>  * Proceed with regular export.



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

[jira] [Updated] (ATLAS-2895) $ , null characters as replicatedTo value on export.

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2895:
--
Fix Version/s: 2.0.0
   1.2.0

> $ , null characters as replicatedTo value on export.
> 
>
> Key: ATLAS-2895
> URL: https://issues.apache.org/jira/browse/ATLAS-2895
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2895-Server-full-name-processing.patch
>
>
> 1. When the replicatedTo value is set to value that contains "$" in it , 
> cluster name is set incorrectly.
> Example : data_centre$1SFO$cl2 
> On exporting , target cluster name is created as 1SFO
> 2. When replicatedTo is set to "$cl2", "Array out of bounds exception" is 
> seen . Export happens successfully and 200 is returned, but Export Import 
> audits are not created.



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

[jira] [Updated] (ATLAS-2886) Export & Import Process: Add Support for Qualified Cluster Names

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2886:
--
Fix Version/s: 2.0.0

> Export & Import Process: Add Support for Qualified Cluster Names
> 
>
> Key: ATLAS-2886
> URL: https://issues.apache.org/jira/browse/ATLAS-2886
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 2.0.0
>
> Attachments: 
> ATLAS-2886-Export-Import-Support-fully-qualified-ser.patch
>
>
> *Background*
> For cases where cluster same cluster names can exist in different data 
> centers, it helps to add a data center name as prefix to cluster name.
> The _replicatedTo_ and _replicatedFrom_ attributes in _AtlasExportRequest_ 
> and _AtlasImportRequest_ should be the place to specify this.
> *Approach Guidance*
>  * Follow a convention where _data center name_ and cluster name should be 
> separated by $. E.g. _dc1$cl1_
>  * Modify _AuditsWriter_ to support this.
>  * _AtlasServer_ already has _qualifiedName_ as a field. This will hold the 
> fully qualified name.



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

[jira] [Updated] (ATLAS-2886) Export & Import Process: Add Support for Qualified Cluster Names

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2886:
--
Fix Version/s: 1.2.0

> Export & Import Process: Add Support for Qualified Cluster Names
> 
>
> Key: ATLAS-2886
> URL: https://issues.apache.org/jira/browse/ATLAS-2886
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-2886-Export-Import-Support-fully-qualified-ser.patch
>
>
> *Background*
> For cases where cluster same cluster names can exist in different data 
> centers, it helps to add a data center name as prefix to cluster name.
> The _replicatedTo_ and _replicatedFrom_ attributes in _AtlasExportRequest_ 
> and _AtlasImportRequest_ should be the place to specify this.
> *Approach Guidance*
>  * Follow a convention where _data center name_ and cluster name should be 
> separated by $. E.g. _dc1$cl1_
>  * Modify _AuditsWriter_ to support this.
>  * _AtlasServer_ already has _qualifiedName_ as a field. This will hold the 
> fully qualified name.



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

[jira] [Updated] (ATLAS-2874) Include handling of Atlas Entity Transformers in current Import logic

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2874:
--
Fix Version/s: 2.0.0
   1.2.0

> Include handling of Atlas Entity Transformers in current Import logic
> -
>
> Key: ATLAS-2874
> URL: https://issues.apache.org/jira/browse/ATLAS-2874
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
>
> Include handling of Atlas Entity Transformers implemented in ATLAS-2873 in 
> current Import logic



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

[jira] [Updated] (ATLAS-2873) Atlas Import Transform Handler Implementation

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2873:
--
Fix Version/s: 2.0.0
   1.2.0

> Atlas Import Transform Handler Implementation
> -
>
> Key: ATLAS-2873
> URL: https://issues.apache.org/jira/browse/ATLAS-2873
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
>
> Implement atlas entity transformation during import.
>  
> e.g.
> *Condition Operators :* EQUALS, STARTS_WITH
> *Action Operators*   : SET, TO_LOWER, TO_UPPER, REPLACE_PREFIX
>  
> *Condition :*  "hdfs_path.clusterName", "EQUALS: cl1"
> *Action   :*  "hdfs_path.clusterName", "SET: cl2"
>  
> *Condition :*  "hdfs_path.clusterName", "EQUALS: cl1"
> *Action   :*  " hdfs_path.clusterName", "TO_UPPER:"
>  
> *Condition :*  " hdfs_path.clusterName", "EQUALS: CL1"
> *Action   :*  " hdfs_path.clusterName", "TO_LOWER:" 
>  
> *Condition :*  " hdfs_path.name", "STARTS_WITH: /aa/bb/"
> *Action   :*  " hdfs_path.name", "REPLACE_PREFIX: = :/aa/bb/=/xx/yy/"
>  
> *Condition :*  "hive_db.clusterName", "EQUALS: cl1"
> *Action   :*  "hive_db.clusterName", "SET: cl1_backup; 
>  
> *Condition :*  "hive_db.name", "EQUALS: hr"
> *Action   :*  "hive_db.name", "SET: hr_backup"
>  
> *Condition :*  "hive_table.name", "EQUALS: employees"
> *Action   :*  "hive_table.name", "SET: employees_backup"
>  
> *Condition :*  "hive_column.name", "EQUALS: age"
> *Action   :*  "hive_column.name", "SET: age_backup"



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

[jira] [Updated] (ATLAS-2862) Export Service: Incremental Export: Next Increment Should Consider All Existing Request Contexts

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2862:
--
Fix Version/s: 2.0.0
   1.2.0

> Export Service: Incremental Export: Next Increment Should Consider All 
> Existing Request Contexts
> 
>
> Key: ATLAS-2862
> URL: https://issues.apache.org/jira/browse/ATLAS-2862
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
>
> *Background*
> When performing incremental Export, the existing implementation computes the 
> next increment timestamp by finding the maximum value of exported entities' 
> _modificationTimestamp_. This may work for majority of cases, however it has 
> a drawback.
> Consider a scenario where export is in progress and one of the entities that 
> has already been written to the zip stream is modified by another request, 
> this will be missed from the the subsequent export operation.
> *Solution Approach*
>  * Compute timestamps by enumerating all the requests in progress and finding 
> the earliest request. If no requests in progress, return current timestamp.
>  * Use the timestamp from step above for the change timestamp in 
> _AtlasExportResult_.



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

[jira] [Updated] (ATLAS-3091) AtlasGraphProvider: Allow for Creation of JanusGraph DB Connection Initialized with Batch Loading Enabled

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3091:
--
Fix Version/s: trunk
   2.0.0

> AtlasGraphProvider: Allow for Creation of JanusGraph DB Connection 
> Initialized with Batch Loading Enabled
> -
>
> Key: ATLAS-3091
> URL: https://issues.apache.org/jira/browse/ATLAS-3091
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: 
> ATLAS-3091-AtlasGraphProvider-supports-graph-with-ba.patch
>
>
> *Background*
> _JanusGraph_ provides improved performance when _batch-loading_. This mode 
> provides improved performance when large amounts of data has to be written to 
> the database.
> *Solution Guidance*
> Use the existing _AtlasJanusGraphDatabase.getBulkLoadingGraphInstance_ to be 
> returned via _AtlasGraphProvider_.



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

[jira] [Updated] (ATLAS-3017) Add Atlas server statistics rest endpoint

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3017:
--
Fix Version/s: trunk

> Add Atlas server statistics rest endpoint 
> --
>
> Key: ATLAS-3017
> URL: https://issues.apache.org/jira/browse/ATLAS-3017
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3017-Atlas-server-statistics-1.patch, 
> ATLAS-3017-Atlas-server-statistics.patch, ATLAS-3017.patch
>
>
> Provide rest endpoint that will return server statistics e.g. time since 
> server is up, time at last kafka message processed, kafka offset related 
> info, hbase state.



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

[jira] [Updated] (ATLAS-3083) Disable SSLAndKerberosTest & SSLTest etc Unitcases on Master

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3083:
--
Fix Version/s: trunk

> Disable SSLAndKerberosTest & SSLTest etc Unitcases on Master
> 
>
> Key: ATLAS-3083
> URL: https://issues.apache.org/jira/browse/ATLAS-3083
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 2.0.0, trunk
>
> Attachments: 
> 0001-ATLAS-3083-Disable-SSLAndKerberosTest-SSLTest-etc-Un.patch
>
>
> SSLAndKerberosTest & SSLTest etc Unitcases on Master are failing due to 
> version change for hadoop3 in ATLAS-2987.
> This testcases need to be revisited with proper configs for hadoop3



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

[jira] [Updated] (ATLAS-3070) Create patch framework to persist typedef patches applied to atlas

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3070:
--
Fix Version/s: trunk

> Create patch framework to persist typedef patches applied to atlas
> --
>
> Key: ATLAS-3070
> URL: https://issues.apache.org/jira/browse/ATLAS-3070
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.1.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk
>
>
> In Atlas, we don't have a way to see all the type patches applied. The patch 
> framework will create a new vertex in the graph database and update its 
> application state. This will be useful when applying new patches and to make 
> sure not to apply applied patches again. A new REST API is also made 
> available to display all the list of patches and its application status.



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

[jira] [Updated] (ATLAS-2996) Message Processing: Conditionally Prevent Message Processing

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2996:
--
Fix Version/s: 2.0.0
   1.2.0

> Message Processing: Conditionally Prevent Message Processing
> 
>
> Key: ATLAS-2996
> URL: https://issues.apache.org/jira/browse/ATLAS-2996
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0, trunk
>
> Attachments: 
> ATLAS-2996-Conditionally-Prevent-Notification-Proces-HA-Mode.patch, 
> ATLAS-2996-Conditionally-Prevent-Notification-Proces.patch
>
>
> *Background*
> There is a need to start Atlas with its message processing ability shut off. 
> This is necessary when ingesting data via REST calls or using utility like 
> _import-hive.sh_. 
> Once message processing ability is shut off, it is possible to be certain 
> that no changes have been made during the manual import process.
> *Approach Guidance*
>  * Introduce new property say, _atlas.notification.consumer.disabled_
>  * Within _NotificationHookConsumer_, check the value of this property and 
> decide on starting the hook processing thread.



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

[jira] [Updated] (ATLAS-2969) Attempt to import empty zip file should not throw excpetion

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2969:
--
Fix Version/s: 2.0.0

> Attempt to import empty zip file should not throw excpetion
> ---
>
> Key: ATLAS-2969
> URL: https://issues.apache.org/jira/browse/ATLAS-2969
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3, 1.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: 
> 0001-ATLAS-2969-Attempt-to-import-empty-zip-file-should-n.patch, 
> ATLAS-2969-Addressed-UniformInterfaceException-from-.patch
>
>
> When empty zip files is imported do not throw exception., only log the 
> exception.



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

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

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2983:
--
Fix Version/s: 2.0.0
   1.2.0

> 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
>Assignee: Umesh Padashetty
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> 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)

[jira] [Commented] (ATLAS-3151) incorrect return type for AtlasClientV2.getRelationshipByGuid()

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3151:


Commit 2c9376f8cbc15c20b02bfd6b227e7063d29b23bd in atlas's branch 
refs/heads/master from jxzhao
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2c9376f ]

ATLAS-3151: fix clientv2 getRelationshipByGuid bug

Signed-off-by: Madhan Neethiraj 


> incorrect return type for AtlasClientV2.getRelationshipByGuid()
> ---
>
> Key: ATLAS-3151
> URL: https://issues.apache.org/jira/browse/ATLAS-3151
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.1.0, 2.0.0
>Reporter: Madhan Neethiraj
>Priority: Major
>
> Reported by jxzhao via [https://github.com/apache/atlas/pull/42.]
> AtlasClientV2.getRelationshipByGuid() method returns AtlasRelationship; 
> however the REST API from Atlas server returns AtlasRelationshipWithExtInfo. 
> The client should be updated to match the server API.



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

[jira] [Updated] (ATLAS-2856) add utility method to find earliest active request in Atlas server

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2856:
--
Fix Version/s: 2.0.0
   1.2.0

> add utility method to find earliest active request in Atlas server
> --
>
> Key: ATLAS-2856
> URL: https://issues.apache.org/jira/browse/ATLAS-2856
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2856.patch
>
>
> RequestContext class captures context for the current request (i.e. REST API 
> call, Notification processing) in a thread-local. An utility method is needed 
> in this class to find the earliest active request - to be used in incremental 
> export feature.



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

[jira] [Updated] (ATLAS-2843) Atlas Client Support for Export & Import APIs: Change Signature to Support Streams

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2843:
--
Fix Version/s: 2.0.0
   1.2.0

> Atlas Client Support for Export & Import APIs: Change Signature to Support 
> Streams
> --
>
> Key: ATLAS-2843
> URL: https://issues.apache.org/jira/browse/ATLAS-2843
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: 
> ATLAS-2843-AtlasClient-updates-for-exportData-and-im.patch
>
>
> *Background*
> Existing implementation of _AtlasClient.exportData and 
> AtlasClient.importData_ converts the stream returned by the REST APIs to 
> _byte_ array and then passes it on to the caller. 
> In case of _importData_ with absolute file path, it converts it to byte array 
> and then writes the bytes to the file.
> This is inefficient from memory perspective and may cause problems on 
> client-side if the data is large.
> *Solution*
>  * The APIs should return streams.
>  * The API that writes file, should implement a version that works with 
> streams.



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

[jira] [Updated] (ATLAS-2818) Import Process: Tag Entities After Import when 'replicatedFrom' option is Present

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2818:
--
Fix Version/s: 2.0.0
   1.2.0

> Import Process: Tag Entities After Import when 'replicatedFrom' option is 
> Present 
> --
>
> Key: ATLAS-2818
> URL: https://issues.apache.org/jira/browse/ATLAS-2818
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2818-Entity-tagging-after-import.patch
>
>
> *Background*
> It will help user identify entities that are part of Atlas cluster 
> replication if they are tagged as so.
> *Approach Guidance*
>  * Within _AuditWriter_, add logic to tag entities.
>  * Update _EntityGraphMapper_ to tag entities without changing their 
> _modificationTimestamp_.



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

[jira] [Updated] (ATLAS-2845) Rename AtlasCluster to AtlasServer

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2845:
--
Fix Version/s: 2.0.0
   1.2.0

> Rename AtlasCluster to AtlasServer
> --
>
> Key: ATLAS-2845
> URL: https://issues.apache.org/jira/browse/ATLAS-2845
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2845-Renamed-AtlasCluster-to-AtlasServer.patch
>
>
> *Background*
> _AtlasCluster_ to represent cluster to which entities are imported to or 
> exported from can be confusing for user.
> *Solution*
> Rename _AtlasCluster to AtlasServer._



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

[jira] [Updated] (ATLAS-2811) Export Process: Support to Optionally Skip Lineage Entities from Being Exported

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2811:
--
Fix Version/s: 2.0.0
   1.2.0

> Export Process: Support to Optionally Skip Lineage Entities from Being 
> Exported
> ---
>
> Key: ATLAS-2811
> URL: https://issues.apache.org/jira/browse/ATLAS-2811
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-intg
>Affects Versions: 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
>
> *Background*
> In scenarios where importing lineage information can cause ambiguity, it will 
> be worthwhile having an option within Export to skip exporting lineage.
> *Approach Guidance*
>  * Create a mechanism within _ExportService_ to filter out entities based on 
> a criteria.
>  * Within the filter, specify a criteria to skip entities of type _Process_.
>  * _AtlasExportRequest_ should have an option to specify filters. 
>  * _ImportService_ should not be impacted.



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