[jira] [Updated] (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:all-tabpanel
 ]

Nallapati, Sreenivasulu updated ATLAS-3114:
---
Attachment: image-2019-05-07-09-28-21-892.png

> 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: 2010-rdbms_model.json, ATLAS-3114.patch, 
> AtlasClientV2Test.java, Error.txt, image-2019-05-07-09-28-21-892.png, 
> 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: [VOTE] Release Apache Atlas version 2.0.0 - rc2

[Madhan Neethiraj]

Sarath - thanks for the updated release candidate.

+1 for Apache Atlas 2.0.0 release candidate #2

Performed the following:
- downloaded apache-atlas-2.0.0-sources.tar.gz and verified the signature
- built and installed Atlas for embedded HBase, Solr profile
- started Atlas with embedded HBase and Solr
- ran QuickStart successfully
- performed number of searches - both basic and DSL
- created glossaries with number of terms, categories, verified term-entity 
associations, term-category associations, term-classification associations
- added/updated/deleted few 'Favorite Searches' - both basic and DSL
- verified classification propagations

Thanks,
Madhan




On 5/6/19, 2:38 PM, "Sarath Subramanian"  wrote:

Atlas team,

Apache Atlas 2.0.0 Release Candidate #2 is now available for a vote within
dev community.

Following commits went into branch-2.0 since the last release candidate
(rc1):
 - ATLAS-3190: UI - Allow user to refresh metric data inside popup
 - ATLAS-3155: UI - IE-11 - Name entry not clickable (#2)
 - ATLAS-3188: Regression: Simple insert queries are being captured in
ATLAS_HOOK topic
 - ATLAS-3033: Skip hive temp table while getting Table object details from
hiveContext.
 - ATLAS-3187: columns attribute is empty for deleted hive_table entity

Links to the release artifacts are given below. Please review and vote.

The vote will be open for at least 72 hours or until necessary votes are
reached.
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)


Thanks,
Sarath


List of issues addressed in this release:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%202.0.0%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC

Git tag for the release:
https://github.com/apache/atlas/tree/release-2.0.0-rc2
Sources for the release:

https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz

Source release verification:
PGP Signature:

https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.asc
SHA512 Hash:

https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.sha512
MD5 Hash:

https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.md5

Keys to verify the signature of the release artifacts are available at:
https://dist.apache.org/repos/dist/release/atlas/KEYS

Re: Review Request 70512: ATLAS-3183: Read Impala lineage record for creating view and send to Atlas

[Aadarsh Jajodia]

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




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


Replace with
LOG.info("Importing: {}", filename);



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


What are we doing with the return value of this method?



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


What if node itself is null?



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


Do we need this check? We can just put LOG.debug. If log level is set to 
debug it will log it else it will not isnt it?



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


Remove extra line



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


Remove extra line



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


Remove extra line



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


Change ":" to constant



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


Do we need the isDebugEnabled check? We can just put LOG.debug. If log 
level is set to debug it will log it else it will not isnt it?

Do we also need the isColumnLineage check? I see that above we are creating 
objects of columnlineage and hence they will never be NULL. I feel this check 
can be avoided here



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


Add comment for method



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


Add comment for method



addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/events/CreateImpalaProcess.java
Lines 304-310 (patched)


Can be simplified

if (inputNodes.isEmpty() || ouputNodes.isEmpty()) {
return true;
}



addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/ImpalaDependencyType.java
Lines 21 (patched)


extra space after enum


- Aadarsh Jajodia


On May 4, 2019, 9:23 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70512/
> ---
> 
> (Updated May 4, 2019, 9:23 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, madhan, Sarath 
> Subramanian, and Xinran Tinney.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Impala generates lineage records for its commands. This new feature will read 
> Impala lineage file, convert the lineage record to Atlas entities and send 
> them to Atlas. In this way, Atlas can get lineage of Impala operation.
> 
> The metadata referred in the lineage are captured in Hive Metastore hook and 
> sent to Atlas. This work is done in ATLAS-3148
> 
> This jira only supports the Impala command "create view". Following jira will 
> add support for more Impala commands.
> 
> 
> Diffs
> -
> 
>   addons/impala-bridge/pom.xml PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/ImpalaLineageTool.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/AtlasImpalaHookContext.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/ImpalaIdentifierParser.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/ImpalaLineageHook.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/ImpalaOperationParser.java
>  PRE-CREATION 
>   
> 

Re: Review Request 70600: Adding the model files for Spark

[Aadarsh Jajodia]

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

(Updated May 7, 2019, 1:32 a.m.)


Review request for atlas, Ashutosh Mestry, Sridhar K, Le Ma, Madhan Neethiraj, 
and Sarath Subramanian.


Repository: atlas


Description (updated)
---

This is an initial mode file for the SPARK models. Please refer to the file 
added here. This file is a GET call on typeDefs on a cluster which had SAC 
enabled and SAC has created the models. The SAC version used was 
https://github.com/hortonworks/spark-atlas-connector/tree/SAC-CDP-1.0-dev


Diffs
-

  addons/models/1000-Hadoop/1090-spark_model.json PRE-CREATION 


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


Testing
---


File Attachments


SAC Models
  
https://reviews.apache.org/media/uploaded/files/2019/05/07/e31827b2-04c5-4fab-b5b7-4271398831e4__spark_sac_api_model_definition.txt


Thanks,

Aadarsh Jajodia

Review Request 70600: Adding the model files for Spark

[Aadarsh Jajodia]

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

Review request for atlas, Ashutosh Mestry, Sridhar K, Le Ma, Madhan Neethiraj, 
and Sarath Subramanian.


Repository: atlas


Description
---

Adding the model files for Spark


Diffs
-

  addons/models/1000-Hadoop/1090-spark_model.json PRE-CREATION 


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


Testing
---


File Attachments


SAC Models
  
https://reviews.apache.org/media/uploaded/files/2019/05/07/e31827b2-04c5-4fab-b5b7-4271398831e4__spark_sac_api_model_definition.txt


Thanks,

Aadarsh Jajodia

[jira] [Created] (ATLAS-3194) Occasional error when Classification/Tag name contains dot

[Yu-Hsin Chang (JIRA)]

Yu-Hsin Chang created ATLAS-3194:


 Summary: Occasional error when Classification/Tag name contains dot
 Key: ATLAS-3194
 URL: https://issues.apache.org/jira/browse/ATLAS-3194
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Yu-Hsin Chang
Assignee: Yu-Hsin Chang


Steps to reproduce:
 # Create a Classification/Tag called "TEST1" and add an attribute associated 
to it called "attr1"
 # Create another Classification/Tag called "TEST1.attr1". Unknown error occurs.

 

The proposed solution is to not allow dot mark in the classification/tag name 
to avoid confusion stored in Solr.



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

Re: Review Request 70512: ATLAS-3183: Read Impala lineage record for creating view and send to Atlas

[Sridhar K]

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



My review is still pending.
thanks,
-Sridhar


addons/impala-bridge/pom.xml
Lines 65 (patched)


Can we please move this version to a variable?



addons/impala-bridge/pom.xml
Lines 71 (patched)


Can we please move this version to a variable? Use the same variable as 
above.



addons/impala-bridge/pom.xml
Lines 449 (patched)


Please move to variable.


- Sridhar K


On May 4, 2019, 9:23 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70512/
> ---
> 
> (Updated May 4, 2019, 9:23 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, madhan, Sarath 
> Subramanian, and Xinran Tinney.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Impala generates lineage records for its commands. This new feature will read 
> Impala lineage file, convert the lineage record to Atlas entities and send 
> them to Atlas. In this way, Atlas can get lineage of Impala operation.
> 
> The metadata referred in the lineage are captured in Hive Metastore hook and 
> sent to Atlas. This work is done in ATLAS-3148
> 
> This jira only supports the Impala command "create view". Following jira will 
> add support for more Impala commands.
> 
> 
> Diffs
> -
> 
>   addons/impala-bridge/pom.xml PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/ImpalaLineageTool.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/AtlasImpalaHookContext.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/ImpalaIdentifierParser.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/ImpalaLineageHook.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/ImpalaOperationParser.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/events/BaseImpalaEvent.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/hook/events/CreateImpalaProcess.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/IImpalaLineageHook.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/ImpalaDataType.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/ImpalaDependencyType.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/ImpalaNode.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/ImpalaOperationType.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/ImpalaQuery.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/ImpalaVertexType.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/LineageEdge.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/main/java/org.apache.atlas.impala/model/LineageVertex.java
>  PRE-CREATION 
>   addons/impala-bridge/src/main/resources/atlas-log4j.xml PRE-CREATION 
>   addons/impala-bridge/src/main/resources/import-impala.sh PRE-CREATION 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
>  PRE-CREATION 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
>  PRE-CREATION 
>   addons/impala-bridge/src/test/resources/atlas-application.properties 
> PRE-CREATION 
>   addons/impala-bridge/src/test/resources/atlas-log4j.xml PRE-CREATION 
>   addons/impala-bridge/src/test/resources/hive-site.xml PRE-CREATION 
>   addons/impala-bridge/src/test/resources/impala1.json PRE-CREATION 
>   addons/impala-bridge/src/test/resources/impala2.json PRE-CREATION 
>   addons/impala-bridge/src/test/resources/impala3.json PRE-CREATION 
>   addons/impala-bridge/src/test/resources/users-credentials.properties 
> PRE-CREATION 
>   addons/models/1000-Hadoop/1090-impala_model.json PRE-CREATION 
>   pom.xml 7de5d31 
> 
> 
> Diff: https://reviews.apache.org/r/70512/diff/14/
> 
> 
> Testing
> ---
> 
> Run the tool in real cluster that has Atlas server with Impala lineage file 
> as input for creating view. The Atlas UI displays hive_lineage lineage and 
> hive_column_lineage.
> Add new integration tests 

Review Request 70599: Import Service: Improvement to Handle Importing to Existing Entity

[Ashutosh Mestry]

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

Review request for atlas, Madhan Neethiraj, Nikhil Bonte, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

**Background**
Please look at bug description.

**Approach**
_ExportService_: Refactor to extract starting entity logic in a separate 
reusable class.
(New) _StartEntityFetchByExportRequest_: Extracted logic for fetching start 
entity.
_BulkImporterImpl_: Handle _AtlasSchemaViolation_ to update guid of existing 
entity. Uses start entity logic (from _StartEntityFetchByExportRequest_ to 
check and fetch existing entities).
_GraphBackedSearchIndexer_: Additional property to index.

**CURL**

Import:
```
curl -X POST -u admin:passW0rd -H "Content-Type: multipart/form-data" -H 
"Cache-Control: no-cache" -F data=@./stocks.zip 
http://localhost:21000/api/atlas/admin/import
```


Diffs
-

  common/src/main/java/org/apache/atlas/repository/Constants.java 5055a0426 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
 1cfa202a9 
  
repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java 
62298f9f1 
  
repository/src/main/java/org/apache/atlas/repository/impexp/ImportService.java 
a52c3f986 
  
repository/src/main/java/org/apache/atlas/repository/impexp/StartEntityFetchByExportRequest.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/BulkImporterImpl.java
 dc8bd19df 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 14f991697 
  
repository/src/test/java/org/apache/atlas/repository/impexp/ImportServiceTest.java
 a1d6cef5c 
  
repository/src/test/java/org/apache/atlas/repository/impexp/StartEntityFetchByExportRequestTest.java
 PRE-CREATION 
  
tools/classification-updater/src/main/java/org/apache/atlas/tools/BulkFetchAndUpdate.java
 91ff89a00 


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


Testing
---

**Unit tests**
New tests added.

**Functional tests**
Existing export and import flow via CURL calls.


Thanks,

Ashutosh Mestry

[jira] [Created] (ATLAS-3193) Import Service: Importing to Existing Database Fails

[Ashutosh Mestry (JIRA)]

Ashutosh Mestry created ATLAS-3193:
--

 Summary: Import Service: Importing to Existing Database Fails
 Key: ATLAS-3193
 URL: https://issues.apache.org/jira/browse/ATLAS-3193
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: trunk
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk


*Background*

Existing implementation of import assumes that the top-level entity is absent 
in the server that it is importing to.

Users create a place holder entity and then attempt an import. This results in 
failure to import.

*Steps to Duplicate*
 * From beeline: _create database stocks;_ From Atlas ensure that _hive_db_ 
with _qualifiedName:_ _stocks@cl1_ is created.
 * Import stocks database (from _/repository/src/test/resources/stocks.zip_).

*_Expected Results_*

Import will be performed successfully.

*_Actual Results_*

Import fails with exception.

*Solution Guidance*
 * Before starting import, check existence of top-level entities on the server.
 * If top-level entity exists, update its GUID with the one from incoming 
entity. Preserve the changed guid a new field say ___historicalGuids_.
 * If none exist, proceed normally.

 



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

[jira] [Updated] (ATLAS-3193) Import Service: Importing to Existing Database Fails

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry updated ATLAS-3193:
---
Attachment: ATLAS-3193-Import-to-Existing.patch

> Import Service: Importing to Existing Database Fails
> 
>
> Key: ATLAS-3193
> URL: https://issues.apache.org/jira/browse/ATLAS-3193
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3193-Import-to-Existing.patch
>
>
> *Background*
> Existing implementation of import assumes that the top-level entity is absent 
> in the server that it is importing to.
> Users create a place holder entity and then attempt an import. This results 
> in failure to import.
> *Steps to Duplicate*
>  * From beeline: _create database stocks;_ From Atlas ensure that _hive_db_ 
> with _qualifiedName:_ _stocks@cl1_ is created.
>  * Import stocks database (from _/repository/src/test/resources/stocks.zip_).
> *_Expected Results_*
> Import will be performed successfully.
> *_Actual Results_*
> Import fails with exception.
> *Solution Guidance*
>  * Before starting import, check existence of top-level entities on the 
> server.
>  * If top-level entity exists, update its GUID with the one from incoming 
> entity. Preserve the changed guid a new field say ___historicalGuids_.
>  * If none exist, proceed normally.
>  



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

[VOTE] Release Apache Atlas version 2.0.0 - rc2

[Sarath Subramanian]

Atlas team,

Apache Atlas 2.0.0 Release Candidate #2 is now available for a vote within
dev community.

Following commits went into branch-2.0 since the last release candidate
(rc1):
 - ATLAS-3190: UI - Allow user to refresh metric data inside popup
 - ATLAS-3155: UI - IE-11 - Name entry not clickable (#2)
 - ATLAS-3188: Regression: Simple insert queries are being captured in
ATLAS_HOOK topic
 - ATLAS-3033: Skip hive temp table while getting Table object details from
hiveContext.
 - ATLAS-3187: columns attribute is empty for deleted hive_table entity

Links to the release artifacts are given below. Please review and vote.

The vote will be open for at least 72 hours or until necessary votes are
reached.
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)


Thanks,
Sarath


List of issues addressed in this release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%202.0.0%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC

Git tag for the release:
https://github.com/apache/atlas/tree/release-2.0.0-rc2
Sources for the release:
https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz

Source release verification:
PGP Signature:
https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.asc
SHA512 Hash:
https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.sha512
MD5 Hash:
https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.md5

Keys to verify the signature of the release artifacts are available at:
https://dist.apache.org/repos/dist/release/atlas/KEYS

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

[Le Ma (JIRA)]

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

Le Ma commented on ATLAS-3114:
--

Hello [~sreenivasulu_nallap...@intuit.com]

Attached is the model that i used. Please take a look. I am going to close this 
item. But if you have further questions, please feel free to comment, i am 
happy to help :)

Thanks,

Le

> 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: 2010-rdbms_model.json, 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)

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

[Le Ma (JIRA)]

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

Le Ma resolved ATLAS-3114.
--
Resolution: Fixed

> 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: 2010-rdbms_model.json, 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)

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

[Le Ma (JIRA)]

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

Le Ma updated ATLAS-3114:
-
Attachment: 2010-rdbms_model.json

> 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: 2010-rdbms_model.json, 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)

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

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian commented on ATLAS-3190:
---

+1 for patch - ATLAS-3190-1.patch. Thanks [~kevalbhatt].

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




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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3190:


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

ATLAS-3190: UI : Allow user to refresh metric data inside popup

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


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




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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3190:


Commit dfc346d3b87d1dce2268904fec6c26a36be7f2f0 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=dfc346d ]

ATLAS-3190: UI : Allow user to refresh metric data inside popup

Signed-off-by: Sarath Subramanian 


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




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

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

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3190:
--
Component/s: atlas-webui

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




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

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

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3190:
--
Affects Version/s: 2.0.0

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




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

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

[Sarath Subramanian (JIRA)]

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

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

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




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

[jira] [Assigned] (ATLAS-3008) UI: Add local sorting for the Search table

[Binit Gutka (JIRA)]

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

Binit Gutka reassigned ATLAS-3008:
--

Assignee: Binit Gutka  (was: Keval Bhatt)

> UI: Add local sorting for the Search table
> --
>
> Key: ATLAS-3008
> URL: https://issues.apache.org/jira/browse/ATLAS-3008
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Binit Gutka
>Priority: Major
>




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

Total number of results in search results (total count)

[Verdan Mahmood]

Hi,
So we are using Atlas's DSL search API and need to get the total count
along with paginated results.
And to solve this problem, at the moment we are making two queries, one is
to count all the entities and the second one to get the paginated result
using the limit parameters.

Is there a way to include the total count within the search response? Or
any other nicer solution?

Best,
*Verdan Mahmood*
(+31) 655 576 560

[jira] [Created] (ATLAS-3192) UI: Search results page should have a frozen horizontal scroll bar

[Rahul Kurup (JIRA)]

Rahul Kurup created ATLAS-3192:
--

 Summary: UI: Search results page should have a frozen horizontal 
scroll bar
 Key: ATLAS-3192
 URL: https://issues.apache.org/jira/browse/ATLAS-3192
 Project: Atlas
  Issue Type: Improvement
Reporter: Rahul Kurup


If we have a large number of results in the Search results page, and if at the 
same time we have a large number of columns selected from the "Columns" button, 
we have to scroll all the way to the end of the Search Results page in order to 
use the horizontal scroll bar.

This is very cumbersome for navigating horizontally and the only work around 
here is to use arrow keys after clicking inside the table space.

It would be better to have the horizontal scroll bar of the search results 
table frozen in view so that it is easier to use.



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

[jira] [Updated] (ATLAS-3191) UI: Improvement Suggestions for Glossary, Classification Validity and Search page Results display header.

[Rahul Kurup (JIRA)]

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

Rahul Kurup updated ATLAS-3191:
---
Description: 
1. Glossary: It is possible to create duplicate terms for a Glossary by using 
spacing in the beginning (see screenshot below). This should be removed.
!dupterms.jpg|height=250,width=500!

2. Classification Validity Period: In UI, there should be an 
indicator/disclaimer that says it is only enforced by other plugins (Ranger 
etc) or at least a help icon linking to a page that explains the functioning of 
the validity period just like Advanced Search.

3. Search page Results display header: Dynamic text expansion should be 
implemented for large queries in entity Search page. For example, in the 
screenshot below, the large query can be compressed using dynamic text. On 
click or hover, we should see the whole query.

!dyntextquery.jpg|height=250,width=500!

  was:
1. Glossary: It is possible to create duplicate terms for a Glossary by using 
spacing in the beginning (see attached screenshot 
!dupterms.jpg|height=250,width=250! ). This should be removed.

2. Classification Validity Period: In UI, there should be an 
indicator/disclaimer that says it is only enforced by other plugins (Ranger 
etc) or at least a help icon linking to a page that explains the functioning of 
the validity period just like Advanced Search.

3. Search page Results display header: Dynamic text expansion should be 
implemented for large queries in entity Search page. For example, in the 
attached screenshot ( !dyntextquery.jpg|height=250,width=250! ) the large query 
can be compressed using dynamic text. On click or hover, we should see the 
whole query.


> UI: Improvement Suggestions for Glossary, Classification Validity and Search 
> page Results display header.
> -
>
> Key: ATLAS-3191
> URL: https://issues.apache.org/jira/browse/ATLAS-3191
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Rahul Kurup
>Priority: Minor
> Attachments: dupterms.jpg, dyntextquery.jpg
>
>
> 1. Glossary: It is possible to create duplicate terms for a Glossary by using 
> spacing in the beginning (see screenshot below). This should be removed.
> !dupterms.jpg|height=250,width=500!
> 2. Classification Validity Period: In UI, there should be an 
> indicator/disclaimer that says it is only enforced by other plugins (Ranger 
> etc) or at least a help icon linking to a page that explains the functioning 
> of the validity period just like Advanced Search.
> 3. Search page Results display header: Dynamic text expansion should be 
> implemented for large queries in entity Search page. For example, in the 
> screenshot below, the large query can be compressed using dynamic text. On 
> click or hover, we should see the whole query.
> !dyntextquery.jpg|height=250,width=500!



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

[jira] [Updated] (ATLAS-3191) UI: Improvement Suggestions for Glossary, Classification Validity and Search page Results display header.

[Rahul Kurup (JIRA)]

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

Rahul Kurup updated ATLAS-3191:
---
Description: 
1. Glossary: It is possible to create duplicate terms for a Glossary by using 
spacing in the beginning (see attached screenshot 
!dupterms.jpg|height=250,width=250! ). This should be removed.

2. Classification Validity Period: In UI, there should be an 
indicator/disclaimer that says it is only enforced by other plugins (Ranger 
etc) or at least a help icon linking to a page that explains the functioning of 
the validity period just like Advanced Search.

3. Search page Results display header: Dynamic text expansion should be 
implemented for large queries in entity Search page. For example, in the 
attached screenshot ( !dyntextquery.jpg|height=250,width=250! ) the large query 
can be compressed using dynamic text. On click or hover, we should see the 
whole query.

  was:
1. Glossary: It is possible to create duplicate terms for a Glossary by using 
spacing in the beginning (see attached screenshot !dupterms.jpg! ). This should 
be removed.

2. Classification Validity Period: In UI, there should be an 
indicator/disclaimer that says it is only enforced by other plugins (Ranger 
etc) or at least a help icon linking to a page that explains the functioning of 
the validity period just like Advanced Search.

3. Search page Results display header: Dynamic text expansion should be 
implemented for large queries in entity Search page. For example, in the 
attached screenshot ( !dyntextquery.jpg! ) the large query can be compressed 
using dynamic text. On click or hover, we should see the whole query.


> UI: Improvement Suggestions for Glossary, Classification Validity and Search 
> page Results display header.
> -
>
> Key: ATLAS-3191
> URL: https://issues.apache.org/jira/browse/ATLAS-3191
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Rahul Kurup
>Priority: Minor
> Attachments: dupterms.jpg, dyntextquery.jpg
>
>
> 1. Glossary: It is possible to create duplicate terms for a Glossary by using 
> spacing in the beginning (see attached screenshot 
> !dupterms.jpg|height=250,width=250! ). This should be removed.
> 2. Classification Validity Period: In UI, there should be an 
> indicator/disclaimer that says it is only enforced by other plugins (Ranger 
> etc) or at least a help icon linking to a page that explains the functioning 
> of the validity period just like Advanced Search.
> 3. Search page Results display header: Dynamic text expansion should be 
> implemented for large queries in entity Search page. For example, in the 
> attached screenshot ( !dyntextquery.jpg|height=250,width=250! ) the large 
> query can be compressed using dynamic text. On click or hover, we should see 
> the whole query.



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

[jira] [Created] (ATLAS-3191) UI: Improvement Suggestions for Glossary, Classification Validity and Search page Results display header.

[Rahul Kurup (JIRA)]

Rahul Kurup created ATLAS-3191:
--

 Summary: UI: Improvement Suggestions for Glossary, Classification 
Validity and Search page Results display header.
 Key: ATLAS-3191
 URL: https://issues.apache.org/jira/browse/ATLAS-3191
 Project: Atlas
  Issue Type: Improvement
Reporter: Rahul Kurup
 Attachments: dupterms.jpg, dyntextquery.jpg

1. Glossary: It is possible to create duplicate terms for a Glossary by using 
spacing in the beginning (see attached screenshot !dupterms.jpg! ). This should 
be removed.

2. Classification Validity Period: In UI, there should be an 
indicator/disclaimer that says it is only enforced by other plugins (Ranger 
etc) or at least a help icon linking to a page that explains the functioning of 
the validity period just like Advanced Search.

3. Search page Results display header: Dynamic text expansion should be 
implemented for large queries in entity Search page. For example, in the 
attached screenshot ( !dyntextquery.jpg! ) the large query can be compressed 
using dynamic text. On click or hover, we should see the whole query.



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