Re: Review Request 66928: Data Migration: Import: Infer Types that Store Edge Ids

[Sarath Subramanian]

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


Ship it!




Ship It!

- Sarath Subramanian


On May 17, 2018, 1:48 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66928/
> ---
> 
> (Updated May 17, 2018, 1:48 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Ruchi Solani, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2637
> https://issues.apache.org/jira/browse/ATLAS-2637
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> New class: _TypesStoringEdgeIds_: Navigates through all the types in the 
> _typeRegistry_, returns map of entity type and properties that store edge ids.
> Modified: _DataMigrationService_: Uses output from class above and passes it 
> down to migration.
> Modified: _PostProcessManager_: Uses the map generated above and uses it for 
> post processing.
> Modified: _GraphSONUtility_: Improvement to check for vertex of type. This 
> avoids potential exeception when a non-existent property is checked for 
> presence.
> 
> Added PostProcess framework.
> Added logic for handling new Array and Map representation.
> 
> 
> Diffs
> -
> 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
> 607baf664 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraph.java
>  c0b9c1741 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphDatabase.java
>  16aecd5e2 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/AtlasGraphSONReader.java
>  ae119b0bc 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtility.java
>  ec320b03e 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/PostProcessManager.java
>  d0a65f7b1 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/RelationshipTypeCache.java
>  e4e82649b 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessListProperty.java
>  PRE-CREATION 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessor.java
>  PRE-CREATION 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/BaseUtils.java
>  e863d9fae 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtilityPostProcessTest.java
>  4d73c78ef 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtilityTest.java
>  794b5471e 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/MappedElementCacheTest.java
>  cac09d229 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/PostProcessListPropertyTest.java
>  PRE-CREATION 
>   graphdb/janus/src/test/resources/col-2-legacy.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col2.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col3.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col4.json PRE-CREATION 
>   graphdb/janus/src/test/resources/table-v-147504.json 898dce5df 
>   intg/src/main/java/org/apache/atlas/store/AtlasTypeDefStore.java b05754f4b 
>   intg/src/test/java/org/apache/atlas/TestUtilsV2.java 886ce77f5 
>   
> repository/src/main/java/org/apache/atlas/repository/migration/DataMigrationService.java
>  22cd55217 
>   
> repository/src/main/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinder.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasTypeDefGraphStoreV1.java
>  3c84e3c22 
>   
> repository/src/test/java/org/apache/atlas/repository/migration/ComplexAttributesTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/migration/HiveParititionTest.java
>  ac0b79d38 
>   
> repository/src/test/java/org/apache/atlas/repository/migration/HiveStocksTest.java
>  ffbf3200b 
>   
> repository/src/test/java/org/apache/atlas/repository/migration/MigrationBaseAsserts.java
>  ec6e64a25 
>   
> repository/src/test/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinderTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityTestBase.java
>  d810a1166 
>   repository/src/test/resources/complex-attr_db/atlas-migration-data.json 
> PRE-CREATION 
>   

Build failed in Jenkins: Atlas-1.0-AllTests #6

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2697: audit log shows 'Propagated classification added' for

--
[...truncated 299.52 KB...]
[INFO] --- apache-rat-plugin:0.12:check (rat-check) @ atlas-repository ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 61 implicit excludes (use -debug for more details).
[INFO] Exclude: **/antlr4/**
[INFO] Exclude: **/dependency-reduced-pom.xml
[INFO] Exclude: **/javax.script.ScriptEngineFactory
[INFO] Exclude: .reviewboardrc
[INFO] Exclude: 3party-licenses/**
[INFO] Exclude: **/.cache
[INFO] Exclude: **/.cache-main
[INFO] Exclude: **/.cache-tests
[INFO] Exclude: **/.checkstyle
[INFO] Exclude: **/*.txt
[INFO] Exclude: **/*.json
[INFO] Exclude: .pc/**
[INFO] Exclude: debian/**
[INFO] Exclude: .svn/**
[INFO] Exclude: .git/**
[INFO] Exclude: .gitignore
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.twiki
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.log
[INFO] Exclude: **/target/**
[INFO] Exclude: **/target*/**
[INFO] Exclude: **/build/**
[INFO] Exclude: **/*.patch
[INFO] Exclude: derby.log
[INFO] Exclude: **/logs/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/mock/**
[INFO] Exclude: **/data/**
[INFO] Exclude: **/maven-eclipse.xml
[INFO] Exclude: **/.externalToolBuilders/**
[INFO] Exclude: **/build.log
[INFO] Exclude: **/.bowerrc
[INFO] Exclude: *.json
[INFO] Exclude: **/overlays/**
[INFO] Exclude: dev-support/**
[INFO] Exclude: **/users-credentials.properties
[INFO] Exclude: **/public/css/animate.min.css
[INFO] Exclude: **/public/css/bootstrap-sidebar.css
[INFO] Exclude: **/public/js/external_lib/**
[INFO] Exclude: **/node_modules/**
[INFO] Exclude: **/public/js/libs/**
[INFO] Exclude: **/atlas.data/**
[INFO] Exclude: **/${sys:atlas.data}/**
[INFO] Exclude: **/policy-store.txt
[INFO] Exclude: **/*rebel*.xml
[INFO] Exclude: **/*rebel*.xml.bak
[INFO] Exclude: **/test/resources/**
[INFO] 174 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 174 licenses.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:copy-resources (copy-resources-solr) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 9 resources
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 132 source files to 

[INFO] 
:
 Some input files use or override a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 35 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 45 source files to 

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation 

[jira] [Updated] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated ATLAS-2698:
---
Attachment: (was: 0001-ATLAS-2698-Glossary-related-documentation.patch)

> [Glossary] Add docs related to Glossary for Apache site
> ---
>
> Key: ATLAS-2698
> URL: https://issues.apache.org/jira/browse/ATLAS-2698
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 0001-ATLAS-2698-Glossary-related-documentation.patch
>
>
> Updating the docs module to include documentation around Glossary



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

[jira] [Updated] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated ATLAS-2698:
---
Attachment: 0001-ATLAS-2698-Glossary-related-documentation.patch

> [Glossary] Add docs related to Glossary for Apache site
> ---
>
> Key: ATLAS-2698
> URL: https://issues.apache.org/jira/browse/ATLAS-2698
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 0001-ATLAS-2698-Glossary-related-documentation.patch
>
>
> Updating the docs module to include documentation around Glossary



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

[jira] [Updated] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated ATLAS-2698:
---
Attachment: 0001-ATLAS-2698-Glossary-related-documentation.patch

> [Glossary] Add docs related to Glossary for Apache site
> ---
>
> Key: ATLAS-2698
> URL: https://issues.apache.org/jira/browse/ATLAS-2698
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 0001-ATLAS-2698-Glossary-related-documentation.patch
>
>
> Updating the docs module to include documentation around Glossary



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

[jira] [Created] (ATLAS-2698) [Glossary] Add docs related to Glossary for Apache site

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2698:
--

 Summary: [Glossary] Add docs related to Glossary for Apache site
 Key: ATLAS-2698
 URL: https://issues.apache.org/jira/browse/ATLAS-2698
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 1.0.0-alpha
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.0.0


Updating the docs module to include documentation around Glossary



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

[jira] [Updated] (ATLAS-918) UI : Deleted entities show status as DELETED and Datasets should be differentiable in lineage

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-918:
---
Fix Version/s: 0.7-incubating

> UI : Deleted entities show status as DELETED and Datasets should be 
> differentiable in lineage
> -
>
> Key: ATLAS-918
> URL: https://issues.apache.org/jira/browse/ATLAS-918
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 2.20.32 PM.png
>
>
> Keval,
> This jira is to track showing deleted entities with a diff color in lineage. 
> Is there anything missing in the lineage API to implement this? We need to 
> take care of this since no one looks at lineage via a process and will be 
> mostly looking at lineage from a table or  a dataset. Also a table can be 
> dropped and recreated in hive, leading to linage showing as attached in 
> screen shot
> Also can we show the property (status)__status for deleted entities  as 
> "DELETED" . We could display that in "properties" section.



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

[jira] [Updated] (ATLAS-780) UI: Atlas UI shows an API response page after login sometimes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-780:
---
Fix Version/s: 0.7-incubating

> UI: Atlas UI shows an API response page after login sometimes
> -
>
> Key: ATLAS-780
> URL: https://issues.apache.org/jira/browse/ATLAS-780
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Minor
> Fix For: 0.7-incubating
>
>
> I left the Atlas UI up for a while. After maybe an hour I came back and 
> performed some action on it. Possibly because of session expiry it took me 
> back to a login page and I logged in. Instead of taking me to the UI, this 
> showed the JSON response of an API. The URL displayed after login was 
> {{http://localhost:21000/api/atlas/types?type=TRAIT}}. This would probably be 
> a little confusing to the end user.



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

[jira] [Commented] (ATLAS-1968) Export/Import - Exception thrown when Import fired with zip file found on server

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry commented on ATLAS-1968:


Commit: 3d3be4084

> Export/Import -  Exception thrown when Import fired with zip file found on 
> server
> -
>
> Key: ATLAS-1968
> URL: https://issues.apache.org/jira/browse/ATLAS-1968
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.1, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Blocker
> Attachments: ATLAS-1968-Importfile-option.patch, 
> ImportExceptionWhenZipFileOnServer.txt
>
>
> 1. Exported an entity on the cluster1 ,created zip file and placed it in /tmp 
> location of cluster2 .
> 2. Fired the following import command against cluster2 :
> {code}
> curl -v -X POST -u admin:admin  
> "http://cluster2:21000/api/atlas/admin/importFile?FILENAME=/tmp/entity.zip; 
> {code}
> The import command failed with 500 internal server error.
> Attached the exception stack trace found in cluster2's application logs.



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

[jira] [Comment Edited] (ATLAS-2139) Map IGC meta model and Atlas OMRS open metadata types

[V Seth (JIRA)]

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

V Seth edited comment on ATLAS-2139 at 5/17/18 9:54 PM:


Thanks [~davidrad] [~grahamwallis] for the response.

[~mandy_chessell], here are the mappings from IGC to OMRS per your response:

1 IGC database maps to DeployedDatabaseSchema entity.  ServerDeployment 
relationship ties the DeployedDatabaseSchema entity with Host entity.

2a IGC schema is a DataSet entity in OMRS.  Database thru DataContentForDataSet 
relationship contains the schema.
 2b For IGC schema a second entity and relationship will have to be created.  
RelationalDBSchemaType entity and it links to DataSet(schema) via 
AssetSchemaType relationship.  This second entity identifies
    the DataSet as a schema.

3a IGC table is a DataSet entity in OMRS.  Dataset(Schema) thru 
DataContentForDataSet relationship contains the table.
 3b For IGC table a second entity and relationship will have to be created - 
RelationalTableType entity and it links to DataSet(table) via AssetSchemaType 
relationship.  This second entity identifies the DataSet as a table.
 3c For IGC table a third entity and relationship will have to be created - 
RelationalTable entity and it links to RelationalTableType entity via 
AttributeForSchema relationship

4a IGC column is an Asset entity in OMRS. DataSet(Table) thru 
DataContentForDataSet relationship contains the column.
 4b For IGC column a second entity and relationship will have to be created - 
RelationalColumnType entity and it links to Asset(column) via AssetSchemaType 
relationship.  This second entity identified the Asset as a column.
 4c For IGC column a third entity and relationship will have to be created - 
RelationalColumn entity and it links to RelationalColumnType entity via 
SchemaAttributeType relationship.

Here are few questions I have:
 1 Would Asset qualifiedName be the right place to put schema name, table name, 
column name.  i guess i can duplicate that name in SchemaType and 
SchemaAttribute because there is nothing in IGC which differentiates.

2 Does the above mapping look correct to you?

3 I am concerned about the number of messages that will be generated to create 
an entity.  For a single schema entity, two entities and two relationships.  
For a single table or column three entities and three relationships.  Any 
thoughts on this?

Thanks in advance.


was (Author: sethv):
Thanks [~davidrad] [~grahamwallis] for the response.

[~mandy_chessell], here are the mappings from IGC to OMRS per your response:

1 IGC database maps to DeployedDatabaseSchema entity.  ServerDeployment 
relationship ties the DeployedDatabaseSchema entity with Host entity.

2a IGC schema is a DataSet entity in OMRS.  Database thru DataContentForDataSet 
relationship contains the schema.
2b For IGC schema a second entity and relationship will have to be created.  
RelationalDBSchemaType entity and it links to DataSet(schema) via 
AssetSchemaType relationship.  This second entity identifies
   the DataSet as a schema.

3a IGC table is a DataSet entity in OMRS.  Dataset(Schema) thru 
DataContentForDataSet relationship contains the table.
3b For IGC table a second entity and relationship will have to be created - 
RelationalTableType entity and it links to DataSet(table) via AssetSchemaType 
relationship.  This second entity identifies the DataSet as a table.
3c For IGC table a third entity and relationship will have to be created - 
RelationalTable entity and it links to RelationalTableType entity via 
AttributeForSchema relationship

4a IGC column is a DataSet entity in OMRS. DataSet(Table) thru 
DataContentForDataSet relationship contains the column.
4b For IGC column a second entity and relationship will have to be created - 
RelationalColumnType entity and it links to DataSet(column) via AssetSchemaType 
relationship.  This second entity identified the DataSet as a column.
4c For IGC column a third entity and relationship will have to be created - 
RelationalColumn entity and it links to RelationalColumnType entity via 
SchemaAttributeType relationship.


Here are few questions I have:
1 Would Asset qualifiedName be the right place to put schema name, table name, 
column name.  i guess i can duplicate that name in SchemaType and 
SchemaAttribute because there is nothing in IGC which differentiates.


2 Does the above mapping look correct to you?


3 I am concerned about the number of messages that will be generated to create 
an entity.  For a single schema entity, two entities and two relationships.  
For a single table or column three entities and three relationships.  Any 
thoughts on this?

Thanks in advance.

> Map IGC meta model and Atlas OMRS open metadata types
> -
>
> Key: ATLAS-2139
> URL: 

Re: Review Request 66928: Data Migration: Import: Infer Types that Store Edge Ids

[Ashutosh Mestry]

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

(Updated May 17, 2018, 8:48 p.m.)


Review request for atlas, Madhan Neethiraj, Ruchi Solani, and Sarath 
Subramanian.


Changes
---

Updates include: Addressed review comments.


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


Repository: atlas


Description
---

**Approach**
New class: _TypesStoringEdgeIds_: Navigates through all the types in the 
_typeRegistry_, returns map of entity type and properties that store edge ids.
Modified: _DataMigrationService_: Uses output from class above and passes it 
down to migration.
Modified: _PostProcessManager_: Uses the map generated above and uses it for 
post processing.
Modified: _GraphSONUtility_: Improvement to check for vertex of type. This 
avoids potential exeception when a non-existent property is checked for 
presence.

Added PostProcess framework.
Added logic for handling new Array and Map representation.


Diffs (updated)
-

  graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
607baf664 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraph.java
 c0b9c1741 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphDatabase.java
 16aecd5e2 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/AtlasGraphSONReader.java
 ae119b0bc 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtility.java
 ec320b03e 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/PostProcessManager.java
 d0a65f7b1 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/RelationshipTypeCache.java
 e4e82649b 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessListProperty.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessor.java
 PRE-CREATION 
  
graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/BaseUtils.java
 e863d9fae 
  
graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtilityPostProcessTest.java
 4d73c78ef 
  
graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtilityTest.java
 794b5471e 
  
graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/MappedElementCacheTest.java
 cac09d229 
  
graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/PostProcessListPropertyTest.java
 PRE-CREATION 
  graphdb/janus/src/test/resources/col-2-legacy.json PRE-CREATION 
  graphdb/janus/src/test/resources/edge-legacy-col.json PRE-CREATION 
  graphdb/janus/src/test/resources/edge-legacy-col2.json PRE-CREATION 
  graphdb/janus/src/test/resources/edge-legacy-col3.json PRE-CREATION 
  graphdb/janus/src/test/resources/edge-legacy-col4.json PRE-CREATION 
  graphdb/janus/src/test/resources/table-v-147504.json 898dce5df 
  intg/src/main/java/org/apache/atlas/store/AtlasTypeDefStore.java b05754f4b 
  intg/src/test/java/org/apache/atlas/TestUtilsV2.java 886ce77f5 
  
repository/src/main/java/org/apache/atlas/repository/migration/DataMigrationService.java
 22cd55217 
  
repository/src/main/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinder.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasTypeDefGraphStoreV1.java
 3c84e3c22 
  
repository/src/test/java/org/apache/atlas/repository/migration/ComplexAttributesTest.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/migration/HiveParititionTest.java
 ac0b79d38 
  
repository/src/test/java/org/apache/atlas/repository/migration/HiveStocksTest.java
 ffbf3200b 
  
repository/src/test/java/org/apache/atlas/repository/migration/MigrationBaseAsserts.java
 ec6e64a25 
  
repository/src/test/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinderTest.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityTestBase.java
 d810a1166 
  repository/src/test/resources/complex-attr_db/atlas-migration-data.json 
PRE-CREATION 
  repository/src/test/resources/complex-attr_db/atlas-migration-typesdef.json 
PRE-CREATION 
  repository/src/test/resources/parts_db/atlas-migration-data.json 1414ea160 


Diff: https://reviews.apache.org/r/66928/diff/15/

Changes: https://reviews.apache.org/r/66928/diff/14-15/


Testing
---

**Unit tests**

Additional tests added.

**Functional tests**

Regular flow verified.

**[Pre-commit 
build](https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/416/)**


Thanks,

Ashutosh Mestry

[jira] [Resolved] (ATLAS-2517) denied audit log is missing for read entity operation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-2517.
-
   Resolution: Cannot Reproduce
Fix Version/s: (was: 1.0.0)

> denied audit log is missing for read entity operation
> -
>
> Key: ATLAS-2517
> URL: https://issues.apache.org/jira/browse/ATLAS-2517
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Deepak Sharma
>Priority: Major
>
> Scenario:
> 1) remove read entity permission for an user.
> 2) through that user try to read the entity
> Result:
> read operation fails due to "admin is not authorized to perform read entity"
> but denied audit log is missing for this operation



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

Re: Review Request 66928: Data Migration: Import: Infer Types that Store Edge Ids

[Sarath Subramanian]

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




repository/src/main/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinder.java
Lines 66 (patched)


getProperties() method in 66 can be replaced with one in line 82. 
AtlasStructDef is supertype of AtlasEntityDef.



repository/src/main/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinder.java
Lines 109 (patched)


rename 109 and 113 with getArrayElementType and getMapValueType for better 
readability.



repository/src/main/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinder.java
Lines 117 (patched)


update() and updatePrimitive() looks duplicate of each other with only 
"_PRIMTITIVE" string difference, can be refactored into a single method.


- Sarath Subramanian


On May 15, 2018, 10:58 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66928/
> ---
> 
> (Updated May 15, 2018, 10:58 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Ruchi Solani, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2637
> https://issues.apache.org/jira/browse/ATLAS-2637
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> New class: _TypesStoringEdgeIds_: Navigates through all the types in the 
> _typeRegistry_, returns map of entity type and properties that store edge ids.
> Modified: _DataMigrationService_: Uses output from class above and passes it 
> down to migration.
> Modified: _PostProcessManager_: Uses the map generated above and uses it for 
> post processing.
> Modified: _GraphSONUtility_: Improvement to check for vertex of type. This 
> avoids potential exeception when a non-existent property is checked for 
> presence.
> 
> Added PostProcess framework.
> Added logic for handling new Array and Map representation.
> 
> 
> Diffs
> -
> 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
> 607baf664 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraph.java
>  c0b9c1741 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphDatabase.java
>  16aecd5e2 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/AtlasGraphSONReader.java
>  ae119b0bc 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtility.java
>  ec320b03e 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/PostProcessManager.java
>  d0a65f7b1 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/RelationshipTypeCache.java
>  e4e82649b 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessListProperty.java
>  PRE-CREATION 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessor.java
>  PRE-CREATION 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/BaseUtils.java
>  e863d9fae 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtilityPostProcessTest.java
>  4d73c78ef 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtilityTest.java
>  794b5471e 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/MappedElementCacheTest.java
>  cac09d229 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/PostProcessListPropertyTest.java
>  PRE-CREATION 
>   graphdb/janus/src/test/resources/col-2-legacy.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col2.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col3.json PRE-CREATION 
>   graphdb/janus/src/test/resources/edge-legacy-col4.json PRE-CREATION 
>   graphdb/janus/src/test/resources/table-v-147504.json 898dce5df 
>   intg/src/main/java/org/apache/atlas/store/AtlasTypeDefStore.java b05754f4b 
>   intg/src/test/java/org/apache/atlas/TestUtilsV2.java 886ce77f5 
>   
> repository/src/main/java/org/apache/atlas/repository/migration/DataMigrationService.java
>  22cd55217 
>   
> repository/src/main/java/org/apache/atlas/repository/migration/TypesWithCollectionsFinder.java
>  PRE-CREATION 
>   
> 

[jira] [Updated] (ATLAS-2478) Elasticsearch support (Tech Preview) is broken for JanusGraph

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2478:

Summary: Elasticsearch support (Tech Preview) is broken for JanusGraph  
(was: Elasticsearch support is broken for JanusGraph)

> Elasticsearch support (Tech Preview) is broken for JanusGraph
> -
>
> Key: ATLAS-2478
> URL: https://issues.apache.org/jira/browse/ATLAS-2478
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0-alpha
>Reporter: Pierre Padovani
>Assignee: Pierre Padovani
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2478.patch
>
>
> With JanusGraph the Elasticsearch support moved to 5.x+. This introduced a 
> change where fields that contained '.' (dots) were not allowed unless either 
> a specific cluster wide setting was enabled AND the mapping was formatted 
> such that each of the fields that contained a '.' could be considered part of 
> an object.
> Example:
> {code:java}
> foo.x
> foo.y
> foo.z{code}
>  Elasticsearch looks at these fields as if they are truly:
> {code:java}
> foo : {
>   x,
>   y,
>   z
> }{code}
> In the file:
> /atlas/common/src/main/java/org/apache/atlas/repository/Constants.java
> {code:java}
> /**
>  * Properties for type store graph.
>  */
> public static final String TYPE_CATEGORY_PROPERTY_KEY = 
> INTERNAL_PROPERTY_KEY_PREFIX + "type.category";
> public static final String VERTEX_TYPE_PROPERTY_KEY = 
> INTERNAL_PROPERTY_KEY_PREFIX + "type";
> public static final String TYPENAME_PROPERTY_KEY = 
> INTERNAL_PROPERTY_KEY_PREFIX + "type.name";
> public static final String TYPEDESCRIPTION_PROPERTY_KEY = 
> INTERNAL_PROPERTY_KEY_PREFIX + "type.description";
> public static final String TYPEVERSION_PROPERTY_KEY = 
> INTERNAL_PROPERTY_KEY_PREFIX + "type.version";
> public static final String TYPEOPTIONS_PROPERTY_KEY = 
> INTERNAL_PROPERTY_KEY_PREFIX + "type.options";
> {code}
> These are the only fields that cause Elasticsearch issue. As you can see a 
> field called 'type' is created, then additional fields type.name, 
> type.description etc. This will cause a mapping conflict exception in 
> Elasticsearch and it will refuse to create the mapping.
>  
> The easy fix is to simply replace the '.' with an '_' (underscore) but this 
> will be a backwards incompatible change for existing customers. 



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

Re: Review Request 66064: ATLAS-2478 Elasticsearch support broken with JanusGraph 0.2.0

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On May 17, 2018, 2:39 p.m., Pierre Padovani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66064/
> ---
> 
> (Updated May 17, 2018, 2:39 p.m.)
> 
> 
> Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2478
> https://issues.apache.org/jira/browse/ATLAS-2478
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch fixes the Elasticsearch support for JanusGraph 0.2.0 and updates 
> documentation.
> 
> Included with this patch is an update to the berkley-elasticsearch profile to 
> automatically download and include elasticsearch as a side application much 
> like solr is. Updates to the start/stop/conf scripts are included as well.
> 
> NOTE: This patch includes a **BACKWARDS INCOMPATIBLE** change to 
> /atlas/common/src/main/java/org/apache/atlas/repository/Constants.java. There 
> are six constants that are incorrectly named with a '.' (dot). This is not 
> supported in Elasticsearch 5 and beyond when defining a mapping **UNLESS** 
> the field names can be collectively thought of as an object. In the case of 
> the fields defined in the Constants.java file, 'type' is defined as a string 
> field, and 'type.name' is also defined as a string field. Elasticsearch sees 
> this as an error, since it cannot convert type to an object. The fix included 
> simply changes the field names from using a '.' (dot) to an '_' (underscore). 
> This should NOT affect compatibility with hbase/solr for new installs. For 
> existing installations, a reindex will be required as the field names will 
> have changed.
> 
> **Query**: There is a way we can simplify integration/unit tests for the 
> in-memory graph store by using a maven plugin that will download and run an 
> elasticsearch node. This is nothing more than a maven change, and change to 
> the atlas-application.properties to switch to elasticsearch from solr. I did 
> not implement this, but am curious if this change would be desired. If so, 
> this can be done with a separate ticket.
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/repository/Constants.java 3732556ae 
>   distro/pom.xml 379ff0d39 
>   distro/src/bin/atlas_config.py 9062da649 
>   distro/src/bin/atlas_start.py 61d69eb21 
>   distro/src/bin/atlas_stop.py 94c3d6d46 
>   distro/src/conf/atlas-env.sh 053cbd500 
>   distro/src/main/assemblies/standalone-package.xml dc88add56 
>   docs/src/site/twiki/Configuration.twiki 63c3fce96 
>   docs/src/site/twiki/HighAvailability.twiki 4270d0974 
>   docs/src/site/twiki/InstallationSteps.twiki dca0618e3 
>   graphdb/janus/pom.xml 016a09c33 
>   pom.xml 3469a393a 
>   webapp/pom.xml 03b84087f 
> 
> 
> Diff: https://reviews.apache.org/r/66064/diff/6/
> 
> 
> Testing
> ---
> 
> We currently use this fix with our Atlas setup in a fork of the Atlas code, 
> and have found no issues with it. Additionally, with the update to the 
> berkley-elasticsearch profile, I have extensively tested that profile to make 
> sure that management of Elasticsearch functioned correctly.
> 
> 
> Thanks,
> 
> Pierre Padovani
> 
>

[jira] [Updated] (ATLAS-1008) Change log message in HiveMetaStoreBridge

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1008:

Fix Version/s: 0.8-incubating

> Change log message in HiveMetaStoreBridge
> -
>
> Key: ATLAS-1008
> URL: https://issues.apache.org/jira/browse/ATLAS-1008
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
>Priority: Trivial
> Fix For: 0.8-incubating
>
>
> LOG.error("Unable to import {} tables out of {} tables from {}", 
> tablesImported, hiveTables.size(), databaseName);
> Unable to import 18 tables out of 19 tables from default 
> (HiveMetaStoreBridge:318)
> No of tables successfully imported are print instead of the number of tables 
> for which import failed



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

[jira] [Resolved] (ATLAS-1094) Receiving Null characters or Binary data when writing logs to a file at the begining

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1094.
-
Resolution: Invalid

> Receiving Null characters or Binary data when writing logs to a file at the 
> begining
> 
>
> Key: ATLAS-1094
> URL: https://issues.apache.org/jira/browse/ATLAS-1094
> Project: Atlas
>  Issue Type: Bug
>Reporter: Harish Anand Kuchana
>Priority: Major
>




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

[jira] [Reopened] (ATLAS-1094) Receiving Null characters or Binary data when writing logs to a file at the begining

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reopened ATLAS-1094:
-

> Receiving Null characters or Binary data when writing logs to a file at the 
> begining
> 
>
> Key: ATLAS-1094
> URL: https://issues.apache.org/jira/browse/ATLAS-1094
> Project: Atlas
>  Issue Type: Bug
>Reporter: Harish Anand Kuchana
>Priority: Major
>




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

[jira] [Resolved] (ATLAS-1134) Full text search for "id" shows the blank screen in some case

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1134.
-
Resolution: Cannot Reproduce

> Full text search for "id" shows the blank screen in some case
> -
>
> Key: ATLAS-1134
> URL: https://issues.apache.org/jira/browse/ATLAS-1134
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>Priority: Major
> Attachments: ATLAS-1134.patch
>
>
> Step to reproduce - 
> 1.Search for "id" in full text. 
> 2.In case of entity Id is null, it doesn't shows the result, loader is 
> display on screen.



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

[jira] [Updated] (ATLAS-1211) Classifications : Support subclasifications & ordering

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1211:

Fix Version/s: 1.0.0

> Classifications : Support subclasifications & ordering
> --
>
> Key: ATLAS-1211
> URL: https://issues.apache.org/jira/browse/ATLAS-1211
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
>
> Governance classifications may be ordered and contain sub-classifications.
> For example a classification "confidentiality" may contain an *ordered* set 
> of values such as
>  - unclassified
>  - internal use
>  - confidential
>  - sensitive
>  - restricted
>  - top secret
> The ordering is a logical progression -- going from the least confidential to 
> the most confidential. 
> When these governance classifications are retrieved or checked against we may 
> wish to performance range checks. For example in a ranger policy we may wish 
> to do the equivilent of "if confidentiality >= confidential then.."
> Furthermore these classifications may be hierarchical. The mail thread below 
> uses the example "confidential/business confidential" and 
> "confidential/personal confidential". these are at an equivilent level, but 
> different
> Atlas should be extended to support this.(further JIRAs would be needed to 
> update ranger)
> In terms of implementation, For existing apis/tag integration we may consider 
> a form of flattening or overloading the name to ease migration.
> Note that this will prereq the anticipated work on ATLAS-1187 to introduce 
> classifications, but I've split this further development out so that we can 
> get a first pass done in 1187
> This suggestion first came up in the mailing list discussion on "Rename Trait 
> to classification", which relates to ATLAS-1187 - also viewable on gmane at 
> news://news.gmane.org:119/nt0jdp$ml0$1...@blaine.gmane.org



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

[jira] [Resolved] (ATLAS-1260) Support fuzzy query in web page

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1260.
-
Resolution: Implemented  (was: Fixed)

> Support fuzzy query in web page
> ---
>
> Key: ATLAS-1260
> URL: https://issues.apache.org/jira/browse/ATLAS-1260
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Qiang Zhang
>Priority: Major
>
> use SEARCH in web page, find that our search policy cannot support fuzzy 
> query.
> eg:  Stored data to three tables, such as login_dept1, login_dept2, 
> login_dept3. 
> There are three scenarios: 
> 1. When  SEARCH condition is "login_dept", can't display any result.
> 2. When SEARCH condition is "login_dept*", can display  three tables 
> information ( login_dept1, login_dept2, login_dept3 ).
> 3. When  SEARCH condition is "login__dept1", can display one table 
> information (login_dept1).
> It would be convenient for users to provide fuzzy query by default, because 
> ordinary users may not be aware of using fuzzy query by wildcard 
> character(*).  meanwhile it may consumption query speed.
> We can have a discussion that whether it is necessary to add wildcard 
> character(*) in our default SEARCH condition automatically?



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

[jira] [Closed] (ATLAS-1260) Support fuzzy query in web page

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj closed ATLAS-1260.
---

> Support fuzzy query in web page
> ---
>
> Key: ATLAS-1260
> URL: https://issues.apache.org/jira/browse/ATLAS-1260
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Qiang Zhang
>Priority: Major
>
> use SEARCH in web page, find that our search policy cannot support fuzzy 
> query.
> eg:  Stored data to three tables, such as login_dept1, login_dept2, 
> login_dept3. 
> There are three scenarios: 
> 1. When  SEARCH condition is "login_dept", can't display any result.
> 2. When SEARCH condition is "login_dept*", can display  three tables 
> information ( login_dept1, login_dept2, login_dept3 ).
> 3. When  SEARCH condition is "login__dept1", can display one table 
> information (login_dept1).
> It would be convenient for users to provide fuzzy query by default, because 
> ordinary users may not be aware of using fuzzy query by wildcard 
> character(*).  meanwhile it may consumption query speed.
> We can have a discussion that whether it is necessary to add wildcard 
> character(*) in our default SEARCH condition automatically?



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

[jira] [Updated] (ATLAS-1280) Atlas changes to support Hive hook for Hive2

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1280:

Fix Version/s: 0.8-incubating

> Atlas changes to support Hive hook for Hive2
> 
>
> Key: ATLAS-1280
> URL: https://issues.apache.org/jira/browse/ATLAS-1280
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1280-v1.patch, ATLAS-1280.patch
>
>
> Atlas is currently built with Hive version 1.2
> Due to significant changes in Hive2(LLAP), some changes are required in Atlas 
> Hive Hook code to ensure that hook works correctly



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

[jira] [Updated] (ATLAS-1272) Update types bootstrap to load from new format typedef JSON files

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1272:

Fix Version/s: 0.8-incubating

> Update types bootstrap to load from new format typedef JSON files
> -
>
> Key: ATLAS-1272
> URL: https://issues.apache.org/jira/browse/ATLAS-1272
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1272.3.patch, ATLAS-1272.patch
>
>
> Atlas server bootstraps types from contents of 'models' directory under 
> atlas.home. This directory contains JSON files in legacy format. Replace the 
> contents of this directory with the JSON files that use current format of 
> typesdef i.e. introduced in ATLAS-1171.
>  



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

[jira] [Updated] (ATLAS-1291) Type "hive_column_lineage" not present in hive_model.json

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1291:

Fix Version/s: 0.8-incubating

> Type "hive_column_lineage" not present in hive_model.json
> -
>
> Key: ATLAS-1291
> URL: https://issues.apache.org/jira/browse/ATLAS-1291
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1291.patch
>
>
> Type "hive_column_lineage" was generated in HiveDataModelGenerator.java.
> The above file has been deprecated and the types are now registered from 
> hive_model.json inside models directory.
> This file does not contain the type definition JSON for type 
> "hive_column_lineage". Due to this, column level lineage hook messages are 
> failing to be registered with Atlas.



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

[jira] [Updated] (ATLAS-1292) Atlas webapp Integration Tests failing

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1292:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/9dc96c46

> Atlas webapp Integration Tests failing 
> ---
>
> Key: ATLAS-1292
> URL: https://issues.apache.org/jira/browse/ATLAS-1292
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Apoorv Naik
>Priority: Blocker
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1292.patch
>
>
> {noformat}
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.103 sec - 
> in org.apache.atlas.web.resources.TypesJerseyResourceIT
> Results :
> Failed tests:
>   EntityNotificationIT.testCreateEntity:85->BaseResourceIT.createInstance:114 
> » AtlasService
>   
> EntityNotificationIT.testDeleteEntity:111->BaseResourceIT.createInstance:114 
> » AtlasService
>   NotificationHookConsumerIT.testCreateEntity:89->BaseResourceIT.waitFor:287 
> »  ...
>   NotificationHookConsumerIT.testDeleteByQualifiedName:164 » AtlasService 
> Metada...
>   
> NotificationHookConsumerIT.testMessageHandleFailureConsumerContinues:72->BaseResourceIT.waitFor:287
>  »
>   NotificationHookConsumerIT.testUpdateEntityFullUpdate:183 » AtlasService 
> Metad...
>   NotificationHookConsumerIT.testUpdateEntityPartial:111 » AtlasService 
> Metadata...
>   NotificationHookConsumerIT.testUpdatePartialUpdatingQualifiedName:136 » 
> AtlasService
>   
> DataSetLineageJerseyResourceIT.setUp:58->setupInstances:224->database:272->BaseResourceIT.createInstance:114
>  » AtlasService
>   
> EntityJerseyResourceIT.testDeleteEntitiesViaClientApi:874->BaseResourceIT.createInstance:114
>  » AtlasService
>   
> EntityJerseyResourceIT.testDeleteEntitiesViaRestApi:844->BaseResourceIT.createInstance:114
>  » AtlasService
>   
> EntityJerseyResourceIT.testDeleteEntityByUniqAttribute:903->BaseResourceIT.createInstance:114
>  » AtlasService
>   EntityJerseyResourceIT.testEntityDeduping:176 » AtlasService Metadata 
> service ...
>   
> EntityJerseyResourceIT.testGetEntityByAttribute:283->BaseResourceIT.createInstance:114
>  » AtlasService
>   EntityJerseyResourceIT.testRequestUser:138 » AtlasService Metadata service 
> API...
>   
> EntityJerseyResourceIT.testSubmitEntity:115->BaseResourceIT.createInstance:114
>  » AtlasService
>   EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:299 
> expected: but was:
>   EntityJerseyResourceIT.testSubmitSingleEntity:156 expected:<201> but 
> was:<400>
>   
> EntityLineageJerseyResourceIT.setUp:62->setupInstances:157->database:204->BaseResourceIT.createInstance:114
>  » AtlasService
>   TypedefsJerseyResourceIT.testCreate:86 » AtlasService Metadata service API 
> org...
>   TypedefsJerseyResourceIT.testDuplicateCreate:98 » AtlasService Metadata 
> servic...
>   TypedefsJerseyResourceIT.testListTypesByFilter:254 » AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:118 » AtlasService Metadata service API 
> or...
> Tests run: 92, Failures: 23, Errors: 0, Skipped: 31
> {noformat}



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

[jira] [Updated] (ATLAS-1300) LineageResource API needs to map to the new LineageREST API

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1300:

Fix Version/s: 0.8-incubating

> LineageResource API needs to map to the new LineageREST API
> ---
>
> Key: ATLAS-1300
> URL: https://issues.apache.org/jira/browse/ATLAS-1300
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8-incubating
>
>
> The current v1 Lineage API (LineageResource) needs to route to the new v2 
> Lineage API (LineageREST).
> 1. Inputs Graph
> 2. Outputs Graph



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

[jira] [Updated] (ATLAS-1304) Code cleanup and simplification

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1304:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/1620284e

> Code cleanup and simplification
> ---
>
> Key: ATLAS-1304
> URL: https://issues.apache.org/jira/browse/ATLAS-1304
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1304.patch
>
>
> This change addresses the following problems
> 1. Lot of redundant code across modules.
> 2. Simplification of boolean expressions
> 3. Embrace JDK7 style (instead of List aList = new ArrayList(); it 
> should be List aList = new ArrayList<>();)
> 4. Unnecessary typecasts



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

[jira] [Updated] (ATLAS-1312) Update QuickStart to use the new APIs for type and entities creation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1312:

Fix Version/s: 0.8-incubating

> Update QuickStart to use the new APIs for type and entities creation
> 
>
> Key: ATLAS-1312
> URL: https://issues.apache.org/jira/browse/ATLAS-1312
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1312.4.patch
>
>
> The quick start currently uses old APIs to create types and entities. This 
> needs to be updated to use the v2 APIs for types and entities.



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

[jira] [Updated] (ATLAS-1322) Coverity Scan 154409 : Fix dereference null return value for RestUtils

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1322:

Fix Version/s: 0.8-incubating

> Coverity Scan 154409 : Fix dereference null return value for RestUtils
> --
>
> Key: ATLAS-1322
> URL: https://issues.apache.org/jira/browse/ATLAS-1322
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1322.1.patch
>
>
> fix the null dereference bug reported by coverity scan:
> To view the defects in Coverity Scan visit, 
> https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V05UPxvVjWch-2Bd2MGckcRZSbhom32dlDl11LWEm9nX1nbwG-2F526MSwix34kV0EOH7g-2BScYg5Neu8mhD8p0GzKU-3D_EjiwCo132RrzFIz-2FJoE3HNlDqdxVVd-2FAbDB7-2F-2BPiDibeKq-2FZ0zwEtKDTCgNnrTmmQQIyMSmLZSp1NcXNYVJ6Wr-2FdO9p0XeCf9kRUEsIWCXLYhpHJ3nY-2BpGOr4WzKI-2BY8H5YYgxlXfJsYHaUEj-2B2VdUC7fl8zedXRCD171EH8RMvSYozLDHCwaU0hF4CWI0JT1cS0q3K3Z2udDOuRmldmidG0Rfsuujk5ZkLatbRn6-2Fg-3D



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

[jira] [Updated] (ATLAS-1336) Storm Hook IT fails due to non registry of type storm_topology

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1336:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/3d212311

> Storm Hook IT fails due to non registry of type storm_topology
> --
>
> Key: ATLAS-1336
> URL: https://issues.apache.org/jira/browse/ATLAS-1336
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1336-v2.patch, ATLAS-1336.patch
>
>
> Storm Hook IT is failing with the following error due to non registry of type 
> "storm_topology":
> org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown 
> datatype: storm_topology
> at 
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
> at 
> org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742)
> at 
> org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726)
> at 
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280)
> at 
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268)
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2016-11-28 12:30:52,628 WARN  - [NotificationHookConsumer thread-0:] ~ Error 
> handling messageMetadata service API CREATE_ENTITY failed with status 400 
> (Bad Request) Response Body 
> (org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown 
> datatype: storm_topology
> at 
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
> at 
> org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742)
> at 
> org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726)
> at 
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280)
> at 
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268)
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> ) (NotificationHookConsumer$HookConsumer:252)



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

[jira] [Updated] (ATLAS-1338) Fix SqoopHookIT failure

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1338:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/389ec561

> Fix SqoopHookIT failure
> ---
>
> Key: ATLAS-1338
> URL: https://issues.apache.org/jira/browse/ATLAS-1338
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ayub Pathan
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1338.patch
>
>
> SqoopHookIT fails with below error
> {noformat}
> org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown 
> datatype: sqoop_dbdatastore
> at 
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
> at 
> org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742)
> at 
> org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726)
> at 
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280)
> at 
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268)
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> 2016-11-28 20:27:30,108 WARN  - [NotificationHookConsumer thread-0:] ~ Error 
> handling messageMetadata service API CREATE_ENTITY failed with status 400 
> (Bad Request) Response Body 
> (org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown 
> datatype: sqoop_dbdatastore
> at 
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
> at 
> org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742)
> at 
> org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726)
> at 
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280)
> at 
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268)
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> ) (NotificationHookConsumer$HookConsumer:252)
> {noformat}



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

[jira] [Updated] (ATLAS-1337) FalconHookIT failure due to model registration failure.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1337:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/be9c2648

> FalconHookIT failure due to model registration failure.
> ---
>
> Key: ATLAS-1337
> URL: https://issues.apache.org/jira/browse/ATLAS-1337
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ayub Pathan
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1337.patch
>
>
> FalconHookIT failure due to model registration failure.
> {code}
> org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.AtlasBaseClient$APIInfo@5fac521d failed with status 400 (Bad 
> Request) Response Body ({"error":" Unknown datatype: 
> falcon_cluster","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
>  Unknown datatype: falcon_cluster\n\tat org.apache.atlas.typesyst 
> em.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat 
> org.apache.atlas.services.DefaultMetadataService.validateTypeExists(DefaultMetadataService.java:519)\n\tat
>  org.apa 
> che.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:319)\n\tat
>  org.apache.atlas.services.DefaultMetadataService.getEntityDefin 
> ition(DefaultMetadataService.java:327)\n\tat 
> org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:525)\n\tat
>  org.apache.atlas.web 
> .resources.EntityResource.getEntity(EntityResource.java:506)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.inv 
> oke(NativeMethodAccessorImpl.java:62)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Metho d.java:498)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  com.sun.jersey.server.impl.model.method.dispatch.Abs 
> tractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  com.sun.jersey.server.impl.model.method.dispatch.Reso 
> urceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  com.s 
> un.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.ja
>  va:147)\n\tat 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  com.sun.jersey.server.impl.application.WebApplicatio 
> nImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  com.sun 
> .jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest( 
> WebApplicationImpl.java:1409)\n\tat 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  com.sun.jersey.spi.container.servlet.ServletContai 
> ner.service(ServletContainer.java:558)\n\tat 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.se rvice(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
>  com.google.inject.servlet.ServletDefinition.doS 
> ervice(ServletDefinition.java:276)\n\tat 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
>  com.google.inject.servlet.ManagedServletPipeli 
> ne.service(ManagedServletPipeline.java:91)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.A 
> uditFilter.doFilter(AuditFilter.java:73)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  com.google.inject.servlet.Manage 
> dFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat 
> com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat 
> org.eclipse.jetty.servlet.ServletHa 
> ndler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>  org 
> 

[jira] [Updated] (ATLAS-1369) Optimize Gremlin created by DSL Translator

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1369:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/62a05c97

> Optimize Gremlin created by DSL Translator
> --
>
> Key: ATLAS-1369
> URL: https://issues.apache.org/jira/browse/ATLAS-1369
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: rb54680.patch
>
>
> The way the queries are generated now, in many cases the indices are not used 
> when executing queries.  The main problem is that gremlin cannot currently 
> use the graph indices to optimize the lookup for "has" expressions within an 
> "and" or an "or".  This JIRA introduces a GremlinQueryOptimizer that attempts 
> to extract "has" expressions out of "and" expressions and turn "or" 
> expressions into unions.
> The code being submitted has only been tested with TP 3 at this point.  There 
> are some issues that need to be fixed before this can be used with TP 2:
>   - GremlinQueryOptimizer is currently disabled when using TP 2.  The 
> condition in AtlasRepositoryConfiguration.isGremlinOptimizerEnabled needs to 
> be updated.
>   - FunctionGenerator - generates functions that take GraphTraversal as an 
> argument.  That should be changed to GreminPipeline when using TP 2.  The 
> return type should probably come from a new method in GremlinExpressionFactory
>- loop support - for TP2, we will need to add logic to make sure that the 
> loop call is not separated from the alias it references
>   - alias handling - the alias save/restore logic in 
> ExpandOrsOptimization.getBaseResultExpression() may be need to adjusted for 
> TP2
>   - possibly other issues, TBD



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

[jira] [Updated] (ATLAS-1385) Add configuration property to disable full text mapper

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1385:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/db18c824

> Add configuration property to disable full text mapper
> --
>
> Key: ATLAS-1385
> URL: https://issues.apache.org/jira/browse/ATLAS-1385
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: Wojciech Wojcik
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: rb56223.patch
>
>
> Add configuration property to disable full text mapper. Populating the full 
> text fields adds considerable overhead, and this allows applications to avoid 
> this overhead if they do not need full text search capability.



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

[jira] [Updated] (ATLAS-1386) Avoid unnecessary type lookups during query parsing

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1386:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/75bcccd1

> Avoid unnecessary type lookups during query parsing
> ---
>
> Key: ATLAS-1386
> URL: https://issues.apache.org/jira/browse/ATLAS-1386
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: rb55436.patch
>
>
> During query parsing, there are unnecessary types lookups happening. For 
> example, in the DSL query hive_table where name = \"bar-999\" select name, 
> name is parsed into an identifier, and it was doing a type lookup to see if a 
> trait or class called 'name' exists. In cases like this, the operands are 
> fields, not types, and so a type lookup is not necessary and arguably 
> incorrect. 



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

[jira] [Updated] (ATLAS-1388) Cache entities that are created/updated

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1388:

Fix Version/s: 0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/09089e09

> Cache entities that are created/updated
> ---
>
> Key: ATLAS-1388
> URL: https://issues.apache.org/jira/browse/ATLAS-1388
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
>Priority: Major
> Fix For: 0.8-incubating
>
>
> - Cache created entities in RequestContext when they are created.
> - Update/refactor DefaultMetadataService.loadEntities() to use the cached 
> created entities.
> - Use the cache in the following places:
> ** FullTextMapper
> ** DefaultMetadataService.onEntitiesAdded - check cache before calling 
> DefaultMetadataService.loadEntities
> ** DefaultMetadataService.onEntitiesUpdated - check cache before calling 
> DefaultMetadataService.loadEntities 
> ** EntityResource.getEntityDefinition - check cache before calling 
> DefaultMetadataService.getEntityDefinition
> ** EntityResource.getResponse - check cache before calling 
> DefaultMetadataService.getEntityDefinition



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

[jira] [Updated] (ATLAS-1395) Lineage improvement for tooltip

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1395:

Fix Version/s: 0.8-incubating

> Lineage improvement for tooltip
> ---
>
> Key: ATLAS-1395
> URL: https://issues.apache.org/jira/browse/ATLAS-1395
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1395.1.patch, ATLAS-1395.patch
>
>
> This patch containes Lineage tooltip improvement.
> Format:
> {noFormat}
> 
> ||
> |   |
> |  |
> 
> {noFormat}
> Both name and typename will be center align inside tooltip



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

[jira] [Resolved] (ATLAS-1397) [V2 API] DELETE should return deleted type guid with proper message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1397.
-
Resolution: Not A Problem

> [V2 API] DELETE should return deleted type guid with proper message
> ---
>
> Key: ATLAS-1397
> URL: https://issues.apache.org/jira/browse/ATLAS-1397
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
>Priority: Major
>
> POST v2/types/enumdef
> {
> "name" : "creation_order1",
> "typeVersion" : "1.1",
> "elementDefs" : [
> { "ordinal" : 1, "value" : "PRE" }
> ,
> { "ordinal" : 2, "value" : "POST" }
> ,
> { "ordinal" : 3, "value" : "UNKNOWN" }
> ]
> }
> returns the response
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "description": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> { "value": "PRE", "ordinal": 1 }
> ,
> { "value": "POST", "ordinal": 2 }
> ,
> { "value": "UNKNOWN", "ordinal": 3 }
> ]
> }
> DELETE v2/types/enumdef/name/creation_order1 is successful but doesn't return 
> anything. DELETE request should return some response in the below format:
> {
> "result" : "SUCCESS/FAIL"
> "guid" : "{guid}"
> }



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

[jira] [Reopened] (ATLAS-1397) [V2 API] DELETE should return deleted type guid with proper message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reopened ATLAS-1397:
-

> [V2 API] DELETE should return deleted type guid with proper message
> ---
>
> Key: ATLAS-1397
> URL: https://issues.apache.org/jira/browse/ATLAS-1397
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
>Priority: Major
>
> POST v2/types/enumdef
> {
> "name" : "creation_order1",
> "typeVersion" : "1.1",
> "elementDefs" : [
> { "ordinal" : 1, "value" : "PRE" }
> ,
> { "ordinal" : 2, "value" : "POST" }
> ,
> { "ordinal" : 3, "value" : "UNKNOWN" }
> ]
> }
> returns the response
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "description": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> { "value": "PRE", "ordinal": 1 }
> ,
> { "value": "POST", "ordinal": 2 }
> ,
> { "value": "UNKNOWN", "ordinal": 3 }
> ]
> }
> DELETE v2/types/enumdef/name/creation_order1 is successful but doesn't return 
> anything. DELETE request should return some response in the below format:
> {
> "result" : "SUCCESS/FAIL"
> "guid" : "{guid}"
> }



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

[jira] [Updated] (ATLAS-1473) Create Entity via UI : Schema tab of an entity not updated after adding a column

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1473:

Fix Version/s: 0.8-incubating

> Create Entity via UI : Schema tab of an entity not updated after adding a 
> column
> 
>
> Key: ATLAS-1473
> URL: https://issues.apache.org/jira/browse/ATLAS-1473
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8-incubating
>
>
> Created a hive_column instance via Create Entity in UI . Added the column to 
> an entity. After adding, the schema tab doesn't show the added column. Reason 
> is that the schema call is not made after updating column. On refreshing the 
> page , added column is found in the schema tab.



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

[jira] [Updated] (ATLAS-1476) Create Entity via UI : Unable to add the same column again after deleting the column from the table

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1476:

Fix Version/s: 0.8-incubating

> Create Entity via UI : Unable to add the same column again after deleting the 
> column from the table
> ---
>
> Key: ATLAS-1476
> URL: https://issues.apache.org/jira/browse/ATLAS-1476
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
>
> 1.Created a hive_table test_table (created using Create Entity ) with column 
> column1(also created using Create Entity).
> 2.Clicked on edit button of the test_table and removed column1.
> 3.In schema tab of the hive_table, column1 is shown DELETED.
> 4.Created another hive_column column1 with same name and qualified name.
> 5.Tried to add the hive_column column1(newly created) to the test_table. 
> 'Edit Entity' window of test_table still has the deleted hive_column and not 
> able to add the new hive_column column1.
> This is possible with hive CLI :
> 1. create table table1(id int,name string)
> 2. alter table table1 replace columns(name string)  >>> id is DELETED
> 3. alter table table1 replace columns(id int,name string) >>> 2 ids are 
> present , one ACTIVE,one DELETED



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

[jira] [Updated] (ATLAS-1477) Create Entity via UI : Update button should be enabled only when any update is made to the entity.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1477:

Fix Version/s: 0.8-incubating

> Create Entity via UI : Update button should be enabled only when any update 
> is made to the entity.
> --
>
> Key: ATLAS-1477
> URL: https://issues.apache.org/jira/browse/ATLAS-1477
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8-incubating
>
>
> When editing an entity via UI , update button is enabled/clickable even 
> though no update is made to the entity. And Entity Audit also happens (could 
> see an extra entry in Audits tab) whenever update button is clicked inspite 
> of no entity update.



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

[jira] [Updated] (ATLAS-1485) Create entity UX changes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1485:

Fix Version/s: 0.8-incubating

> Create entity UX changes
> 
>
> Key: ATLAS-1485
> URL: https://issues.apache.org/jira/browse/ATLAS-1485
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Kalyani Kashikar
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1485.patch
>
>
> # Change the create entity button place
> # After creating new entity redirect to detail page of that newly created 
> entity



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

[jira] [Updated] (ATLAS-1487) Create Entity in UI : types list doesn't list fs_permissions (struct type) hence no entity could be created for it.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1487:

Fix Version/s: 0.8-incubating

> Create Entity in UI : types list doesn't list fs_permissions (struct type) 
> hence no entity could be created for it.
> ---
>
> Key: ATLAS-1487
> URL: https://issues.apache.org/jira/browse/ATLAS-1487
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1487.patch
>
>
> hdfs_path and fs_path have PosixPermissions as one of the (optional) 
> attributes  which is of type fs_permissions (struct) . When creating entity 
> in UI , the types list (/api/atlas/v2/types/entitydef) doesn't return 
> fs_permissions hence no entity could be created for it.   



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

[jira] [Updated] (ATLAS-1486) UI to Handle server side error for V2 API

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1486:

Fix Version/s: 0.8-incubating

> UI to Handle server side error for V2 API
> -
>
> Key: ATLAS-1486
> URL: https://issues.apache.org/jira/browse/ATLAS-1486
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1486.patch
>
>
> UI to handle error according to errorMessage attribute from server reponse 
> object



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

[jira] [Comment Edited] (ATLAS-1805) Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj edited comment on ATLAS-1805 at 5/17/18 3:26 PM:
--

commit link:
 - master: 
https://github.com/apache/atlas/commit/b05b855622166bf98ef6a18198ae94a9414bf21d
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/183e9239


was (Author: rmani):
commit link 
https://github.com/apache/atlas/commit/b05b855622166bf98ef6a18198ae94a9414bf21d

> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas
> ---
>
> Key: ATLAS-1805
> URL: https://issues.apache.org/jira/browse/ATLAS-1805
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names.patch, 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names_002.patch, 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names_003.patch
>
>
> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas



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

[jira] [Updated] (ATLAS-1805) Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1805:

Fix Version/s: 0.8.2
   1.0.0

> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas
> ---
>
> Key: ATLAS-1805
> URL: https://issues.apache.org/jira/browse/ATLAS-1805
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names.patch, 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names_002.patch, 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names_003.patch
>
>
> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas



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

[jira] [Updated] (ATLAS-1806) Error while redirecting it to Tag tab after doing advance search and creating entity

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1806:

Fix Version/s: 0.8.1
   1.0.0

> Error while redirecting it to Tag tab after doing advance search and creating 
> entity
> 
>
> Key: ATLAS-1806
> URL: https://issues.apache.org/jira/browse/ATLAS-1806
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: SS11.png
>
>
>  Steps to reproduce:-
> 1.Do an Advance Search
> 2.Then create an entity
> 3.Click on search tab
> 4.Now click on Tags Tab
> Error:- It would redirect back to Search Tab which is incorrect



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

[jira] [Updated] (ATLAS-1815) Exclude DELETED entities : Not all ACTIVE instances are returned when queried with limit 'n' even when more than 'n' ACTIVE instances are present.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1815:

Fix Version/s: 0.8.1
   1.0.0

> Exclude DELETED entities : Not all ACTIVE instances are returned when queried 
> with limit 'n' even when more than 'n' ACTIVE instances are present.
> --
>
> Key: ATLAS-1815
> URL: https://issues.apache.org/jira/browse/ATLAS-1815
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.8.1, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-1815.1.patch
>
>
> "excludeDeletedEntities" filter is made after the response is returned, which 
> produces unexpected results when limit keyword is used like in the following 
> case :
> 1.Started fresh instance of Atlas and created 50 hive_tables
> 2. Made a basic search query , type name = hive_table which returned 50 
> tables in 2 pages in UI.
> Query fired : 
> {code}
> /api/atlas/v2/search/basic?limit=25=true=hive_table
> {code}
> 3.Dropped the five tables which were shown as the first five results in the 
> first page of basic search query results.
> 4. Made the same basic query again (type name = hive_table) .
> 5.Expected that 25 ACTIVE results would come up in the first page of UI. But 
> only 20 results were displayed in the UI.
> 6. When "Include historical Entities" is checked , result table showed 20 
> ACTIVE tables and 5 DELETED tables.
> This happens because , probably when 
> "limit=25=true=hive_table" is fired ,
> first 25 results are returned (irrespective of ACTIVE or DELETED) and 
> excludeDeletedEntities=true filter is applied which results in only 20 
> results. User would expect 25 tables to be returned in the UI since there are 
> 45 ACTIVE tables but UI shows only 20 ACTIVE instances because of the 
> "excludeDeletedEntities=true" filter.



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

[jira] [Updated] (ATLAS-1832) If no attribute is present in tag then showing edit-button for a tag in tags tab on entity page.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1832:

Fix Version/s: 0.8.1
   1.0.0

> If no attribute is present in tag  then showing edit-button for a tag in tags 
> tab on entity page.
> -
>
> Key: ATLAS-1832
> URL: https://issues.apache.org/jira/browse/ATLAS-1832
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Chrome
>Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-1832.1.patch, ATLAS-1832.patch, edit attribute for 
> tag bug .png
>
>




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

[jira] [Updated] (ATLAS-1849) Atlas should prereq Java 8

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1849:

Fix Version/s: 1.0.0

> Atlas should prereq Java 8
> --
>
> Key: ATLAS-1849
> URL: https://issues.apache.org/jira/browse/ATLAS-1849
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
>
> Atlas should move to assume Java 8 in order to remain current
> Java 7's last official release was in April 2015
> Java 8 was released in March 2014 and is the current release
> Java 9 is currently targetted for release in July 2017
> Various new components we wish to integrate, such as Janus Graph now quite 
> sensibly depend on, and can take advantage of, Java 8. Whilst Atlas does 
> build cleanly under java 8, the new capabilities cannot be used and more 
> crucially any components requiring it can't be so easily integrated into the 
> source. With Java 7 way out of focus there are more likely to be security 
> exposures too.
> One of the current main environments Atlas is supported in is Hadoop. Hadoop 
> 2.x is build with Java 7, though the very latest releases do at least support 
> build with Java 8. Hadoop 3 which prereqs java 8 is due for release in August 
> 2017
> However other environments in the enterprise need not be constrained by this 
> dependency
> We need to decide how we will tackle this dependency change & mitigate the 
> impacts - for example
>  * we stay as-is until hadoop 3 is current/into 2018 (in my view too long)
>  * we go all out on java 8 in the current trunk, and branches are cut for 
> java 7 approach (I worry this is too much work to dual-fix)
>  * we create multiple build profiles and carefully allow java8 code in as 
> needed, but in such a way as a java7 version can still be built, albeit 
> missing out on selective functionality - this could still be tricky, and has 
> run-time dependency differences
>  * if profiles we decide on default (once working I'd suggest 8...)
> Thoughts welcome :-)



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

[jira] [Updated] (ATLAS-1856) Relationship instance API Java & REST implementation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1856:

Fix Version/s: 1.0.0

> Relationship instance API Java & REST implementation
> 
>
> Key: ATLAS-1856
> URL: https://issues.apache.org/jira/browse/ATLAS-1856
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: trunk, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1856.2.patch, curl_create_new_relationDef, 
> curl_create_new_relationInstance
>
>
> Based on the relationDef implementation in ATLAS-1852. Implement instance API 
> and REST for entity relationships



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

[jira] [Updated] (ATLAS-1872) Spring based bean ordering/configuration change

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1872:

Affects Version/s: (was: trunk)
Fix Version/s: 0.8.1
   1.0.0

Committed to following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/82b6f727
 - 0.8-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/46295b55

> Spring based bean ordering/configuration change
> ---
>
> Key: ATLAS-1872
> URL: https://issues.apache.org/jira/browse/ATLAS-1872
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: 
> 0001-ATLAS-1872-Spring-fix-for-Kerberos-and-bean-ordering.patch
>
>
> * In a kerberized environment Atlas fails to start as the LoginProcessor 
> doesn't perform login before bean creation
> * HBaseAuditRepository should be default instead of NoopEntityAuditRepository



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

[jira] [Updated] (ATLAS-1873) Rename AtlasRelationshipEndPoint to Rename AtlasRelationshipEnd

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1873:

Fix Version/s: 1.0.0
  Description: Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/1de6016d
  Component/s:  atlas-core

> Rename AtlasRelationshipEndPoint to Rename AtlasRelationshipEnd
> ---
>
> Key: ATLAS-1873
> URL: https://issues.apache.org/jira/browse/ATLAS-1873
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Fix For: 1.0.0
>
>
> Committed to master: 
> http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/1de6016d



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

[jira] [Updated] (ATLAS-1884) Mixed-mode and intelligent querying

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1884:

Fix Version/s: 0.8.1
   1.0.0

> Mixed-mode and intelligent querying
> ---
>
> Key: ATLAS-1884
> URL: https://issues.apache.org/jira/browse/ATLAS-1884
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>




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

[jira] [Updated] (ATLAS-1883) Gremlin search implementation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1883:

Fix Version/s: 0.8.1
   1.0.0

> Gremlin search implementation
> -
>
> Key: ATLAS-1883
> URL: https://issues.apache.org/jira/browse/ATLAS-1883
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>




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

[jira] [Updated] (ATLAS-1882) Solr (indexed) search implementation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1882:

Fix Version/s: 0.8.1
   1.0.0

> Solr (indexed) search implementation
> 
>
> Key: ATLAS-1882
> URL: https://issues.apache.org/jira/browse/ATLAS-1882
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>




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

[jira] [Updated] (ATLAS-1881) Request structure design

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1881:

Fix Version/s: 0.8.1
   1.0.0

> Request structure design
> 
>
> Key: ATLAS-1881
> URL: https://issues.apache.org/jira/browse/ATLAS-1881
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>




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

[jira] [Updated] (ATLAS-1888) UI - While Update Entity the data of type Long is not updating in entity from UI.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1888:

Fix Version/s: 0.8.1
   1.0.0

> UI - While Update Entity the data of type Long is not updating in entity from 
> UI.
> -
>
> Key: ATLAS-1888
> URL: https://issues.apache.org/jira/browse/ATLAS-1888
> Project: Atlas
>  Issue Type: Bug
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-1888.patch
>
>
> Step to reproduce :-
> * Search for the Table.
> * Go to sales_fact_monthly_mv, and update CreateTime, LastAccessTime
> * Click on update button
> * CreateTime and LastAccessTime are not updating properly.
>  



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

[jira] [Updated] (ATLAS-1313) Tests SSLAndKerberosTest.testService and SSLTest.testService are failing

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1313:

Fix Version/s: (was: trunk)
   0.8-incubating

> Tests SSLAndKerberosTest.testService and SSLTest.testService are failing 
> -
>
> Key: ATLAS-1313
> URL: https://issues.apache.org/jira/browse/ATLAS-1313
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Vimal Sharma
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1313.patch
>
>
> Tests SSLAndKerberosTest.testService and SSLTest.testService are failing with 
> the below trace
> testService(org.apache.atlas.web.security.SSLTest)  Time elapsed: 0.333 sec  
> <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.AtlasBaseClient$APIInfo@5d4ca7d9 failed with status 400 (Bad 
> Request) Response Body ({"error":"Given search filter did not yield any 
> results ","stackTrace":"java.lang.Exception: Given search filter did not 
> yield any results \n\tat 
> org.apache.atlas.web.resources.TypesResource.getTypesByFilter(TypesResource.java:289)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
>  com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
>  
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>  
> org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)\n\tat
>  
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
>  
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)\n\tat
>  
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)\n\tat
>  
> 

[jira] [Updated] (ATLAS-1315) Fix webapp Integration tests

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1315:

Fix Version/s: (was: trunk)
   0.8-incubating

> Fix webapp Integration tests
> 
>
> Key: ATLAS-1315
> URL: https://issues.apache.org/jira/browse/ATLAS-1315
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1315-v1.patch, ATLAS-1315.patch, Screen Shot 
> 2016-11-22 at 9.02.53 AM.png, Screen Shot 2016-11-22 at 9.03.51 AM.png, 
> Screen Shot 2016-11-22 at 9.05.41 AM.png, Screen Shot 2016-11-22 at 9.11.55 
> AM.png
>
>
> webapp tests are failing. Below are the failing tests
>   EntityNotificationIT.testCreateEntity:90 NullPointer
>   EntityNotificationIT.testDeleteEntity:119 NullPointer
>   EntityJerseyResourceIT.testEntityDeduping:233 » AtlasService Metadata 
> service ...
> org.apache.atlas.web.resources.EntityJerseyResourceIT.testEntityInvalidValue(org.apache.atlas.web.resources.EntityJerseyResourceIT)
>   Run 1: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected 
> AtlasServiceException
>   Run 2: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected 
> AtlasServiceException
>   EntityJerseyResourceIT.testSubmitEntity:128 NullPointer
>   EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:323 Was expecting 
> an  exception here 
>   EntityJerseyResourceIT.testUTF8:754 NullPointer
>   EntityLineageJerseyResourceIT.testInputLineageInfo:74 expected:<200> but 
> was:<404>
>   EntityLineageJerseyResourceIT.testLineageInfo:134 expected:<200> but 
> was:<404>
>   EntityLineageJerseyResourceIT.testOutputLineageInfo:104 expected:<200> but 
> was:<404>
>   MetadataDiscoveryJerseyResourceIT.testSearchByDSL:76 expected:<200> but 
> was:<400>
>   MetadataDiscoveryJerseyResourceIT.testSearchDSLLimits:108 expected:<200> 
> but was:<400>
>   MetadataDiscoveryJerseyResourceIT.testSearchUsingDSL:196 expected: but 
> was:
>   TypedefsJerseyResourceIT.testCreate:86 » AtlasService Metadata service API 
> org...
>   TypedefsJerseyResourceIT.testDuplicateCreate:98 » AtlasService Metadata 
> servic...
>   TypedefsJerseyResourceIT.testListTypesByFilter:254 » AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:118 » AtlasService Metadata service API 
> or...



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

[jira] [Updated] (ATLAS-1316) V2 API webapp tests are failing

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1316:

Fix Version/s: (was: trunk)
   0.8-incubating

> V2 API webapp tests are failing
> ---
>
> Key: ATLAS-1316
> URL: https://issues.apache.org/jira/browse/ATLAS-1316
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Pathan
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1316-v1.patch, ATLAS-1316.patch, application.log, 
> org.apache.atlas.web.resources.TypedefsJerseyResourceIT-output.txt, 
> org.apache.atlas.web.resources.TypedefsJerseyResourceIT.txt
>
>
> {noformat}
> Failed tests:
>   EntityLineageJerseyResourceIT.testInputLineageInfo:74 expected:<200> but 
> was:<404>
>   EntityLineageJerseyResourceIT.testLineageInfo:134 expected:<200> but 
> was:<404>
>   EntityLineageJerseyResourceIT.testOutputLineageInfo:104 expected:<200> but 
> was:<404>
>   TypedefsJerseyResourceIT.testCreate:86 » AtlasService Metadata service API 
> org...
>   TypedefsJerseyResourceIT.testDuplicateCreate:98 » AtlasService Metadata 
> servic...
>   TypedefsJerseyResourceIT.testListTypesByFilter:254 » AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:118 » AtlasService Metadata service API 
> or...
> {noformat}
> *From high level this seems like AtlasAuthorizationUtils.java is not handling 
> V2 API's properly*



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

[jira] [Updated] (ATLAS-1321) Fix failure of Hive ITs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1321:

Fix Version/s: (was: trunk)
   0.8-incubating

> Fix failure of Hive ITs
> ---
>
> Key: ATLAS-1321
> URL: https://issues.apache.org/jira/browse/ATLAS-1321
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Vimal Sharma
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1321-v2.patch, ATLAS-1321-v3.patch, 
> ATLAS-1321-v4.patch, ATLAS-1321-v5.patch, ATLAS-1321-v6.patch, 
> ATLAS-1321.patch
>
>
> Hive ITs fail because the Atlas TypeDef initializer cannot locate models 
> directory. None of the types defined in hive-model.json are regsitered.
> Below is the stack trace:
> Caused by: org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.AtlasBaseClient$APIInfo@6398e143 failed with status 400 (Bad 
> Request) Response Body ({"error":"Unknown datatype: 
> hive_db","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
>  Unknown datatype: hive_db\n\tat 
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.validateTypeExists(DefaultMetadataService.java:519)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:327)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:525)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:506)\n\tat
>  sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:73)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
>  com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
>  
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>  
> 

[jira] [Updated] (ATLAS-1324) Fix SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider UT failure

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1324:

Fix Version/s: (was: trunk)
   0.8-incubating

> Fix SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider UT 
> failure
> ---
>
> Key: ATLAS-1324
> URL: https://issues.apache.org/jira/browse/ATLAS-1324
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Pathan
>Assignee: Ayub Pathan
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1324.patch
>
>
> {noformat}
> testServerConfiguredUsingCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
>   Time elapsed: 16.378 sec  <<< FAILURE!
> java.lang.AssertionError: War deploy failed
>   at org.testng.Assert.fail(Assert.java:89)
>   at org.testng.Assert.failNotEquals(Assert.java:489)
>   at org.testng.Assert.assertEquals(Assert.java:118)
>   at org.testng.Assert.assertEquals(Assert.java:365)
>   at org.testng.Assert.assertEquals(Assert.java:375)
>   at 
> org.apache.atlas.web.service.SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider(SecureEmbeddedServerTest.java:76)
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0
> Running org.apache.atlas.web.service.ServiceStateTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.484 sec - 
> in org.apache.atlas.web.service.ServiceStateTest
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0
> Running org.apache.atlas.web.setup.SetupStepsTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.66 sec - in 
> org.apache.atlas.web.setup.SetupStepsTest
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0
> Running org.apache.atlas.web.TestUtils
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.149 sec - 
> in org.apache.atlas.web.TestUtils
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0
> Running org.apache.atlas.web.util.ServletsTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.417 sec - 
> in org.apache.atlas.web.util.ServletsTest
> Results :
> Failed tests:
>   SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider:78 War 
> deploy failed
> Tests run: 107, Failures: 1, Errors: 0, Skipped: 0
> {noformat}



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

[jira] [Updated] (ATLAS-1340) Credential Provider utility does not work with fully qualified local/HDFS jceks path

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1340:

Fix Version/s: (was: trunk)
   0.8-incubating

> Credential Provider utility does not work with fully qualified local/HDFS 
> jceks path
> 
>
> Key: ATLAS-1340
> URL: https://issues.apache.org/jira/browse/ATLAS-1340
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Vipin Rathor
>Priority: Minor
>  Labels: patch, security
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1340-v2.patch, fix-hdfs-credProvider.patch
>
>
> At present the Atlas Credential Provider utility (./bin/cputil.py) does not 
> work with credential provider path like 
> jceks://file/local/file/path/file.jceks or 
> jceks://hdfs@namenodehost:port/path/in/hdfs/to/file.jceks as mentioned in 
> documentation page at http://atlas.apache.org/Security.html (section: 
> Credential Provider Utility Script)
> Current Behavior:
> cputil.py always creates a credential provider file in local file system at 
> root directory as follows:
> 1. For the input "jceks://file/local/file/path/file.jceks",
> file created => /jceks:/file/local/file/path/file.jceks
> 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks",
> file created => /jceks:/h...@namenode.com:8020/path/in/hdfs/to/file.jceks on 
> local file system
> Expected Behavior:
> 1. For the input "jceks://file/local/file/path/file.jceks",
> file created should be /local/file/path/file.jceks
> 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks",
> file created should be /path/in/hdfs/to/file.jceks on the specified HDFS file 
> system.
> Steps to re-create:
> 1. Run ./bin/cputil.py and provide fully qualified path to jceks file as 
> described above.
> Attached is a patch to fix this issue. Tested with both local and HDFS jceks 
> credential provider path.



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

[jira] [Updated] (ATLAS-1889) Failure in simultaneous updates to an entity tag association

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1889:

Fix Version/s: (was: trunk)

> Failure in simultaneous updates to an entity tag association
> 
>
> Key: ATLAS-1889
> URL: https://issues.apache.org/jira/browse/ATLAS-1889
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.1
>
> Attachments: ATLAS-1889-Handling-multiple-entities.patch
>
>
> *Background*
> When multiple requests simultaneously attempt to change the tags associated 
> with an entity, the current implementation might result in APIs returning 
> fewer tags for the entity than is actually associated.
> The problem thus causes UI not to behave correctly.
>  
> *Solution*
> Implements a synchronization mechanism.
>  
> Steps to duplicate the problem:
> * Create several tags. Eg. tag1, tag2, tag3, tag4.
> * Attach these tags to and entity say ‘testtable1’
> * Use the following CURL commands to delete the tags:
> {code}
> curl -X DELETE -u admin:admin 
> 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag1'
>   -H 'Content-Type: application/json' &
> curl -X DELETE -u admin:admin 
> 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag2'
>   -H 'Content-Type: application/json' &
> curl -X DELETE -u admin:admin 
> 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag3'
>   -H 'Content-Type: application/json' &
> curl -X DELETE -u admin:admin 
> 'http://localhost:21000/api/atlas/entities/a2d0b023-aafe-4ddd-bb90-65164af8796c/traits/tag4'
>   -H 'Content-Type: application/json'
> {code}
> You will notice that entity _testtable1_ ends up with some tags not deleted.
> Additional querying with gremlin will show that the edges are deleted 
> correctly.



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

[jira] [Updated] (ATLAS-1804) Allow PAM for authentication

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1804:

Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)

> Allow PAM for authentication
> 
>
> Key: ATLAS-1804
> URL: https://issues.apache.org/jira/browse/ATLAS-1804
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Shi Wang
>Assignee: Shi Wang
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: 0001-ATLAS-1804.patch, ATLAS-1804.3.patch
>
>
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type. 



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

[jira] [Updated] (ATLAS-1834) TestNG asserts across tests instead on JUnit

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1834:

Fix Version/s: (was: trunk)

> TestNG asserts across tests instead on JUnit
> 
>
> Key: ATLAS-1834
> URL: https://issues.apache.org/jira/browse/ATLAS-1834
> Project: Atlas
>  Issue Type: Bug
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1
>
> Attachments: 
> 0002-ATLAS-1834-TestNG-asserts-over-JUnit-for-consistency.patch
>
>
> Most of our tests use TestNG Asserts, only a handful of them are using JUnit. 
> As a side-effect the builds on apache jenkins are failing because of the 
> incorrect JUnit version getting picked from m2 repository, this causing 
> certain tests to fail in-deterministically.
> Changing all imports to TestNG



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

[jira] [Updated] (ATLAS-1198) Move from Guice + Spring to only Spring

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1198:

Affects Version/s: (was: 1.0.0)
   0.8-incubating
Fix Version/s: (was: trunk)
   1.0.0

> Move from Guice + Spring to only Spring
> ---
>
> Key: ATLAS-1198
> URL: https://issues.apache.org/jira/browse/ATLAS-1198
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: 
> 0001-ATLAS-1198-Spring-Framework-v4-with-Spring-security-.patch
>
>
> Right now we're using both Guice and Spring and dependency injection which is 
> not a ideal combination. As Atlas evolves as a product we can leverage the 
> spring framework to avoid re-inventing the wheel like caching, transaction 
> management etc.



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

[jira] [Updated] (ATLAS-636) Tags/Traits associated with partitionkeys should be retained after rename table.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-636:
---
Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)
   0.7-incubating

> Tags/Traits associated with partitionkeys should be retained after rename 
> table.
> 
>
> Key: ATLAS-636
> URL: https://issues.apache.org/jira/browse/ATLAS-636
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ayub Pathan
>Assignee: Suma Shivaprasad
>Priority: Major
> Fix For: 0.7-incubating
>
>
> Partition keys tag/trait association is lost when a table is renamed.
> Hive table entity has tags associated to partition keys..
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/entities/b70c53b1-e6a1-4811-9cfd-5d1aa52a353f'
>  -H 'Accept: application/json, text/plain, */*' -H 'Referer: 
> http://localhost:21000/' -H 'Cache-Control: no-cache' --compressed | python 
> -m json.tool
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  33550  33550 0   103k  0 --:--:-- --:--:-- --:--:--  105k
> {
> "GUID": "b70c53b1-e6a1-4811-9cfd-5d1aa52a353f",
> "definition": {
> "id": {
> "id": "b70c53b1-e6a1-4811-9cfd-5d1aa52a353f",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "typeName": "hive_table",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_table",
> "values": {
> "columns": [
> {
> "id": {
> "id": "6600947f-c9d0-4158-82d1-54406401df46",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "typeName": "hive_column",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_column",
> "values": {
> "comment": null,
> "name": "s",
> "qualifiedName": "d2.p2.s@primary",
> "type": "string"
> }
> }
> ],
> "comment": null,
> "createTime": 1459845523,
> "db": {
> "id": "9a2c114d-dbb9-41c6-86bf-fbdb52f93ef2",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "typeName": "hive_db",
> "version": 0
> },
> "description": null,
> "lastAccessTime": 0,
> "name": "d2.p2@primary",
> "owner": "apathan",
> "parameters": {
> "last_modified_by": "apathan",
> "last_modified_time": "1459845523",
> "transient_lastDdlTime": "1459845523"
> },
> "partitionKeys": [
> {
> "id": {
> "id": "726fa937-8131-4d48-8c21-ce0ebed965ca",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "typeName": "hive_column",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [
> "DataProducer"
> ],
> "traits": {
> "DataProducer": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "DataProducer",
> "values": {}
> }
> },
> "typeName": "hive_column",
> "values": {
> "comment": null,
> "name": "month",
> "qualifiedName": "d2.p2.month@primary",
> "type": "int"
> }
> },
> {
> "id": {
> "id": "83e0c544-1e06-48bf-865d-d2ce09084943",
> "jsonClass": 
> 

[jira] [Updated] (ATLAS-468) Add automatic patch validation script for Apache ATLAS using preCommit-ATLAS-build

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-468:
---
Fix Version/s: (was: trunk)

> Add automatic patch validation script for Apache ATLAS using 
> preCommit-ATLAS-build
> --
>
> Key: ATLAS-468
> URL: https://issues.apache.org/jira/browse/ATLAS-468
> Project: Atlas
>  Issue Type: Task
>Reporter: Selvamohan Neethiraj
>Assignee: Selvamohan Neethiraj
>Priority: Major
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-468-added-automatic-patch-validation-scripts.patch
>
>
> These script will allow automatic validation of (submitted) patches. 
> This is standard apache process to automatically validate and provide the 
> feedback in the JIRA - using preCommit-ATLAS-build jenkin job (yet to be 
> setup!).



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

[jira] [Updated] (ATLAS-424) UI: The UI Should not expose guids

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-424:
---
Fix Version/s: (was: trunk)
   0.7-incubating

> UI: The UI Should not expose guids
> --
>
> Key: ATLAS-424
> URL: https://issues.apache.org/jira/browse/ATLAS-424
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
>Priority: Major
> Fix For: 0.7-incubating
>
>
> In the cases where guids are displayed in the UI, we should change to display 
> something meaningful to users. In the cases where the REST API does not 
> support or provide the name, Jiras should be filed to enhance the API as 
> necessary.



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

[jira] [Updated] (ATLAS-394) Fix BaseResourceIT.waitForNotification()

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-394:
---
Fix Version/s: (was: trunk)

> Fix BaseResourceIT.waitForNotification()
> 
>
> Key: ATLAS-394
> URL: https://issues.apache.org/jira/browse/ATLAS-394
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Major
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-394-v2.patch, ATLAS-394-v3.patch, 
> ATLAS-394-v4.patch, ATLAS-394.patch
>
>
> EntityNotificationConsumer sets entityNotification to the last read 
> notification waitForNotification returns with the last read notification 
> which may not be the expected one.  waitForNotification() should accept a 
> predicate instead



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

[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-385:
---
Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)

> Support for Lineage for entities with SuperType as DataSet 
> ---
>
> Key: ATLAS-385
> URL: https://issues.apache.org/jira/browse/ATLAS-385
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Rishabh Bhardwaj
>Assignee: Anilsg
>Priority: Major
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-385-v1.patch, ATLAS-385-v2.patch, 
> ATLAS-385-v3.patch, ATLAS-385.patch, feed_enhancements.txt, lineage.png, 
> sample_graph_api_output.txt
>
>
> Currently from the trunk code,the lineage only comes to type "Table" while 
> previously It used to come when `superType` is "DataSet" for the entities.
> Due to this change now lineage only comes for the entities of type "Table" 
> and not for custom entities with superType 'DataSet'.
> Can we get this support for DataSet back ?
> Or is there any workaround for the same ? 



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

[jira] [Updated] (ATLAS-395) UI : In details page maps not displayed for different data models

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-395:
---
Fix Version/s: (was: trunk)

> UI : In details page maps not displayed for different data models
> -
>
> Key: ATLAS-395
> URL: https://issues.apache.org/jira/browse/ATLAS-395
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
>Priority: Major
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-395-v1.patch, ATLAS-395.patch
>
>
> The response for scope data model
> commandlineOpts : key,value
> {  
>"requestId":"qtp1879648991-116 - 95121c27-1bdd-43e8-8f32-1c087038e88a",
>"GUID":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>"definition":{  
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{  
>  
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>  "id":"f9aef3cb-f243-4b91-9c19-d1086aaadfc4",
>  "version":0,
>  "typeName":"sqoop_process"
>   },
>   "typeName":"sqoop_process",
>   "values":{  
>  "name":"sqoop_mysql_localhost_2181_sqoop_table_12434343",
>  "startTime":1450342252394,
>  "description":null,
>  "outputs":[  
> {  
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"a8d2846e-8854-47f2-9d24-16a4655f7f49",
>"version":0,
>"typeName":"DataSet"
> }
>  ],
>  "commandlineOpts":{  
> "option2":"value2",
> "option1":"value1",
> "option4":"value4",
> "option3":"value3"
>  },
>  "endTime":1450342262394,
>  "inputs":[  
> {  
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>"id":"7f1149b0-12c0-401f-9543-c2de18fb6b8e",
>"version":0,
>"typeName":"DataSet"
> }
>  ],
>  "operation":"select",
>  "userName":"sqoop_admin"
>   },
>   "traitNames":[  
>   ],
>   "traits":{  
>   }
>}
> }



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

[jira] [Updated] (ATLAS-402) UI : Validation of Associating a Tag

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-402:
---
Fix Version/s: (was: trunk)

> UI : Validation of Associating a Tag   
> ---
>
> Key: ATLAS-402
> URL: https://issues.apache.org/jira/browse/ATLAS-402
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
>Priority: Major
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-401-ATLAS-402-v0.patch, ATLAS-402-v1.patch, 
> ATLAS-402.patch
>
>
> Tag association  - no confirmation when linking it to an asset.  I click save 
> the second time and I get an error saying its already there… so I know it 
> works but we should confirm or close the window



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

[jira] [Updated] (ATLAS-405) UI: Lineage is broken seemingly if there are more than one input Processes creating a Dataset

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-405:
---
Fix Version/s: (was: trunk)

> UI: Lineage is broken seemingly if there are more than one input Processes 
> creating a Dataset
> -
>
> Key: ATLAS-405
> URL: https://issues.apache.org/jira/browse/ATLAS-405
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Darshan Kumar
>Priority: Blocker
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-405-v0.patch, ATLAS-405.patch, 
> failing_lineage.png, failing_lineage_api_responses.txt, 
> failing_lineage_entity_responses.txt, lineage_view_issue.png, 
> spikedMockData.png, working_lineage.png, working_lineage_api_responses.txt
>
>
> I have a slightly complex lineage which is like this:
> [DataSet 1] -> (3 processes) -> [DataSet 2] -> (1 process) -> [DataSet 3]
> When I click on DataSet1, the lineage graph is showing correctly.
> When I click on DataSet2, the lineage graph is broken. What is happening is 
> that there are 2 dangling processes on the input side of DataSet 2 which are 
> not linked to the DataSet 1. Only one of the processes seems linked. It 
> appears that maybe the graph walking is not taking into effect multiple 
> inputs to a vertex like DataSet 2.
> The API response is right. I will upload images of working and failing 
> lineages with the corresponding responses in follow-up comments.



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

[jira] [Updated] (ATLAS-382) Fixed Hive Bridge doc for ATLAS cluster name

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-382:
---
Fix Version/s: (was: trunk)

> Fixed Hive Bridge doc for ATLAS cluster name
> 
>
> Key: ATLAS-382
> URL: https://issues.apache.org/jira/browse/ATLAS-382
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating, trunk
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Major
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-382.patch
>
>
> ---++ Importing Hive Metadata
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge imports the hive metadata 
> into Atlas using the model defined in 
> org.apache.atlas.hive.model.HiveDataModelGenerator. import-hive.sh command 
> can be used to facilitate this.
> Set the following configuration in /client.properties and set 
> environment variable HIVE_CONFIG to the hive conf directory:
>   
> 
>   atlas.cluster.name
>   primary
> 
>   
> THis should instead mention $HIVE_CONFIG/hive-site.xml instead of 
> client.properties



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

[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-376:
---
Fix Version/s: (was: trunk)

> UI: Use the Schema API of the backend to populate details for Schema tab
> 
>
> Key: ATLAS-376
> URL: https://issues.apache.org/jira/browse/ATLAS-376
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Hemanth Yamijala
>Assignee: Darshan Kumar
>Priority: Major
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-376-ATLAS-314-v1.patch, 
> ATLAS-376-ATLAS-314-v2.patch, ATLAS-376-ATLAS-314.patch, schema_response.json
>
>
> Currently, the information that comes in the schema tab seems to be populated 
> from the entity information that is fired to get the details of the entity. 
> In the API, we have a specific API to get schema of any dataset. This API 
> should be used to populate the schema tab instead of using information from 
> the entity information.
> Specifically:
> * Use the entity API, something of the form /lineage/hive/table/$name$/schema 
> where $name$ is the name attribute of the entity in question. For e.g. for 
> hive_tables an example URL would be 
> /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where 
> default.tbl16@primary is the name.
> * The results of the API should be parsed to populate the details of the 
> Schema table. (Will attach a sample response, and expand more details on this 
> point in the comments).
> * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. 
> Hive columns), it should put up the 'Add tag' action and should allow the 
> user to associate a tag to that entity. In addition, it should put up the 
> list of available tags currently associated with the entity. (Note this 
> functionality is similar to how the search results are handled for 
> reference-able entities)
> * The API could return a 404 if the name does not exist, or the name is 
> something that does not represent a dataset. This should be handled, and upon 
> receipt should not display the Schema tab at all.



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

[jira] [Updated] (ATLAS-374) Doc: Create a wiki for documenting fault tolerance and HA options for Atlas data

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-374:
---
Fix Version/s: (was: trunk)

> Doc: Create a wiki for documenting fault tolerance and HA options for Atlas 
> data
> 
>
> Key: ATLAS-374
> URL: https://issues.apache.org/jira/browse/ATLAS-374
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Major
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-374.patch, ATLAS-374.patch, ATLAS-374.patch, 
> ATLAS-374.patch
>
>
> With switching to HBase and Solr as backends for Atlas's datastore, it is now 
> possible to have a high level of fault tolerance and availability guarantees 
> for Atlas data. This JIRA is to enhance the documentation to have a guide for 
> setting up Atlas in a fault tolerant and available mode.



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

[jira] [Updated] (ATLAS-246) QuickStart uses integer data type for dates, which causes data loss

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-246:
---
Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)

> QuickStart uses integer data type for dates, which causes data loss
> ---
>
> Key: ATLAS-246
> URL: https://issues.apache.org/jira/browse/ATLAS-246
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: David Kantor
>Assignee: David Kantor
>Priority: Minor
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-246-v0.patch
>
>
> The QuickStart program uses DataTypes.INT_TYPE when defining datetime 
> attributes on the DB, Table, and LoadProcess types.  This causes data loss 
> when Java long integer date values (such as what is returned by 
> System.currentTimeMillis()) are converted to integers, and an incorrect value 
> is stored when entities of these types are created in the repository.  
> DataTypes.LONG_TYPE should be used to avoid the data loss.



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

[jira] [Updated] (ATLAS-249) Seach based on classType and Trait returns 0 rows

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-249:
---
Fix Version/s: (was: trunk)
   0.6-incubating

> Seach based on classType and Trait returns 0 rows
> -
>
> Key: ATLAS-249
> URL: https://issues.apache.org/jira/browse/ATLAS-249
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Herman Yu
>Priority: Major
> Fix For: 0.6-incubating
>
>
> DSL query: hive_table is  returns 0 rows, even though at least 
> one  hive_table entity is associated with 



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

[jira] [Updated] (ATLAS-244) UI: Add Tag Tab

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-244:
---
Fix Version/s: (was: trunk)

> UI: Add Tag Tab
> ---
>
> Key: ATLAS-244
> URL: https://issues.apache.org/jira/browse/ATLAS-244
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Major
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-244-v1.patch
>
>
> The detailed entity screen needs to add a Tag tab. See: 
> https://monosnap.com/file/en3YL2ARN111d9UDlCozZpBnUhkPwv for additional 
> details.



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

[jira] [Updated] (ATLAS-342) Atlas is sending an ENTITY_CREATE event to the ATLAS_ENTITIES topic even if the entity exists already.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-342:
---
Fix Version/s: (was: trunk)
   0.6-incubating

> Atlas is sending an ENTITY_CREATE event to the ATLAS_ENTITIES topic even if 
> the entity exists already.
> --
>
> Key: ATLAS-342
> URL: https://issues.apache.org/jira/browse/ATLAS-342
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
>Priority: Major
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-342.patch
>
>
> * Configure Hive hook in Hive.
> * Configure Atlas to talk to Kafka topics on a separately set Kafka instance.
> * Run a script to create tables in Hive multiple times, for e.g.
> {code}
> for i in `seq 1 10`; do ./bin/hive -e "create table tbl$i (column${i}1 
> string, column${i}2 int)"; done
> {code}
> * After the script completes, check the number of entities & list the actual 
> entities in the ATLAS_ENTITIES topic.
> We can see one ENTITY_CREATE event for the Hive database for every table 
> created in Hive. For e.g.: 
> {code}
> {"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"e7ed4ad9-1fba-47ad-a089-1ff7e715c1ad","version":0,"typeName":"hive_db"},"typeName":"hive_db","values":{"name":"default","description":"Default
>  Hive 
> database","ownerType":{"value":"ROLE","ordinal":2},"qualifiedName":"primary.default","locationUri":"hdfs://localhost:9000/user/hive/warehouse","ownerName":"public","clusterName":"primary"},"traitNames":[],"traits":{}},"operationType":"ENTITY_CREATE","traits":[]}
> {"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"e7ed4ad9-1fba-47ad-a089-1ff7e715c1ad","version":0,"typeName":"hive_db"},"typeName":"hive_db","values":{"name":"default","description":"Default
>  Hive 
> database","ownerType":{"value":"ROLE","ordinal":2},"qualifiedName":"primary.default","locationUri":"hdfs://localhost:9000/user/hive/warehouse","ownerName":"public","clusterName":"primary"},"traitNames":[],"traits":{}},"operationType":"ENTITY_CREATE","traits":[]}
> {code}
> The expectation is that we don't have these extraneous events as there is no 
> change to the entity.



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

[jira] [Updated] (ATLAS-213) UI: When searching for Tag/Trait, Search results show guid instead of name

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-213:
---
Fix Version/s: (was: trunk)
   0.6-incubating

> UI: When searching for Tag/Trait, Search results show guid instead of name
> --
>
> Key: ATLAS-213
> URL: https://issues.apache.org/jira/browse/ATLAS-213
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
>Priority: Major
> Fix For: 0.6-incubating
>
>
> UI: When searching for Tag/Trait, Search results show guid instead of name.
> See: https://monosnap.com/file/m9857DlVtUWCwkAbRQ3kcOZla6pdaa



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

[jira] [Updated] (ATLAS-209) Use testng and delete junit and scalatest

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-209:
---
Fix Version/s: (was: trunk)

> Use testng and delete junit and scalatest
> -
>
> Key: ATLAS-209
> URL: https://issues.apache.org/jira/browse/ATLAS-209
> Project: Atlas
>  Issue Type: Improvement
>Reporter: liutongfeng
>Assignee: liutongfeng
>Priority: Major
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-209.v1.patch
>
>
> Currently, maven-surefire-plugin using both testng and junit, the tests will 
> be run twice, resulting in wrong test results report.
> Now, this issue will delete junit and scalatest, only use testng.



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

[jira] [Updated] (ATLAS-346) Atlas server loses messages sent from Hive hook if restarted after unclean shutdown

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-346:
---
Fix Version/s: (was: trunk)

> Atlas server loses messages sent from Hive hook if restarted after unclean 
> shutdown
> ---
>
> Key: ATLAS-346
> URL: https://issues.apache.org/jira/browse/ATLAS-346
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-346.patch, ATLAS-346.patch, ATLAS-346.patch, 
> hive_server2_import_bug_snip.txt
>
>
> * Start Atlas server pointed to an external Kafka instance
> * Configure HiveServer2 with Atlas hook pointing to the same Kafka instance.
> * Run a hive DDL script like 
> {code}
> for i in `seq 1 25`; do ./bin/beeline -u jdbc:hive2://localhost:1 -n 
> ${user} -p ${pass} -e "create table tbl${i} (col${i}1 int, col${i}2 
> string);"; done
> {code}
> * While the script is executing, kill -9 the Atlas server
> * Let the script complete.
> * Verify that all the events are added to the ATLAS_HOOK topic.
> * Verify if the tables are added to Atlas.
> The observation is that the Kafka topic has all relevant messages, but the 
> tables aren't added to Atlas.



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

[jira] [Updated] (ATLAS-334) Update documentation to reflect copying required atlas file on solr installation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-334:
---
Fix Version/s: (was: trunk)

> Update documentation to reflect copying required atlas file on solr 
> installation
> 
>
> Key: ATLAS-334
> URL: https://issues.apache.org/jira/browse/ATLAS-334
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Major
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-334.patch
>
>
> Currently, if solr is installed on a different machine other than Atlas the 
> instructions to run the command to create solr vertices may not be valid.
> The instructions currently mentions
> Run the following commands from SOLR_HOME directory to create collections in 
> Solr corresponding to the indexes that Atlas uses
> bin/solr create -c vertex_index -d ATLAS_HOME/conf/solr -shards #numShards 
> -replicationFactor #replicationFactor
> bin/solr create -c edge_index -d ATLAS_HOME/conf/solr -shards #numShards 
> -replicationFactor #replicationFactor
> bin/solr create -c fulltext_index -d ATLAS_HOME/conf/solr -shards #numShards 
> -replicationFactor #replicationFactor
> We will have to update this with required files that required to be copied 
> over to the solr server .



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

Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas

[Bogdan Sava]

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

(Updated May 17, 2018, 2:56 p.m.)


Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy 
Chessell, and Ruxandra Rosu.


Repository: atlas


Description
---

Create configuration for OMAG API in Atlas


Diffs (updated)
-

  om-fwk-ocf/pom.xml 8b1cefd 
  omag-api/pom.xml 2338286 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java
 dd19018 
  omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java 
PRE-CREATION 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java
 PRE-CREATION 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java
 ebc9f2a 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java
 PRE-CREATION 
  
omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java
 1a15215 
  
omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java
 c2950c4 
  omag-server/pom.xml 527c5c3 
  
omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java
 88397de 
  omag-server/src/main/resources/application.properties PRE-CREATION 
  omas-assetconsumer/pom.xml 29935e7 
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java
 80a98f5 
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java
  
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java
 967be5a 
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java
 PRE-CREATION 
  omas-connectedasset/README.md 2f431df 
  omas-connectedasset/pom.xml 219c972 
  
omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java
 8ae6c37 
  
omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java
 PRE-CREATION 
  omrs/pom.xml 50b9898 
  omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java 
7ae87c6 
  
omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java
 5948482 
  
omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java
 PRE-CREATION 
  
omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
 3f85317 
  
omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java
 ccf0de6 
  webapp/pom.xml 03b8408 
  webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 
  webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION 
  webapp/src/main/webapp/WEB-INF/web.xml 23dc063 


Diff: https://reviews.apache.org/r/67083/diff/6/

Changes: https://reviews.apache.org/r/67083/diff/5-6/


Testing
---

Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.


Change base URL for the API to "/open-metadata/access-services" 


Clean maven unused dependenies

The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665


File Attachments


Added apache licence to a properties file
  
https://reviews.apache.org/media/uploaded/files/2018/05/11/77fbc4f6-b16a-42f9-983c-261f70f3ca9f__0002-ATLAS-2665-Added-apache-licence-to-properties-file.patch
0003-ATLAS-2665-comments-fixed.patch
  
https://reviews.apache.org/media/uploaded/files/2018/05/11/004f018b-1ee5-4da1-91d4-b50f4913298d__0003-ATLAS-2665-comments-fixed.patch
ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch
  
https://reviews.apache.org/media/uploaded/files/2018/05/14/160f8499-661d-4fa9-8ce1-afe4bd88b723__ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch


Thanks,

Bogdan Sava

[jira] [Updated] (ATLAS-2665) Add OMAG-API in Atlas

[Bogdan Sava (JIRA)]

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

Bogdan Sava updated ATLAS-2665:
---
Attachment: ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch

> Add OMAG-API in Atlas
> -
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



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

Re: Review Request 66949: ATLAS-2523: changes to accept external GUIDs and manage homeIds

[Madhan Neethiraj]

> On May 16, 2018, 4:37 p.m., Madhan Neethiraj wrote:
> > intg/src/main/java/org/apache/atlas/model/instance/AtlasEntity.java
> > Lines 77 (patched)
> > 
> >
> > Shouldn't homeId be added to AtlasObjectId as well? Please review and 
> > update.
> 
> Graham Wallis wrote:
> I'm not sure - the GUID is still globally unique provides a means to 
> uniquely identify an entity or relationship. The homeId is additional 
> context, but it's not clear to me that it would be required in a reference to 
> an entity or relationship. The purpose of homeId is to enable the enterprise 
> OMRS to determine whether an object originated from (is 'owned' by) Atlas or 
> is something a copy stored in Atlas, of an object that originated in a 
> different repository. The enterprise OMRS uses that information for routing, 
> etc. 
> I am happy to add homeId to AtlasObjectId (and maybe 
> AtlasRelatedObjectId) if you still think it should be there.

If you don't see the need for 'homeId' in AtlasObjectId (and AtlasEntityHeader 
- which is returned in search results), the current patch is good to go.

Please rebase the patch for current master and commit.

Thanks!


- Madhan


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


On May 10, 2018, 2:52 p.m., Graham Wallis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66949/
> ---
> 
> (Updated May 10, 2018, 2:52 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2523: Changes to accept external GUIDs and manage homeIds
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/repository/Constants.java 3732556ae 
>   intg/src/main/java/org/apache/atlas/model/instance/AtlasEntity.java 
> 7f36a10f5 
>   intg/src/main/java/org/apache/atlas/model/instance/AtlasRelationship.java 
> d04daa5d2 
>   intg/src/main/java/org/apache/atlas/type/AtlasTypeUtil.java 6c0fdbf36 
>   repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
> 78ab206d3 
>   repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
> 7490a15b1 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1.java
>  9fcba6dda 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
>  cd00639de 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphRetriever.java
>  183a2f6c0 
> 
> 
> Diff: https://reviews.apache.org/r/66949/diff/3/
> 
> 
> Testing
> ---
> 
> Functional testing of these changes to save reference copies of entities and 
> relationships
> 
> 
> Thanks,
> 
> Graham Wallis
> 
>

Re: Review Request 66949: ATLAS-2523: changes to accept external GUIDs and manage homeIds

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On May 10, 2018, 2:52 p.m., Graham Wallis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66949/
> ---
> 
> (Updated May 10, 2018, 2:52 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2523: Changes to accept external GUIDs and manage homeIds
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/repository/Constants.java 3732556ae 
>   intg/src/main/java/org/apache/atlas/model/instance/AtlasEntity.java 
> 7f36a10f5 
>   intg/src/main/java/org/apache/atlas/model/instance/AtlasRelationship.java 
> d04daa5d2 
>   intg/src/main/java/org/apache/atlas/type/AtlasTypeUtil.java 6c0fdbf36 
>   repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
> 78ab206d3 
>   repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
> 7490a15b1 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1.java
>  9fcba6dda 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
>  cd00639de 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphRetriever.java
>  183a2f6c0 
> 
> 
> Diff: https://reviews.apache.org/r/66949/diff/3/
> 
> 
> Testing
> ---
> 
> Functional testing of these changes to save reference copies of entities and 
> relationships
> 
> 
> Thanks,
> 
> Graham Wallis
> 
>

Re: Review Request 66064: ATLAS-2478 Elasticsearch support broken with JanusGraph 0.2.0

[Pierre Padovani]

> On May 16, 2018, 6:11 p.m., Madhan Neethiraj wrote:
> > docs/src/site/twiki/Configuration.twiki
> > Lines 47 (patched)
> > 
> >
> > Per earlier discussions, support for Elasticsearch will be tech-preview 
> > for Atlas 1.0.0 release. Please update the documentation to reflect this.
> > 
> > Does Elasticsearch support kerberos authentication? If yes, have you 
> > validated Atlas working with Elasticsearch in kerberized environment?

I updated the application properties to reflect the answers to the above. It 
does not support kerberos out of the box. There is a plugin that provides 
security from the company that makes Elasticsearch, and I referenced it as well 
as the recommended method for securing elasticsearch in the JanusGraph 
ducomentation.


- Pierre


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


On May 17, 2018, 2:39 p.m., Pierre Padovani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66064/
> ---
> 
> (Updated May 17, 2018, 2:39 p.m.)
> 
> 
> Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2478
> https://issues.apache.org/jira/browse/ATLAS-2478
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch fixes the Elasticsearch support for JanusGraph 0.2.0 and updates 
> documentation.
> 
> Included with this patch is an update to the berkley-elasticsearch profile to 
> automatically download and include elasticsearch as a side application much 
> like solr is. Updates to the start/stop/conf scripts are included as well.
> 
> NOTE: This patch includes a **BACKWARDS INCOMPATIBLE** change to 
> /atlas/common/src/main/java/org/apache/atlas/repository/Constants.java. There 
> are six constants that are incorrectly named with a '.' (dot). This is not 
> supported in Elasticsearch 5 and beyond when defining a mapping **UNLESS** 
> the field names can be collectively thought of as an object. In the case of 
> the fields defined in the Constants.java file, 'type' is defined as a string 
> field, and 'type.name' is also defined as a string field. Elasticsearch sees 
> this as an error, since it cannot convert type to an object. The fix included 
> simply changes the field names from using a '.' (dot) to an '_' (underscore). 
> This should NOT affect compatibility with hbase/solr for new installs. For 
> existing installations, a reindex will be required as the field names will 
> have changed.
> 
> **Query**: There is a way we can simplify integration/unit tests for the 
> in-memory graph store by using a maven plugin that will download and run an 
> elasticsearch node. This is nothing more than a maven change, and change to 
> the atlas-application.properties to switch to elasticsearch from solr. I did 
> not implement this, but am curious if this change would be desired. If so, 
> this can be done with a separate ticket.
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/repository/Constants.java 3732556ae 
>   distro/pom.xml 379ff0d39 
>   distro/src/bin/atlas_config.py 9062da649 
>   distro/src/bin/atlas_start.py 61d69eb21 
>   distro/src/bin/atlas_stop.py 94c3d6d46 
>   distro/src/conf/atlas-env.sh 053cbd500 
>   distro/src/main/assemblies/standalone-package.xml dc88add56 
>   docs/src/site/twiki/Configuration.twiki 63c3fce96 
>   docs/src/site/twiki/HighAvailability.twiki 4270d0974 
>   docs/src/site/twiki/InstallationSteps.twiki dca0618e3 
>   graphdb/janus/pom.xml 016a09c33 
>   pom.xml 3469a393a 
>   webapp/pom.xml 03b84087f 
> 
> 
> Diff: https://reviews.apache.org/r/66064/diff/6/
> 
> 
> Testing
> ---
> 
> We currently use this fix with our Atlas setup in a fork of the Atlas code, 
> and have found no issues with it. Additionally, with the update to the 
> berkley-elasticsearch profile, I have extensively tested that profile to make 
> sure that management of Elasticsearch functioned correctly.
> 
> 
> Thanks,
> 
> Pierre Padovani
> 
>

Re: Review Request 66064: ATLAS-2478 Elasticsearch support broken with JanusGraph 0.2.0

[Pierre Padovani]

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

(Updated May 17, 2018, 2:39 p.m.)


Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
Subramanian.


Changes
---

Updated the comments in the application properties for configuring 
elasticsearch: Indicated tech preview, and security options


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


Repository: atlas


Description
---

This patch fixes the Elasticsearch support for JanusGraph 0.2.0 and updates 
documentation.

Included with this patch is an update to the berkley-elasticsearch profile to 
automatically download and include elasticsearch as a side application much 
like solr is. Updates to the start/stop/conf scripts are included as well.

NOTE: This patch includes a **BACKWARDS INCOMPATIBLE** change to 
/atlas/common/src/main/java/org/apache/atlas/repository/Constants.java. There 
are six constants that are incorrectly named with a '.' (dot). This is not 
supported in Elasticsearch 5 and beyond when defining a mapping **UNLESS** the 
field names can be collectively thought of as an object. In the case of the 
fields defined in the Constants.java file, 'type' is defined as a string field, 
and 'type.name' is also defined as a string field. Elasticsearch sees this as 
an error, since it cannot convert type to an object. The fix included simply 
changes the field names from using a '.' (dot) to an '_' (underscore). This 
should NOT affect compatibility with hbase/solr for new installs. For existing 
installations, a reindex will be required as the field names will have changed.

**Query**: There is a way we can simplify integration/unit tests for the 
in-memory graph store by using a maven plugin that will download and run an 
elasticsearch node. This is nothing more than a maven change, and change to the 
atlas-application.properties to switch to elasticsearch from solr. I did not 
implement this, but am curious if this change would be desired. If so, this can 
be done with a separate ticket.


Diffs (updated)
-

  common/src/main/java/org/apache/atlas/repository/Constants.java 3732556ae 
  distro/pom.xml 379ff0d39 
  distro/src/bin/atlas_config.py 9062da649 
  distro/src/bin/atlas_start.py 61d69eb21 
  distro/src/bin/atlas_stop.py 94c3d6d46 
  distro/src/conf/atlas-env.sh 053cbd500 
  distro/src/main/assemblies/standalone-package.xml dc88add56 
  docs/src/site/twiki/Configuration.twiki 63c3fce96 
  docs/src/site/twiki/HighAvailability.twiki 4270d0974 
  docs/src/site/twiki/InstallationSteps.twiki dca0618e3 
  graphdb/janus/pom.xml 016a09c33 
  pom.xml 3469a393a 
  webapp/pom.xml 03b84087f 


Diff: https://reviews.apache.org/r/66064/diff/6/

Changes: https://reviews.apache.org/r/66064/diff/5-6/


Testing
---

We currently use this fix with our Atlas setup in a fork of the Atlas code, and 
have found no issues with it. Additionally, with the update to the 
berkley-elasticsearch profile, I have extensively tested that profile to make 
sure that management of Elasticsearch functioned correctly.


Thanks,

Pierre Padovani

Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas

[David Radley]

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




omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java
Line 55 (original), 55 (patched)


This should be plural to be consistent with access-services. there are a 
few otehr instances of this in the patch



omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java
Line 291 (original), 291 (patched)


this is not what the code does. For this example wouldn't the code would 
produce urls starting with. 


ocalhost:8080/open-metadata/localServerName/open-metadata/repository-service/



omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java
Line 306 (original), 306 (patched)


should be repository-services to be consistant



omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java
Line 202 (original), 201 (patched)


Are we missing the /users/ before the {userId} in the path? The same for 
the rest of this file.



omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java
Lines 84 (patched)


plural for consistancy ?



webapp/src/main/webapp/WEB-INF/openMetadataContext.xml
Lines 3 (patched)


Bad end of line character on this and the next 6 lines


- David Radley


On May 17, 2018, 12:10 p.m., Bogdan Sava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67083/
> ---
> 
> (Updated May 17, 2018, 12:10 p.m.)
> 
> 
> Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy 
> Chessell, and Ruxandra Rosu.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Create configuration for OMAG API in Atlas
> 
> 
> Diffs
> -
> 
>   om-fwk-ocf/pom.xml 8b1cefd 
>   omag-api/pom.xml 2338286 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java
>  dd19018 
>   omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java 
> PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java
>  ebc9f2a 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java
>  1a15215 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java
>  c2950c4 
>   omag-server/pom.xml 527c5c3 
>   
> omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java
>  88397de 
>   omag-server/src/main/resources/application.properties PRE-CREATION 
>   omas-assetconsumer/pom.xml 29935e7 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java
>  80a98f5 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java
>   
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java
>  967be5a 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java
>  PRE-CREATION 
>   omas-connectedasset/README.md 2f431df 
>   omas-connectedasset/pom.xml 219c972 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java
>  8ae6c37 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java
>  PRE-CREATION 
>   omrs/pom.xml 50b9898 
>   
> omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java 
> 7ae87c6 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java
>  5948482 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java
>  PRE-CREATION 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
>  3f85317 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java
>  ccf0de6 
>   webapp/pom.xml 03b8408 
>   webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 
>   webapp/src/main/webapp/WEB-INF/openMetadataContext.xml 

Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas

[Bogdan Sava]

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

(Updated May 17, 2018, 12:10 p.m.)


Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy 
Chessell, and Ruxandra Rosu.


Repository: atlas


Description
---

Create configuration for OMAG API in Atlas


Diffs (updated)
-

  om-fwk-ocf/pom.xml 8b1cefd 
  omag-api/pom.xml 2338286 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java
 dd19018 
  omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java 
PRE-CREATION 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java
 PRE-CREATION 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java
 ebc9f2a 
  
omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java
 PRE-CREATION 
  
omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java
 1a15215 
  
omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java
 c2950c4 
  omag-server/pom.xml 527c5c3 
  
omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java
 88397de 
  omag-server/src/main/resources/application.properties PRE-CREATION 
  omas-assetconsumer/pom.xml 29935e7 
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java
 80a98f5 
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java
  
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java
 967be5a 
  
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java
 PRE-CREATION 
  omas-connectedasset/README.md 2f431df 
  omas-connectedasset/pom.xml 219c972 
  
omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java
 8ae6c37 
  
omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java
 PRE-CREATION 
  omrs/pom.xml 50b9898 
  omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java 
7ae87c6 
  
omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java
 5948482 
  
omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java
 PRE-CREATION 
  
omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
 3f85317 
  
omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java
 ccf0de6 
  webapp/pom.xml 03b8408 
  webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 
  webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION 
  webapp/src/main/webapp/WEB-INF/web.xml 23dc063 


Diff: https://reviews.apache.org/r/67083/diff/5/

Changes: https://reviews.apache.org/r/67083/diff/4-5/


Testing
---

Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.


Change base URL for the API to "/open-metadata/access-services" 


Clean maven unused dependenies

The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665


File Attachments


Added apache licence to a properties file
  
https://reviews.apache.org/media/uploaded/files/2018/05/11/77fbc4f6-b16a-42f9-983c-261f70f3ca9f__0002-ATLAS-2665-Added-apache-licence-to-properties-file.patch
0003-ATLAS-2665-comments-fixed.patch
  
https://reviews.apache.org/media/uploaded/files/2018/05/11/004f018b-1ee5-4da1-91d4-b50f4913298d__0003-ATLAS-2665-comments-fixed.patch
ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch
  
https://reviews.apache.org/media/uploaded/files/2018/05/14/160f8499-661d-4fa9-8ce1-afe4bd88b723__ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch


Thanks,

Bogdan Sava

Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas

[Bogdan Sava]

> On May 11, 2018, 10:34 a.m., David Radley wrote:
> > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java
> > Line 291 (original), 291 (patched)
> > 
> >
> > I thought we were talking of
> > for omrs use /open-metadata/repository-services 
> > for omas use  /open-metadata/access-services 
> > for admin use /open-metadata/admin 
> > 
> > 
> > I think these would often be followd by userId and local servername.
> > 
> > In this example is metadatacollection an instance of 
> > repository-services?
> 
> David Radley wrote:
> I am not sure why this issue has been closed - the urls do not match waht 
> I would expect.

those are examlples


- Bogdan


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


On May 16, 2018, 3:49 p.m., Bogdan Sava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67083/
> ---
> 
> (Updated May 16, 2018, 3:49 p.m.)
> 
> 
> Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy 
> Chessell, and Ruxandra Rosu.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Create configuration for OMAG API in Atlas
> 
> 
> Diffs
> -
> 
>   om-fwk-ocf/pom.xml 8b1cefd 
>   omag-api/pom.xml 2338286 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java
>  dd19018 
>   omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java 
> PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java
>  ebc9f2a 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java
>  1a15215 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java
>  c2950c4 
>   omag-server/pom.xml 527c5c3 
>   
> omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java
>  88397de 
>   omag-server/src/main/resources/application.properties PRE-CREATION 
>   omas-assetconsumer/pom.xml 29935e7 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java
>  80a98f5 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java
>   
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java
>  967be5a 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java
>  PRE-CREATION 
>   omas-connectedasset/README.md 2f431df 
>   omas-connectedasset/pom.xml 219c972 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java
>  8ae6c37 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java
>  PRE-CREATION 
>   omrs/pom.xml 50b9898 
>   
> omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java 
> 7ae87c6 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java
>  5948482 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java
>  PRE-CREATION 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
>  3f85317 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java
>  ccf0de6 
>   webapp/pom.xml 03b8408 
>   webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 
>   webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION 
>   webapp/src/main/webapp/WEB-INF/web.xml 23dc063 
> 
> 
> Diff: https://reviews.apache.org/r/67083/diff/4/
> 
> 
> Testing
> ---
> 
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> 
> 
> Change base URL for the API to "/open-metadata/access-services" 
> 
> 
> Clean maven unused dependenies
> 
> The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665
> 
> 
> File Attachments
> 
> 
> Added apache licence to a properties file
>   
> https://reviews.apache.org/media/uploaded/files/2018/05/11/77fbc4f6-b16a-42f9-983c-261f70f3ca9f__0002-ATLAS-2665-Added-apache-licence-to-properties-file.patch
> 0003-ATLAS-2665-comments-fixed.patch
>   
> 

Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas

[Bogdan Sava]

> On May 11, 2018, 10:05 a.m., David Radley wrote:
> > omag-server/src/main/resources/application.properties
> > Lines 1 (patched)
> > 
> >
> > This file causes the Atlas build to fail with a rat check. I am not 
> > sure why we have a comment with the same content as the line below. I 
> > suggest a meaningful comment might help in stead here.

commented one is for spring-boot 2.0.*, while the active one is for 
spring-boot-1.5.7

I'll add the apache licence to the file


- Bogdan


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


On May 16, 2018, 3:49 p.m., Bogdan Sava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67083/
> ---
> 
> (Updated May 16, 2018, 3:49 p.m.)
> 
> 
> Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy 
> Chessell, and Ruxandra Rosu.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Create configuration for OMAG API in Atlas
> 
> 
> Diffs
> -
> 
>   om-fwk-ocf/pom.xml 8b1cefd 
>   omag-api/pom.xml 2338286 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java
>  dd19018 
>   omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java 
> PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java
>  ebc9f2a 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java
>  1a15215 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java
>  c2950c4 
>   omag-server/pom.xml 527c5c3 
>   
> omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java
>  88397de 
>   omag-server/src/main/resources/application.properties PRE-CREATION 
>   omas-assetconsumer/pom.xml 29935e7 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java
>  80a98f5 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java
>   
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java
>  967be5a 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java
>  PRE-CREATION 
>   omas-connectedasset/README.md 2f431df 
>   omas-connectedasset/pom.xml 219c972 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java
>  8ae6c37 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java
>  PRE-CREATION 
>   omrs/pom.xml 50b9898 
>   
> omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java 
> 7ae87c6 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java
>  5948482 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java
>  PRE-CREATION 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
>  3f85317 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java
>  ccf0de6 
>   webapp/pom.xml 03b8408 
>   webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 
>   webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION 
>   webapp/src/main/webapp/WEB-INF/web.xml 23dc063 
> 
> 
> Diff: https://reviews.apache.org/r/67083/diff/4/
> 
> 
> Testing
> ---
> 
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> 
> 
> Change base URL for the API to "/open-metadata/access-services" 
> 
> 
> Clean maven unused dependenies
> 
> The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665
> 
> 
> File Attachments
> 
> 
> Added apache licence to a properties file
>   
> https://reviews.apache.org/media/uploaded/files/2018/05/11/77fbc4f6-b16a-42f9-983c-261f70f3ca9f__0002-ATLAS-2665-Added-apache-licence-to-properties-file.patch
> 0003-ATLAS-2665-comments-fixed.patch
>   
> https://reviews.apache.org/media/uploaded/files/2018/05/11/004f018b-1ee5-4da1-91d4-b50f4913298d__0003-ATLAS-2665-comments-fixed.patch
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch
>   
> 

[jira] [Updated] (ATLAS-2665) Add OMAG-API in Atlas

[Bogdan Sava (JIRA)]

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

Bogdan Sava updated ATLAS-2665:
---
Attachment: ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch

> Add OMAG-API in Atlas
> -
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



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