[jira] [Commented] (ATLAS-491) Business Catalog / Taxonomy

[John Speidel (JIRA)]

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

John Speidel commented on ATLAS-491:


I have been unable to upload the patch to the jira but the latest patch is 
available at review board.


> Business Catalog / Taxonomy
> ---
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search 
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use 
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy

[John Speidel (JIRA)]

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

John Speidel updated ATLAS-491:
---
Attachment: (was: test.txt)

> Business Catalog / Taxonomy
> ---
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search 
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use 
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy

[John Speidel (JIRA)]

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

John Speidel updated ATLAS-491:
---
Attachment: test.txt

> Business Catalog / Taxonomy
> ---
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch, test.txt
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search 
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use 
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-491) Business Catalog / Taxonomy

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-491:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12803980/ATLAS-491.patch
  against master revision 9e1f366.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 17 new 
or modified test files.

  {color:red}-1 javac{color}.  The applied patch generated 130 javac 
compiler warnings (more than the master's current 120 warnings).

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 379 new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 2 
release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Javac warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/238//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/238//console

This message is automatically generated.

> Business Catalog / Taxonomy
> ---
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search 
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use 
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog ent

Review Request 47382: ATLAS-491 : Business Catalog API

[John Speidel]

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

Review request for atlas and Hemanth Yamijala.


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


Repository: atlas


Description
---

Initial implementation of Catalog API.

Known Issues/Limitations:
- No update/delete support for taxonomies/terms
  -- this will be added next week
- Some gaps in test coverage
  - Need more in-depth test coverage that exercise the generated gremlin 
pipeline
- some refactoring should still be done espcecially in the 'query' package
- need to add more logging
- need to finish some javadoc


Diffs
-

  catalog/pom.xml PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/AtlasTypeSystem.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/BaseRequest.java PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/BaseResourceProvider.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/CollectionRequest.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/DefaultDateFormatter.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/DefaultPropertyMapper.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/DefaultTypeSystem.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/EntityResourceProvider.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/EntityTagResourceProvider.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/InstanceRequest.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/JsonSerializer.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/PropertyMapper.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/PropertyValueFormatter.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/Request.java PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/ResourceComparator.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/ResourceProvider.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/Result.java PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/TaxonomyResourceProvider.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/TermPath.java PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/TermResourceProvider.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/TermVertexWrapper.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/VertexWrapper.java 
PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/BaseResourceDefinition.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/EntityResourceDefinition.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/EntityTagResourceDefinition.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/ResourceDefinition.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/TaxonomyResourceDefinition.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/TermResourceDefinition.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/exception/CatalogException.java 
PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/exception/CatalogRuntimeException.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/exception/InvalidPayloadException.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/exception/InvalidQueryException.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/exception/ResourceAlreadyExistsException.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/exception/ResourceNotFoundException.java
 PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/projection/GenericRelation.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/projection/Projection.java 
PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/projection/ProjectionResult.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/projection/Relation.java 
PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/projection/RelationProjection.java
 PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/projection/RelationSet.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/projection/TagRelation.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/projection/TraitRelation.java 
PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/query/AlwaysQueryExpression.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityQuery.java 
PRE-CREATION 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityTagQuery.java 
PRE-C

[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy

[John Speidel (JIRA)]

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

John Speidel updated ATLAS-491:
---
Attachment: (was: ATLAS-491.patch)

> Business Catalog / Taxonomy
> ---
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search 
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use 
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy

[John Speidel (JIRA)]

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

John Speidel updated ATLAS-491:
---
Attachment: ATLAS-491.patch

> Business Catalog / Taxonomy
> ---
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch, 
> ATLAS-491.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search 
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use 
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy

[John Speidel (JIRA)]

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

John Speidel updated ATLAS-491:
---
Attachment: (was: business-catalog-WIP.patch)

> Business Catalog / Taxonomy
> ---
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search 
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use 
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-786) Close - Invalid

[Jo Desmet (JIRA)]

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

Jo Desmet updated ATLAS-786:

Description: (was: On a filesystem that is about to fill up, execute 
"hdfs dfs -put" for a file that is big enough to go over the limit. As a 
result, the command fails with an exception, however the command terminates 
normally (exit code 0).

Expectation is that any detectable failure generates an exit code different 
than zero.

Documentation on 
https://hadoop.apache.org/docs/r1.2.1/file_system_shell.html#put states:
Exit Code:

Returns 0 on success and -1 on error. 

following is the exception generated: 
16/05/11 13:37:07 INFO hdfs.DFSClient: Exception in createBlockOutputStream
java.io.EOFException: Premature EOF: no length prefix available
at 
org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed(PBHelper.java:2282)
at 
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1352)
at 
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1271)
at 
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:464)
16/05/11 13:37:07 INFO hdfs.DFSClient: Abandoning 
BP-1964113808-130.8.138.99-1446787670498:blk_1073835906_95114
16/05/11 13:37:08 INFO hdfs.DFSClient: Excluding datanode 
DatanodeInfoWithStorage[130.8.138.99:50010,DS-eed7039a-8031-499e-85a5-7216b9d766a8,DISK]
)
Summary: Close - Invalid  (was: hdfs dfs -put exits with zero on 
exception)

> Close - Invalid
> ---
>
> Key: ATLAS-786
> URL: https://issues.apache.org/jira/browse/ATLAS-786
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jo Desmet
>  Labels: exception-handling, hdfs, put
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-786) Close - Invalid

[Jo Desmet (JIRA)]

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

Jo Desmet resolved ATLAS-786.
-
Resolution: Invalid

> Close - Invalid
> ---
>
> Key: ATLAS-786
> URL: https://issues.apache.org/jira/browse/ATLAS-786
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jo Desmet
>  Labels: exception-handling, hdfs, put
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-787) Close

[Jo Desmet (JIRA)]

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

Jo Desmet resolved ATLAS-787.
-
Resolution: Invalid

> Close
> -
>
> Key: ATLAS-787
> URL: https://issues.apache.org/jira/browse/ATLAS-787
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jo Desmet
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-787) hdfs dfs -put exits with zero on error

[Jo Desmet (JIRA)]

Jo Desmet created ATLAS-787:
---

 Summary: hdfs dfs -put exits with zero on error
 Key: ATLAS-787
 URL: https://issues.apache.org/jira/browse/ATLAS-787
 Project: Atlas
  Issue Type: Bug
Reporter: Jo Desmet






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-787) Close

[Jo Desmet (JIRA)]

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

Jo Desmet updated ATLAS-787:

Summary: Close  (was: hdfs dfs -put exits with zero on error)

> Close
> -
>
> Key: ATLAS-787
> URL: https://issues.apache.org/jira/browse/ATLAS-787
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jo Desmet
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-786) hdfs dfs -put exits with zero on exception

[Jo Desmet (JIRA)]

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

Jo Desmet updated ATLAS-786:

Labels: exception-handling hdfs put  (was: )

> hdfs dfs -put exits with zero on exception
> --
>
> Key: ATLAS-786
> URL: https://issues.apache.org/jira/browse/ATLAS-786
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jo Desmet
>  Labels: exception-handling, hdfs, put
>
> On a filesystem that is about to fill up, execute "hdfs dfs -put" for a file 
> that is big enough to go over the limit. As a result, the command fails with 
> an exception, however the command terminates normally (exit code 0).
> Expectation is that any detectable failure generates an exit code different 
> than zero.
> Documentation on 
> https://hadoop.apache.org/docs/r1.2.1/file_system_shell.html#put states:
> Exit Code:
> Returns 0 on success and -1 on error. 
> following is the exception generated: 
> 16/05/11 13:37:07 INFO hdfs.DFSClient: Exception in createBlockOutputStream
> java.io.EOFException: Premature EOF: no length prefix available
> at 
> org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed(PBHelper.java:2282)
> at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1352)
> at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1271)
> at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:464)
> 16/05/11 13:37:07 INFO hdfs.DFSClient: Abandoning 
> BP-1964113808-130.8.138.99-1446787670498:blk_1073835906_95114
> 16/05/11 13:37:08 INFO hdfs.DFSClient: Excluding datanode 
> DatanodeInfoWithStorage[130.8.138.99:50010,DS-eed7039a-8031-499e-85a5-7216b9d766a8,DISK]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-786) hdfs dfs -put exits with zero on exception

[Jo Desmet (JIRA)]

Jo Desmet created ATLAS-786:
---

 Summary: hdfs dfs -put exits with zero on exception
 Key: ATLAS-786
 URL: https://issues.apache.org/jira/browse/ATLAS-786
 Project: Atlas
  Issue Type: Bug
Reporter: Jo Desmet






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-786) hdfs dfs -put exits with zero on exception

[Jo Desmet (JIRA)]

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

Jo Desmet updated ATLAS-786:

Description: 
On a filesystem that is about to fill up, execute "hdfs dfs -put" for a file 
that is big enough to go over the limit. As a result, the command fails with an 
exception, however the command terminates normally (exit code 0).

Expectation is that any detectable failure generates an exit code different 
than zero.

Documentation on 
https://hadoop.apache.org/docs/r1.2.1/file_system_shell.html#put states:
Exit Code:

Returns 0 on success and -1 on error. 

following is the exception generated: 
16/05/11 13:37:07 INFO hdfs.DFSClient: Exception in createBlockOutputStream
java.io.EOFException: Premature EOF: no length prefix available
at 
org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed(PBHelper.java:2282)
at 
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1352)
at 
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1271)
at 
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:464)
16/05/11 13:37:07 INFO hdfs.DFSClient: Abandoning 
BP-1964113808-130.8.138.99-1446787670498:blk_1073835906_95114
16/05/11 13:37:08 INFO hdfs.DFSClient: Excluding datanode 
DatanodeInfoWithStorage[130.8.138.99:50010,DS-eed7039a-8031-499e-85a5-7216b9d766a8,DISK]


> hdfs dfs -put exits with zero on exception
> --
>
> Key: ATLAS-786
> URL: https://issues.apache.org/jira/browse/ATLAS-786
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jo Desmet
>
> On a filesystem that is about to fill up, execute "hdfs dfs -put" for a file 
> that is big enough to go over the limit. As a result, the command fails with 
> an exception, however the command terminates normally (exit code 0).
> Expectation is that any detectable failure generates an exit code different 
> than zero.
> Documentation on 
> https://hadoop.apache.org/docs/r1.2.1/file_system_shell.html#put states:
> Exit Code:
> Returns 0 on success and -1 on error. 
> following is the exception generated: 
> 16/05/11 13:37:07 INFO hdfs.DFSClient: Exception in createBlockOutputStream
> java.io.EOFException: Premature EOF: no length prefix available
> at 
> org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed(PBHelper.java:2282)
> at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1352)
> at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1271)
> at 
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:464)
> 16/05/11 13:37:07 INFO hdfs.DFSClient: Abandoning 
> BP-1964113808-130.8.138.99-1446787670498:blk_1073835906_95114
> 16/05/11 13:37:08 INFO hdfs.DFSClient: Excluding datanode 
> DatanodeInfoWithStorage[130.8.138.99:50010,DS-eed7039a-8031-499e-85a5-7216b9d766a8,DISK]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: apache-atlas-nightly #275

[Apache Jenkins Server]

See 

Changes:

[sumasai.shivaprasad] ATLAS-619 Canonicalize hive queries (sumasai)

--
[...truncated 4829 lines...]
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 60 Java sources to 

[WARNING] Note: 

 uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: 

 uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 60 source files to 

[WARNING] 
:
 

 uses or overrides a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 

 uses unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 42 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 42 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [2240 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-w

[jira] [Updated] (ATLAS-673) Install Setup: SOLR

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-673:
---
Attachment: ATLAS-673-2.patch

Latest patch from RB

> Install Setup: SOLR
> ---
>
> Key: ATLAS-673
> URL: https://issues.apache.org/jira/browse/ATLAS-673
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Tom Beerbower
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-673-2.patch, ATLAS-673.patch
>
>
> As a part of Atlas install,  SOLR indexes need to be setup properly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-619) Queries should be normalized when tracking lineage at table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-619:
---
Attachment: ATLAS-619.4.patch

Latest patch committed

> Queries should be normalized when  tracking lineage at table
> 
>
> Key: ATLAS-619
> URL: https://issues.apache.org/jira/browse/ATLAS-619
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-619.4.patch, ATLAS-619.patch
>
>
> Partition type and entities are no loner being created after ATLAS-599. Even 
> prior to this change , the linage for partition based queries are being 
> tracked at the table level and not at the partition level which would be 
> ideal. To track at the table level, the queries should be canonicialized for 
> the partition values or only the latest few partition queries should be 
> tracked since otherwise there could be potentially thousands of such queries 
> while tracking lineage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47107: ATLAS_619 Normalize literals for hive queries

[Suma Shivaprasad]

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

(Updated May 13, 2016, 3:37 p.m.)


Review request for atlas.


Changes
---

fixed comments


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


Repository: atlas


Description
---

Normlized all literals in a query and replacing them CONSTANT literals. Storing 
recently run queries in  a new attribute for hive_process - recentQueries


Diffs (updated)
-

  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java 
8fced05 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
 2494675 
  
addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
 4e2a06f 
  addons/hive-bridge/pom.xml eeb2aa4 
  addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
ffd5d22 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
 6418770 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/ASTRewriter.java 
PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/HiveASTRewriter.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/LiteralRewriter.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteContext.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteException.java
 PRE-CREATION 
  
addons/hive-bridge/src/test/java/org/apache/atlas/hive/bridge/HiveLiteralRewriterTest.java
 PRE-CREATION 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
da21195 
  addons/hive-bridge/src/test/resources/hive-site.xml f1facb8 
  addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
ab7e6ee 
  
addons/sqoop-bridge/src/test/java/org/apache/atlas/sqoop/hook/SqoopHookIT.java 
2820169 
  
addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
 267e228 
  
addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
 de67c39 
  
repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
9f69940 
  repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 66e1365 
  webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 70dce6b 
  webapp/src/test/java/org/apache/atlas/examples/QuickStartIT.java cdf6049 
  
webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
 bc02f90 

Diff: https://reviews.apache.org/r/47107/diff/


Testing
---

Added UT - HiveAStREwriteTest and IT asserttions in HiveHookIT


Thanks,

Suma Shivaprasad

Re: Review Request 47135: Install Setup: SOLR

[Tom Beerbower]

> On May 10, 2016, 6:11 p.m., Suma Shivaprasad wrote:
> > distro/src/bin/atlas_config.py, line 102
> > 
> >
> > if this config is changed by a user through Ambari, we need to handle 
> > the case where we need to support resharding after confirming from the 
> > user. I am not sure if this is something that can be done instantaneously 
> > or requires down time. Can we dig deeper and see how we can handle this. 
> > The same goes for replica
> 
> Tom Beerbower wrote:
> It can be set by Ambari.  I'll deal with it in the related Ambari patch.
> 
> The resharding seems like an issue with or without this patch.  Can it be 
> handled in a separate Jira?
> 
> Suma Shivaprasad wrote:
> Yes we can take it up in a separate jira
> 
> Suma Shivaprasad wrote:
> If the user changes these values and expects it to be reflected with the 
> bew values in the setup, it can lead to confusion. Are we planning to address 
> this jira for Erie?

I think we can document for now and handle the resharding in a separate Jira.


- Tom


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


On May 12, 2016, 1:19 a.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47135/
> ---
> 
> (Updated May 12, 2016, 1:19 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-663 and ATLAS-673
> https://issues.apache.org/jira/browse/ATLAS-663
> https://issues.apache.org/jira/browse/ATLAS-673
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Install standalone SOLR by default.
> 
> SOLR indexes need to be setup properly.
> 
> Fix location of standalone solr and hbase data dirs.
> 
> 
> Diffs
> -
> 
>   .gitignore 20db282 
>   distro/pom.xml ee9add0 
>   distro/src/bin/atlas_config.py dbe1191 
>   distro/src/bin/atlas_start.py 73b8920 
>   distro/src/bin/atlas_stop.py 265084e 
>   distro/src/conf/atlas-application.properties 119865d 
>   distro/src/conf/hbase/hbase-site.xml.template f5c4aad 
>   distro/src/main/assemblies/standalone-package.xml 527f604 
>   distro/src/test/python/scripts/TestMetadata.py 9e55869 
>   docs/src/site/twiki/Configuration.twiki 0793c82 
>   docs/src/site/twiki/InstallationSteps.twiki 270d1c4 
> 
> Diff: https://reviews.apache.org/r/47135/diff/
> 
> 
> Testing
> ---
> 
> Manual testing of atlas_start / atlas_start with standalone solr.
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

Build failed in Jenkins: apache-atlas-nightly #274

[Apache Jenkins Server]

See 

Changes:

[hyamijala] ATLAS-784 Configure config.store.uri for Falcon hook IT (yhemanth)

--
[...truncated 4828 lines...]
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 60 Java sources to 

[WARNING] Note: 

 uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: 

 uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 60 source files to 

[WARNING] 
:
 

 uses or overrides a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 

 uses unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 42 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 42 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [3061 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor)

[jira] [Commented] (ATLAS-784) Configure config.store.uri for Falcon hook IT

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-784:


0.10 version of Falcon has a code path change from the 0.8 version causing the 
test failure. Debugging this, I found we need to set a configuration property 
{{config.store.uri}} in Falcon's startup.properties. Adding this property does 
not affect the 0.8 version.


> Configure config.store.uri for Falcon hook IT
> -
>
> Key: ATLAS-784
> URL: https://issues.apache.org/jira/browse/ATLAS-784
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Attachments: ATLAS-784.patch
>
>
> While testing with later versions of Falcon dependencies, we found 
> FalconHookIT is failing due to expecting a particular property. The specific 
> exception is
> {code}
> java.lang.ExceptionInInitializerError
> at 
> org.apache.atlas.falcon.hook.FalconHookIT.(FalconHookIT.java:69)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at 
> org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:28)
> at org.testng.internal.ClassHelper.createInstance1(ClassHelper.java:372)
> at org.testng.internal.ClassHelper.createInstance(ClassHelper.java:284)
> at org.testng.internal.ClassImpl.getDefaultInstance(ClassImpl.java:109)
> at org.testng.internal.ClassImpl.getInstances(ClassImpl.java:181)
> at 
> org.testng.internal.TestNGClassFinder.(TestNGClassFinder.java:120)
> at org.testng.TestRunner.initMethods(TestRunner.java:402)
> at org.testng.TestRunner.init(TestRunner.java:228)
> at org.testng.TestRunner.init(TestRunner.java:198)
> at org.testng.TestRunner.(TestRunner.java:147)
> at 
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:525)
> at org.testng.SuiteRunner.init(SuiteRunner.java:156)
> at org.testng.SuiteRunner.(SuiteRunner.java:110)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1235)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1222)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1074)
> at org.testng.TestNG.run(TestNG.java:999)
> at 
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132)
> at 
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at 
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at 
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> Caused by: java.lang.IllegalArgumentException: Can not create a Path from a 
> null string
> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:122)
> at org.apache.hadoop.fs.Path.(Path.java:134)
> at org.apache.falcon.util.StartupProperties.get(StartupProperties.java:91)
> at 
> org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:121)
> at 
> org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:99)
> ... 29 more
> {code}
> Adding this property does not harm the current versions we are building with, 
> so filing this ticket to add the same for ease of migrating.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-784) Configure config.store.uri for Falcon hook IT

[Shwetha G S (JIRA)]

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

Shwetha G S commented on ATLAS-784:
---

+1

> Configure config.store.uri for Falcon hook IT
> -
>
> Key: ATLAS-784
> URL: https://issues.apache.org/jira/browse/ATLAS-784
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Attachments: ATLAS-784.patch
>
>
> While testing with later versions of Falcon dependencies, we found 
> FalconHookIT is failing due to expecting a particular property. The specific 
> exception is
> {code}
> java.lang.ExceptionInInitializerError
> at 
> org.apache.atlas.falcon.hook.FalconHookIT.(FalconHookIT.java:69)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at 
> org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:28)
> at org.testng.internal.ClassHelper.createInstance1(ClassHelper.java:372)
> at org.testng.internal.ClassHelper.createInstance(ClassHelper.java:284)
> at org.testng.internal.ClassImpl.getDefaultInstance(ClassImpl.java:109)
> at org.testng.internal.ClassImpl.getInstances(ClassImpl.java:181)
> at 
> org.testng.internal.TestNGClassFinder.(TestNGClassFinder.java:120)
> at org.testng.TestRunner.initMethods(TestRunner.java:402)
> at org.testng.TestRunner.init(TestRunner.java:228)
> at org.testng.TestRunner.init(TestRunner.java:198)
> at org.testng.TestRunner.(TestRunner.java:147)
> at 
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:525)
> at org.testng.SuiteRunner.init(SuiteRunner.java:156)
> at org.testng.SuiteRunner.(SuiteRunner.java:110)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1235)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1222)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1074)
> at org.testng.TestNG.run(TestNG.java:999)
> at 
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132)
> at 
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at 
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at 
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> Caused by: java.lang.IllegalArgumentException: Can not create a Path from a 
> null string
> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:122)
> at org.apache.hadoop.fs.Path.(Path.java:134)
> at org.apache.falcon.util.StartupProperties.get(StartupProperties.java:91)
> at 
> org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:121)
> at 
> org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:99)
> ... 29 more
> {code}
> Adding this property does not harm the current versions we are building with, 
> so filing this ticket to add the same for ease of migrating.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-710) Soft deletes: GET response on a deleted hive tables should have references to hive_db and hive_storagedesc

[Shwetha G S (JIRA)]

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

Shwetha G S resolved ATLAS-710.
---
Resolution: Duplicate

Will address it as part of ATLAS-716

> Soft deletes: GET response on a deleted hive tables should have references to 
> hive_db and hive_storagedesc
> --
>
> Key: ATLAS-710
> URL: https://issues.apache.org/jira/browse/ATLAS-710
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Shwetha G S
>
> Soft deletes: GET response on a deleted hive tables does not have references 
> to hive_db and hive_storagedesc.
> After creating the hive_table, get response shows references to db, sd and 
> columns
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/entities/1b11b234-7360-4679-93f9-d1c01f839f79'
>  -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Accept-Language: 
> en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 
> 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 
> Safari/537.36' -H 'Accept: application/json, text/plain, */*' -H 'Referer: 
> http://localhost:21000/index.html' -H 'Cookie: 
> JSESSIONID=3frbae3qwzi2xkdjyvz8nyko' -H 'Connection: keep-alive' --compressed 
> | python -m json.tool
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  32710  32710 0   2088  0 --:--:--  0:00:01 --:--:--  2088
> {
> "GUID": "1b11b234-7360-4679-93f9-d1c01f839f79",
> "definition": {
> "id": {
> "id": "1b11b234-7360-4679-93f9-d1c01f839f79",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_table",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_table",
> "values": {
> "columns": [
> {
> "id": {
> "id": "2c50426e-7db3-4912-9bbc-13150e962ed5",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_column",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_column",
> "values": {
> "comment": null,
> "name": "name",
> "qualifiedName": 
> "default.after_changes_13.name@primary",
> "type": "string"
> }
> },
> {
> "id": {
> "id": "2af81d25-bbcd-44bd-95b8-4fee915c9dba",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_column",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_column",
> "values": {
> "comment": null,
> "name": "age",
> "qualifiedName": 
> "default.after_changes_13.age@primary",
> "type": "int"
> }
> }
> ],
> "comment": null,
> "createTime": "2016-04-26T09:27:29.000Z",
> "db": {
> "id": "b23cc76a-32e4-4137-860e-8cac2689ba0e",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_db",
> "version": 0
> },
> "description": null,
> "lastAccessTime": "2016-04-26T09:27:29.000Z",
> "name": "default.after_changes_13@primary",
> "owner": "apathan",
> "parameters": {
> "transient_lastDdlTime": "1461662849"
> },
> "partitionKeys": [
> {
> "id": {
> "id": "84db2789-82b3-460e

[jira] [Created] (ATLAS-785) Kerberized cluster: Embedded hbase fails to comeup because not keytab info is found, resulting in atlas failure.

[Ayub Khan (JIRA)]

Ayub Khan created ATLAS-785:
---

 Summary: Kerberized cluster: Embedded hbase fails to comeup 
because not keytab info is found, resulting in atlas failure.
 Key: ATLAS-785
 URL: https://issues.apache.org/jira/browse/ATLAS-785
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Ayub Khan
Priority: Blocker
 Fix For: 0.7-incubating


Embedded hbase log snapshot:
{noformat}
2016-05-13 06:26:28,965 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61581] 
server.NIOServerCnxnFactory: Accepted socket connection from /127.0.0.1:55701
2016-05-13 06:26:28,982 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61581] 
server.NIOServerCnxn: Processing stat command from /127.0.0.1:55701
2016-05-13 06:26:28,995 INFO  [Thread-2] server.NIOServerCnxn: Stat command 
output
2016-05-13 06:26:28,996 INFO  [main] zookeeper.MiniZooKeeperCluster: Started 
MiniZooKeeperCluster and ran successful 'stat' on client port=61581
2016-05-13 06:26:28,996 INFO  [main] master.HMasterCommandLine: Starting up 
instance of localHBaseCluster; master=1, regionserversCount=1
2016-05-13 06:26:29,006 INFO  [Thread-2] server.NIOServerCnxn: Closed socket 
connection for client /127.0.0.1:55701 (no session established for client)
2016-05-13 06:26:32,013 INFO  [main] regionserver.RSRpcServices: 
master/ranger-erie-suja-test2-2.openstacklocal/172.22.117.31:0 server-side 
HConnection retries=350
2016-05-13 06:26:33,009 INFO  [main] ipc.SimpleRpcScheduler: Using deadline as 
user call queue, count=3
2016-05-13 06:26:33,248 INFO  [main] ipc.RpcServer: 
master/ranger-erie-suja-test2-2.openstacklocal/172.22.117.31:0: started 10 
reader(s) listening on port=53455
2016-05-13 06:26:33,652 INFO  [main] impl.MetricsConfig: loaded properties from 
hadoop-metrics2-hbase.properties
2016-05-13 06:26:33,814 INFO  [main] impl.MetricsSystemImpl: Scheduled snapshot 
period at 10 second(s).
2016-05-13 06:26:33,814 INFO  [main] impl.MetricsSystemImpl: HBase metrics 
system started
2016-05-13 06:26:33,938 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Failed construction of Master: class 
org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at 
org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:143)
at 
org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:219)
at 
org.apache.hadoop.hbase.LocalHBaseCluster.(LocalHBaseCluster.java:155)
at 
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:224)
at 
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at 
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2355)
Caused by: java.io.IOException: Running in secure mode, but config doesn't have 
a keytab
at org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:235)
at 
org.apache.hadoop.hbase.security.User$SecureHadoopUser.login(User.java:386)
at org.apache.hadoop.hbase.security.User.login(User.java:253)
at 
org.apache.hadoop.hbase.security.UserProvider.login(UserProvider.java:115)
at org.apache.hadoop.hbase.master.HMaster.login(HMaster.java:488)
at 
org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:549)
at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:365)
at 
org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster.(HMasterCommandLine.java:307)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at 
org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:139)
... 7 more
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-784) Configure config.store.uri for Falcon hook IT

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-784:
---
Attachment: ATLAS-784.patch

> Configure config.store.uri for Falcon hook IT
> -
>
> Key: ATLAS-784
> URL: https://issues.apache.org/jira/browse/ATLAS-784
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Attachments: ATLAS-784.patch
>
>
> While testing with later versions of Falcon dependencies, we found 
> FalconHookIT is failing due to expecting a particular property. The specific 
> exception is
> {code}
> java.lang.ExceptionInInitializerError
> at 
> org.apache.atlas.falcon.hook.FalconHookIT.(FalconHookIT.java:69)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at 
> org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:28)
> at org.testng.internal.ClassHelper.createInstance1(ClassHelper.java:372)
> at org.testng.internal.ClassHelper.createInstance(ClassHelper.java:284)
> at org.testng.internal.ClassImpl.getDefaultInstance(ClassImpl.java:109)
> at org.testng.internal.ClassImpl.getInstances(ClassImpl.java:181)
> at 
> org.testng.internal.TestNGClassFinder.(TestNGClassFinder.java:120)
> at org.testng.TestRunner.initMethods(TestRunner.java:402)
> at org.testng.TestRunner.init(TestRunner.java:228)
> at org.testng.TestRunner.init(TestRunner.java:198)
> at org.testng.TestRunner.(TestRunner.java:147)
> at 
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:525)
> at org.testng.SuiteRunner.init(SuiteRunner.java:156)
> at org.testng.SuiteRunner.(SuiteRunner.java:110)
> at org.testng.TestNG.createSuiteRunner(TestNG.java:1235)
> at org.testng.TestNG.createSuiteRunners(TestNG.java:1222)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1074)
> at org.testng.TestNG.run(TestNG.java:999)
> at 
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132)
> at 
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
> at 
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
> at 
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> Caused by: java.lang.IllegalArgumentException: Can not create a Path from a 
> null string
> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:122)
> at org.apache.hadoop.fs.Path.(Path.java:134)
> at org.apache.falcon.util.StartupProperties.get(StartupProperties.java:91)
> at 
> org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:121)
> at 
> org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:99)
> ... 29 more
> {code}
> Adding this property does not harm the current versions we are building with, 
> so filing this ticket to add the same for ease of migrating.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47293: ATLAS-736 :: UI - BUG :: displaying timestamp values for hive_db description

[keval bhatt]

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

(Updated May 13, 2016, 10:39 a.m.)


Review request for atlas, Ayub Pathan, Gautam Borad, Shwetha GS, Selvamohan 
Neethiraj, and Hemanth Yamijala.


Changes
---

Handled all your suggestions. 

Overall Patch contains :: 
1) It takes care of Null values in all Table columns (in search result Table).
2) Corrected error response as well as success message as per your suggestion. 
3) Corrected display of Top Navigation menu item of current page  (sometimes it 
was showing improper top navigation menu item)
4) Improvised by adding a common function view to show the modal for Delete Tag.


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


Repository: atlas


Description
---

Bug Description : Showing date in description if description is null same for 
other colums

Changed: * Validation added to handle null value and showing empty value.
 * Removed Tools column for add tag and add tag button displayed after 
tags.
 * Search table loading effect improvements.
 * Header Menu fix.


Diffs (updated)
-

  dashboardv2/public/css/override.css 4c452cc 
  dashboardv2/public/index.html c2f15c9 
  dashboardv2/public/js/utils/CommonViewFunction.js PRE-CREATION 
  dashboardv2/public/js/views/asset/AssetPageLayoutView.js c86fef4 
  dashboardv2/public/js/views/schema/SchemaLayoutView.js 35487a5 
  dashboardv2/public/js/views/site/Header.js 500bd91 
  dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js c5e1ace 
  dashboardv2/public/js/views/tag/addTagModalView.js d663ae2 

Diff: https://reviews.apache.org/r/47293/diff/


Testing
---

Manually tested the changes.


Thanks,

keval bhatt

[jira] [Updated] (ATLAS-736) New UI: displaying timestamp values for hive_db description

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-736:
--
Attachment: ATLAS-736.1.patch

> New UI: displaying timestamp values for hive_db description
> ---
>
> Key: ATLAS-736
> URL: https://issues.apache.org/jira/browse/ATLAS-736
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-736.1.patch, ATLAS-736.patch
>
>
> New UI: displaying timestamp values for hive_db description, whose actual 
> value is null.
> https://monosnap.com/file/FSJqVfbgMzMbWKVPl5ou6PNo2AO1Dj



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: apache-atlas-nightly #273

[Apache Jenkins Server]

See 

Changes:

[sshivalingamurthy] ATLAS-645 FieldMapping.output() results in stack overflow 
when instances

--
[...truncated 4828 lines...]
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 60 Java sources to 

[WARNING] Note: 

 uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: 

 uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 60 source files to 

[WARNING] 
:
 

 uses or overrides a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 

 uses unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 42 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 42 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [1064 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (att

[jira] [Created] (ATLAS-784) Configure config.store.uri for Falcon hook IT

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-784:
--

 Summary: Configure config.store.uri for Falcon hook IT
 Key: ATLAS-784
 URL: https://issues.apache.org/jira/browse/ATLAS-784
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala
Assignee: Hemanth Yamijala


While testing with later versions of Falcon dependencies, we found FalconHookIT 
is failing due to expecting a particular property. The specific exception is

{code}
java.lang.ExceptionInInitializerError
at org.apache.atlas.falcon.hook.FalconHookIT.(FalconHookIT.java:69)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at 
org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:28)
at org.testng.internal.ClassHelper.createInstance1(ClassHelper.java:372)
at org.testng.internal.ClassHelper.createInstance(ClassHelper.java:284)
at org.testng.internal.ClassImpl.getDefaultInstance(ClassImpl.java:109)
at org.testng.internal.ClassImpl.getInstances(ClassImpl.java:181)
at org.testng.internal.TestNGClassFinder.(TestNGClassFinder.java:120)
at org.testng.TestRunner.initMethods(TestRunner.java:402)
at org.testng.TestRunner.init(TestRunner.java:228)
at org.testng.TestRunner.init(TestRunner.java:198)
at org.testng.TestRunner.(TestRunner.java:147)
at 
org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:525)
at org.testng.SuiteRunner.init(SuiteRunner.java:156)
at org.testng.SuiteRunner.(SuiteRunner.java:110)
at org.testng.TestNG.createSuiteRunner(TestNG.java:1235)
at org.testng.TestNG.createSuiteRunners(TestNG.java:1222)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1074)
at org.testng.TestNG.run(TestNG.java:999)
at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:132)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
at 
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:147)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Caused by: java.lang.IllegalArgumentException: Can not create a Path from a 
null string
at org.apache.hadoop.fs.Path.checkPathArg(Path.java:122)
at org.apache.hadoop.fs.Path.(Path.java:134)
at org.apache.falcon.util.StartupProperties.get(StartupProperties.java:91)
at 
org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:121)
at 
org.apache.falcon.entity.store.ConfigurationStore.(ConfigurationStore.java:99)
... 29 more
{code}

Adding this property does not harm the current versions we are building with, 
so filing this ticket to add the same for ease of migrating.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[Vimal Sharma (JIRA)]

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

Vimal Sharma reassigned ATLAS-688:
--

Assignee: Vimal Sharma

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-645) FieldMapping.output() results in stack overflow when instances reference each other

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-645:
--
Attachment: rb45948.patch

patch from reveiwboard

> FieldMapping.output() results in stack overflow when instances reference each 
> other
> ---
>
> Key: ATLAS-645
> URL: https://issues.apache.org/jira/browse/ATLAS-645
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: David Kantor
> Attachments: rb45948.patch, rb45948.patch
>
>
> FieldMapping.output() results in a stack overflow due to infinite recursion 
> when two IReferenceableInstance or IStruct objects reference each other.  
> This issue was first exposed by 
> GraphBackedMetadataRepositoryDeleteEntitiesTest.testDisconnectMapReferenceFromClassType().
> {noformat}
> SLF4J: Failed toString() invocation on an object of type 
> [org.apache.atlas.typesystem.persistence.ReferenceableInstance]
> java.lang.StackOverflowError
>   at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
>   at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
>   at java.util.regex.Pattern$BranchConn.match(Pattern.java:4466)
>   at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615)
>   at java.util.regex.Pattern$Curly.match0(Pattern.java:4177)
>   at java.util.regex.Pattern$Curly.match(Pattern.java:4132)
>   at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
>   at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
>   at java.util.regex.Pattern$Branch.match(Pattern.java:4500)
>   at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715)
>   at java.util.regex.Pattern$Start.match(Pattern.java:3408)
>   at java.util.regex.Matcher.search(Matcher.java:1199)
>   at java.util.regex.Matcher.find(Matcher.java:618)
>   at java.util.Formatter.parse(Formatter.java:2517)
>   at java.util.Formatter.format(Formatter.java:2469)
>   at java.util.Formatter.format(Formatter.java:2423)
>   at java.lang.String.format(String.java:2792)
>   at org.apache.atlas.typesystem.persistence.Id.toString(Id.java:98)
>   at 
> org.apache.atlas.typesystem.types.FieldMapping.output(FieldMapping.java:114)
>   at 
> org.apache.atlas.typesystem.persistence.ReferenceableInstance.toString(ReferenceableInstance.java:92)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47107: ATLAS_619 Normalize literals for hive queries

[Shwetha GS]

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


Fix it, then Ship it!





addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
(line 110)


change to - procRef.set(AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, 
sqoopProcessName)



repository/src/main/java/org/apache/atlas/repository/graph/TypedInstanceToGraphMapper.java
 (line 560)


no changes, revert file


- Shwetha GS


On May 13, 2016, 7:20 a.m., Suma Shivaprasad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47107/
> ---
> 
> (Updated May 13, 2016, 7:20 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-619
> https://issues.apache.org/jira/browse/ATLAS-619
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Normlized all literals in a query and replacing them CONSTANT literals. 
> Storing recently run queries in  a new attribute for hive_process - 
> recentQueries
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  8fced05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  2494675 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  4e2a06f 
>   addons/hive-bridge/pom.xml eeb2aa4 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> ffd5d22 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  6418770 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/ASTRewriter.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/HiveASTRewriter.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/LiteralRewriter.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteContext.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteException.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/test/java/org/apache/atlas/hive/bridge/HiveLiteralRewriterTest.java
>  PRE-CREATION 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> da21195 
>   addons/hive-bridge/src/test/resources/hive-site.xml f1facb8 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> ab7e6ee 
>   
> addons/sqoop-bridge/src/test/java/org/apache/atlas/sqoop/hook/SqoopHookIT.java
>  2820169 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  267e228 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  de67c39 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/TypedInstanceToGraphMapper.java
>  a017536 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  9f69940 
>   repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 
> 66e1365 
>   webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 70dce6b 
>   webapp/src/test/java/org/apache/atlas/examples/QuickStartIT.java cdf6049 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
>  bc02f90 
> 
> Diff: https://reviews.apache.org/r/47107/diff/
> 
> 
> Testing
> ---
> 
> Added UT - HiveAStREwriteTest and IT asserttions in HiveHookIT
> 
> 
> Thanks,
> 
> Suma Shivaprasad
> 
>

Re: Review Request 45948: Atlas-645: avoid infinite recursion in FieldMapping.output()

[Shwetha GS]

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


Ship it!




Ship It!

- Shwetha GS


On May 13, 2016, 2:09 a.m., David Kantor wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/45948/
> ---
> 
> (Updated May 13, 2016, 2:09 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-645
> https://issues.apache.org/jira/browse/ATLAS-645
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-645: In FieldMapping.output(), avoid infinite recursion when 
> IReferenceableInstance and IStruct instances reference each other.
> 
> 
> Diffs
> -
> 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/persistence/ReferenceableInstance.java
>  31ef49d5e6accd8b4621385cce1e3a6b7a6936ff 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/persistence/StructInstance.java
>  af62442bfe5daa221079207acf361e1316cab3ad 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/AbstractDataType.java
>  92be3c794077bd3e437aa6f3426ed8b7892b945e 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/AttributeInfo.java 
> e748579df8056994899624fac8e8a86958a27a6f 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/ClassType.java 
> 90cf3ccfe8e9d0e20901452c0b83796ba3994998 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/DataTypes.java 
> 55ec91f5c3cba65f1bf7c524c84c075cc1c96dff 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/FieldMapping.java 
> 36149bafff80b68ce176e82dcacac87035459362 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/HierarchicalType.java
>  89fcea6828c9e23c28a60952c3e4ca27c0667494 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/IDataType.java 
> 373ad2c93efdecc292b68fab1ea2403afce84dac 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/Multiplicity.java 
> a54dabc2f8366dbecc8372d81a48c741b2d65258 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/StructType.java 
> 54e344f5d6322a00ac7825ee8964f43a1552dcbe 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/TraitType.java 
> 84c22bf96a059a78b065a73a8feefae87deb9975 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/TypedStructHandler.java
>  da246d66d94bcd3e221b70b859de2850fa6cf7a8 
>   
> typesystem/src/test/java/org/apache/atlas/typesystem/types/FieldMappingTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/45948/diff/
> 
> 
> Testing
> ---
> 
> Ran all unit and integration tests with no regressions.  Added test cases
> 
> 
> Thanks,
> 
> David Kantor
> 
>

[jira] [Updated] (ATLAS-713) Atlas UI is still showing the deleted column of a hive table (Entity response of hive table does not have it). - with browser cache disabled.

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-713:
--
Attachment: ATLAS-713-v2.patch

> Atlas UI is still showing the deleted column of a hive table (Entity response 
> of hive table does not have it). - with browser cache disabled.
> -
>
> Key: ATLAS-713
> URL: https://issues.apache.org/jira/browse/ATLAS-713
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-713-v2.patch, ATLAS-713.patch
>
>
> Atlas UI is still showing the deleted column of a hive table (Entity response 
> of hive table does not have it). - with browser cache disabled.
> Create a hive table (CREATE TABLE test_change1 (a int, b int, c int); )
> Change column name to new one (ALTER TABLE test_change1 CHANGE c c1 INT 
> FIRST; )
> UI snapshot: https://monosnap.com/file/GVOipYxkcaJPcqgnJuxULBTCZopytR
> {noformat}
> curl 
> 'http://localhost:21000/api/atlas/entities/ff37663a-7561-462c-9ec8-2bacaebc0296'
>  -H 'Pragma: no-cache' -H 'Accept-Encoding: gzip, deflate, sdch' -H 
> 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; 
> Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) 
> Chrome/49.0.2623.112 Safari/537.36' -H 'Accept: application/json, text/plain, 
> */*' -H 'Referer: http://localhost:21000/index.html' -H 'Cookie: 
> JSESSIONID=13d5gxn515o7l5271gbb0j0ec' -H 'Connection: keep-alive' -H 
> 'Cache-Control: no-cache' --compressed | python -m json.tool
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  33900  33900 0   2187  0 --:--:--  0:00:01 --:--:--  2188
> {
> "GUID": "ff37663a-7561-462c-9ec8-2bacaebc0296",
> "definition": {
> "id": {
> "id": "ff37663a-7561-462c-9ec8-2bacaebc0296",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_table",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_table",
> "values": {
> "columns": [
> {
> "id": {
> "id": "9252f481-ca2a-4b31-88d2-d404dfc9d3fd",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_column",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_column",
> "values": {
> "comment": null,
> "name": "c1",
> "qualifiedName": "default.test_change1.c1@primary",
> "type": "int"
> }
> },
> {
> "id": {
> "id": "a4d14fff-842f-48bc-962f-0e4fbac2a815",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_column",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "traitNames": [],
> "traits": {},
> "typeName": "hive_column",
> "values": {
> "comment": null,
> "name": "a",
> "qualifiedName": "default.test_change1.a@primary",
> "type": "int"
> }
> },
> {
> "id": {
> "id": "5c700938-5782-4ae4-8599-7dfe90fecfdc",
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "state": "ACTIVE",
> "typeName": "hive_column",
> "version": 0
> },
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference

Re: Review Request 47225: ATLAS-713 Atlas UI is still showing the deleted column of a hive table (Entity response of hive table does not have it). - with browser cache disabled.

[Shwetha GS]

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

(Updated May 13, 2016, 9:19 a.m.)


Review request for atlas.


Changes
---

Rename of classes


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


Repository: atlas


Description
---

Current lineage APIs work on the dataset name. With soft delete, there can be 
more than one entities for the given dataset name. 
1. Added new lineage APIs(input graph, output graph, schema) which work on 
entity id
2. Modified current lineage APIs to work on the active entity for the given 
dataset name
3. Modified UI to use the new APIs


Diffs (updated)
-

  client/src/main/java/org/apache/atlas/AtlasClient.java b3ec95c 
  dashboardv2/public/js/models/VLineage.js e33488a 
  dashboardv2/public/js/models/VSchema.js 1f8e0bb 
  dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js 87adec0 
  dashboardv2/public/js/views/graph/LineageLayoutView.js 973d091 
  dashboardv2/public/js/views/schema/SchemaLayoutView.js 35487a5 
  distro/src/conf/atlas-application.properties 68a0021 
  repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java 
8dae968 
  
repository/src/main/java/org/apache/atlas/discovery/DataSetLineageService.java 
PRE-CREATION 
  repository/src/main/java/org/apache/atlas/discovery/HiveLineageService.java 
00905d7 
  repository/src/main/scala/org/apache/atlas/query/ClosureQuery.scala 05dc6a4 
  repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 66e1365 
  repository/src/test/java/org/apache/atlas/BaseRepositoryTest.java 
PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/discovery/DataSetLineageServiceTest.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/discovery/GraphBackedDiscoveryServiceTest.java
 3b50dfb 
  
repository/src/test/java/org/apache/atlas/discovery/HiveLineageServiceTest.java 
6d5a15a 
  repository/src/test/scala/org/apache/atlas/query/GremlinTest2.scala 2fd8bb9 
  server-api/src/main/java/org/apache/atlas/discovery/LineageService.java 
8dc36cd 
  typesystem/src/main/resources/atlas-application.properties aafad0f 
  
webapp/src/main/java/org/apache/atlas/web/resources/DataSetLineageResource.java 
PRE-CREATION 
  webapp/src/main/java/org/apache/atlas/web/resources/HiveLineageResource.java 
9b3fbc9 
  webapp/src/main/java/org/apache/atlas/web/resources/LineageResource.java 
PRE-CREATION 
  
webapp/src/test/java/org/apache/atlas/web/resources/DataSetLineageJerseyResourceIT.java
 PRE-CREATION 
  
webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
 bc02f90 

Diff: https://reviews.apache.org/r/47225/diff/


Testing
---

UTs, ITs and end to end test with hive cli


Thanks,

Shwetha GS

Build failed in Jenkins: apache-atlas-nightly #272

[Apache Jenkins Server]

See 

Changes:

[sumasai.shivaprasad] ATLAS-663,ATLAS-673 Install Setup: SOLR (tbeerbower via 
sumasai)

[hyamijala] ATLAS-733 UI: undefined XHR request is made for every entity GET 
page

--
[...truncated 4805 lines...]
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 60 Java sources to 

[WARNING] Note: 

 uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: 

 uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 60 source files to 

[WARNING] 
:
 

 uses or overrides a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 

 uses unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 42 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 42 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [524 msecs]
[INFO] Building war: 

[jira] [Updated] (ATLAS-783) UI: Table view showing results for entities like hive_table is very cramped.

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-783:
---
Attachment: hive_table.png

Picture showing the truncation of columns and empty space that can possibly be 
optimized.

> UI: Table view showing results for entities like hive_table is very cramped.
> 
>
> Key: ATLAS-783
> URL: https://issues.apache.org/jira/browse/ATLAS-783
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
> Attachments: hive_table.png
>
>
> Integrate with Hive and import a few table entities into Atlas. In the UI, 
> search for hive_table using DSL. This displays a table with a long list of 
> columns that should be scrolled. Things like tags (which I believe are fairly 
> important) are shown at the end of this frame and not immediately visible. 
> However, overall there's lots of unused real estate in the page and I think 
> we can use that. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-783) UI: Table view showing results for entities like hive_table is very cramped.

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-783:
--

 Summary: UI: Table view showing results for entities like 
hive_table is very cramped.
 Key: ATLAS-783
 URL: https://issues.apache.org/jira/browse/ATLAS-783
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Hemanth Yamijala


Integrate with Hive and import a few table entities into Atlas. In the UI, 
search for hive_table using DSL. This displays a table with a long list of 
columns that should be scrolled. Things like tags (which I believe are fairly 
important) are shown at the end of this frame and not immediately visible. 
However, overall there's lots of unused real estate in the page and I think we 
can use that. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47107: ATLAS_619 Normalize literals for hive queries

[Suma Shivaprasad]

> On May 12, 2016, 9:21 a.m., Shwetha GS wrote:
> > addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java, 
> > line 726
> > 
> >
> > Can you file a bug to handle hive_process update - to update 
> > recentQueries

ATLAS-782


- Suma


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


On May 13, 2016, 7:20 a.m., Suma Shivaprasad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47107/
> ---
> 
> (Updated May 13, 2016, 7:20 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-619
> https://issues.apache.org/jira/browse/ATLAS-619
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Normlized all literals in a query and replacing them CONSTANT literals. 
> Storing recently run queries in  a new attribute for hive_process - 
> recentQueries
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  8fced05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  2494675 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  4e2a06f 
>   addons/hive-bridge/pom.xml eeb2aa4 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> ffd5d22 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  6418770 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/ASTRewriter.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/HiveASTRewriter.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/LiteralRewriter.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteContext.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteException.java
>  PRE-CREATION 
>   
> addons/hive-bridge/src/test/java/org/apache/atlas/hive/bridge/HiveLiteralRewriterTest.java
>  PRE-CREATION 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> da21195 
>   addons/hive-bridge/src/test/resources/hive-site.xml f1facb8 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> ab7e6ee 
>   
> addons/sqoop-bridge/src/test/java/org/apache/atlas/sqoop/hook/SqoopHookIT.java
>  2820169 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  267e228 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  de67c39 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/TypedInstanceToGraphMapper.java
>  a017536 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  9f69940 
>   repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 
> 66e1365 
>   webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 70dce6b 
>   webapp/src/test/java/org/apache/atlas/examples/QuickStartIT.java cdf6049 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
>  bc02f90 
> 
> Diff: https://reviews.apache.org/r/47107/diff/
> 
> 
> Testing
> ---
> 
> Added UT - HiveAStREwriteTest and IT asserttions in HiveHookIT
> 
> 
> Thanks,
> 
> Suma Shivaprasad
> 
>

Re: Review Request 47107: ATLAS_619 Normalize literals for hive queries

[Suma Shivaprasad]

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

(Updated May 13, 2016, 7:20 a.m.)


Review request for atlas.


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


Repository: atlas


Description
---

Normlized all literals in a query and replacing them CONSTANT literals. Storing 
recently run queries in  a new attribute for hive_process - recentQueries


Diffs (updated)
-

  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java 
8fced05 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
 2494675 
  
addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
 4e2a06f 
  addons/hive-bridge/pom.xml eeb2aa4 
  addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
ffd5d22 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
 6418770 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/ASTRewriter.java 
PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/HiveASTRewriter.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/LiteralRewriter.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteContext.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteException.java
 PRE-CREATION 
  
addons/hive-bridge/src/test/java/org/apache/atlas/hive/bridge/HiveLiteralRewriterTest.java
 PRE-CREATION 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
da21195 
  addons/hive-bridge/src/test/resources/hive-site.xml f1facb8 
  addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
ab7e6ee 
  
addons/sqoop-bridge/src/test/java/org/apache/atlas/sqoop/hook/SqoopHookIT.java 
2820169 
  
addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
 267e228 
  
addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
 de67c39 
  
repository/src/main/java/org/apache/atlas/repository/graph/TypedInstanceToGraphMapper.java
 a017536 
  
repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
9f69940 
  repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 66e1365 
  webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 70dce6b 
  webapp/src/test/java/org/apache/atlas/examples/QuickStartIT.java cdf6049 
  
webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
 bc02f90 

Diff: https://reviews.apache.org/r/47107/diff/


Testing
---

Added UT - HiveAStREwriteTest and IT asserttions in HiveHookIT


Thanks,

Suma Shivaprasad

Re: Review Request 47225: ATLAS-713 Atlas UI is still showing the deleted column of a hive table (Entity response of hive table does not have it). - with browser cache disabled.

[Hemanth Yamijala]

> On May 12, 2016, 9:12 p.m., Suma Shivaprasad wrote:
> > repository/src/main/java/org/apache/atlas/discovery/HiveLineageService.java,
> >  lines 69-70
> > 
> >
> > while we are anyways doing this, should we rename HiveLineageService to 
> > DataSetLineageService
> 
> Hemanth Yamijala wrote:
> Change the class name and also the api? I know changing the API will be a 
> breaking change. But doing it now is better than later, no? The UI will be 
> the most impacted from an internal Atlas perspective. Other than that we will 
> need to intimate Atlas dev list. We could pre-announce on dev list *before* 
> the patch gets in, IMO.
> 
> Shwetha GS wrote:
> I will change the classname. 
> 
> I have changed the UI to use the new APIs. So, there are no internal 
> users for the olds APIs. We can probably check in the community and remove 
> the tablename based lineage APIs later (alternative is get id using tablename 
> and use new lineage APIs). So, I don't want to change the path of old lineage 
> APIs. Do you strongly feel for the change

Sounds ok to me. Essentially, it seems like we can deprecate and remove in next 
release.


- Hemanth


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


On May 11, 2016, 9:21 a.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47225/
> ---
> 
> (Updated May 11, 2016, 9:21 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-713
> https://issues.apache.org/jira/browse/ATLAS-713
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Current lineage APIs work on the dataset name. With soft delete, there can be 
> more than one entities for the given dataset name. 
> 1. Added new lineage APIs(input graph, output graph, schema) which work on 
> entity id
> 2. Modified current lineage APIs to work on the active entity for the given 
> dataset name
> 3. Modified UI to use the new APIs
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/atlas/AtlasClient.java b3ec95c 
>   dashboardv2/public/js/models/VLineage.js e33488a 
>   dashboardv2/public/js/models/VSchema.js 1f8e0bb 
>   dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js 87adec0 
>   dashboardv2/public/js/views/graph/LineageLayoutView.js 973d091 
>   dashboardv2/public/js/views/schema/SchemaLayoutView.js 35487a5 
>   distro/src/conf/atlas-application.properties 119865d 
>   repository/src/main/java/org/apache/atlas/discovery/HiveLineageService.java 
> 00905d7 
>   repository/src/main/scala/org/apache/atlas/query/ClosureQuery.scala 05dc6a4 
>   repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 
> 66e1365 
>   
> repository/src/test/java/org/apache/atlas/discovery/HiveLineageServiceTest.java
>  6d5a15a 
>   repository/src/test/scala/org/apache/atlas/query/GremlinTest2.scala 2fd8bb9 
>   server-api/src/main/java/org/apache/atlas/discovery/LineageService.java 
> 8dc36cd 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/AttributeInfo.java 
> 330d1cb 
>   typesystem/src/main/resources/atlas-application.properties a343a20 
>   
> webapp/src/main/java/org/apache/atlas/web/resources/HiveLineageResource.java 
> 9b3fbc9 
>   webapp/src/main/java/org/apache/atlas/web/resources/LineageResource.java 
> PRE-CREATION 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
>  bc02f90 
> 
> Diff: https://reviews.apache.org/r/47225/diff/
> 
> 
> Testing
> ---
> 
> UTs, ITs and end to end test with hive cli
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

[jira] [Created] (ATLAS-782) Hive Hook : Append to list of recentQueries instead of replacing

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-782:
--

 Summary: Hive Hook : Append to list of recentQueries instead of 
replacing 
 Key: ATLAS-782
 URL: https://issues.apache.org/jira/browse/ATLAS-782
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Suma Shivaprasad






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47107: ATLAS_619 Normalize literals for hive queries

[Suma Shivaprasad]

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

(Updated May 13, 2016, 7:11 a.m.)


Review request for atlas.


Changes
---

Fixed review comments


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


Repository: atlas


Description
---

Normlized all literals in a query and replacing them CONSTANT literals. Storing 
recently run queries in  a new attribute for hive_process - recentQueries


Diffs (updated)
-

  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java 
8fced05 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
 2494675 
  
addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
 4e2a06f 
  addons/hive-bridge/pom.xml eeb2aa4 
  addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
ffd5d22 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
 6418770 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/ASTRewriter.java 
PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/HiveASTRewriter.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/LiteralRewriter.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteContext.java
 PRE-CREATION 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/rewrite/RewriteException.java
 PRE-CREATION 
  
addons/hive-bridge/src/test/java/org/apache/atlas/hive/bridge/HiveLiteralRewriterTest.java
 PRE-CREATION 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
da21195 
  addons/hive-bridge/src/test/resources/hive-site.xml f1facb8 
  addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
ab7e6ee 
  
addons/sqoop-bridge/src/test/java/org/apache/atlas/sqoop/hook/SqoopHookIT.java 
2820169 
  
addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
 267e228 
  
addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
 de67c39 
  
repository/src/main/java/org/apache/atlas/repository/graph/TypedInstanceToGraphMapper.java
 a017536 
  
repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
9f69940 
  repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 66e1365 
  webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 70dce6b 
  webapp/src/test/java/org/apache/atlas/examples/QuickStartIT.java cdf6049 
  
webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
 bc02f90 

Diff: https://reviews.apache.org/r/47107/diff/


Testing
---

Added UT - HiveAStREwriteTest and IT asserttions in HiveHookIT


Thanks,

Suma Shivaprasad

[jira] [Commented] (ATLAS-736) New UI: displaying timestamp values for hive_db description

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-736:


I have posted few comments on review board. Can you please take a look?

The core issue of timestamp display is fixed (as per my testing). But the patch 
has made other fixes (some are listed on the review board). I have tested 
things that I could find from the code. But can you please give a list of the 
fixes, so I can test them before committing? Thanks.

> New UI: displaying timestamp values for hive_db description
> ---
>
> Key: ATLAS-736
> URL: https://issues.apache.org/jira/browse/ATLAS-736
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-736.patch
>
>
> New UI: displaying timestamp values for hive_db description, whose actual 
> value is null.
> https://monosnap.com/file/FSJqVfbgMzMbWKVPl5ou6PNo2AO1Dj



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 47293: ATLAS-736 :: UI - BUG :: displaying timestamp values for hive_db description

[Hemanth Yamijala]

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




dashboardv2/public/js/views/asset/AssetPageLayoutView.js (line 385)


I can see this message when I delete a tag from the results table. But 
can't see it if the same is deleted from the Tags table in the asset page. You 
can take this as part of another JIRA if you want.



dashboardv2/public/js/views/asset/AssetPageLayoutView.js (line 396)


Could we have a better message here? Something like "Tag  could not 
be deleted".



dashboardv2/public/js/views/schema/SchemaLayoutView.js (line 200)


Looks like this code is duplicate in AssetPageLayoutView as well. Can this 
be refactored into being at one place?


- Hemanth Yamijala


On May 12, 2016, 7:38 a.m., keval bhatt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47293/
> ---
> 
> (Updated May 12, 2016, 7:38 a.m.)
> 
> 
> Review request for atlas, Ayub Pathan, Gautam Borad, Shwetha GS, Selvamohan 
> Neethiraj, and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-736
> https://issues.apache.org/jira/browse/ATLAS-736
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Bug Description : Showing date in description if description is null same for 
> other colums
> 
> Changed: * Validation added to handle null value and showing empty value.
>  * Removed Tools column for add tag and add tag button displayed 
> after tags.
>  * Search table loading effect improvements.
>  * Header Menu fix.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/css/override.css 4c452cc 
>   dashboardv2/public/index.html c2f15c9 
>   dashboardv2/public/js/views/asset/AssetPageLayoutView.js c86fef4 
>   dashboardv2/public/js/views/schema/SchemaLayoutView.js 35487a5 
>   dashboardv2/public/js/views/site/Header.js 500bd91 
>   dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js c5e1ace 
> 
> Diff: https://reviews.apache.org/r/47293/diff/
> 
> 
> Testing
> ---
> 
> Manually tested the changes.
> 
> 
> Thanks,
> 
> keval bhatt
> 
>

Re: Review Request 47225: ATLAS-713 Atlas UI is still showing the deleted column of a hive table (Entity response of hive table does not have it). - with browser cache disabled.

[Shwetha GS]

> On May 12, 2016, 9:12 p.m., Suma Shivaprasad wrote:
> > repository/src/main/java/org/apache/atlas/discovery/HiveLineageService.java,
> >  lines 69-70
> > 
> >
> > while we are anyways doing this, should we rename HiveLineageService to 
> > DataSetLineageService
> 
> Hemanth Yamijala wrote:
> Change the class name and also the api? I know changing the API will be a 
> breaking change. But doing it now is better than later, no? The UI will be 
> the most impacted from an internal Atlas perspective. Other than that we will 
> need to intimate Atlas dev list. We could pre-announce on dev list *before* 
> the patch gets in, IMO.

I will change the classname. 

I have changed the UI to use the new APIs. So, there are no internal users for 
the olds APIs. We can probably check in the community and remove the tablename 
based lineage APIs later (alternative is get id using tablename and use new 
lineage APIs). So, I don't want to change the path of old lineage APIs. Do you 
strongly feel for the change


- Shwetha


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


On May 11, 2016, 9:21 a.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47225/
> ---
> 
> (Updated May 11, 2016, 9:21 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-713
> https://issues.apache.org/jira/browse/ATLAS-713
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Current lineage APIs work on the dataset name. With soft delete, there can be 
> more than one entities for the given dataset name. 
> 1. Added new lineage APIs(input graph, output graph, schema) which work on 
> entity id
> 2. Modified current lineage APIs to work on the active entity for the given 
> dataset name
> 3. Modified UI to use the new APIs
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/atlas/AtlasClient.java b3ec95c 
>   dashboardv2/public/js/models/VLineage.js e33488a 
>   dashboardv2/public/js/models/VSchema.js 1f8e0bb 
>   dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js 87adec0 
>   dashboardv2/public/js/views/graph/LineageLayoutView.js 973d091 
>   dashboardv2/public/js/views/schema/SchemaLayoutView.js 35487a5 
>   distro/src/conf/atlas-application.properties 119865d 
>   repository/src/main/java/org/apache/atlas/discovery/HiveLineageService.java 
> 00905d7 
>   repository/src/main/scala/org/apache/atlas/query/ClosureQuery.scala 05dc6a4 
>   repository/src/test/java/org/apache/atlas/BaseHiveRepositoryTest.java 
> 66e1365 
>   
> repository/src/test/java/org/apache/atlas/discovery/HiveLineageServiceTest.java
>  6d5a15a 
>   repository/src/test/scala/org/apache/atlas/query/GremlinTest2.scala 2fd8bb9 
>   server-api/src/main/java/org/apache/atlas/discovery/LineageService.java 
> 8dc36cd 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/AttributeInfo.java 
> 330d1cb 
>   typesystem/src/main/resources/atlas-application.properties a343a20 
>   
> webapp/src/main/java/org/apache/atlas/web/resources/HiveLineageResource.java 
> 9b3fbc9 
>   webapp/src/main/java/org/apache/atlas/web/resources/LineageResource.java 
> PRE-CREATION 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/HiveLineageJerseyResourceIT.java
>  bc02f90 
> 
> Diff: https://reviews.apache.org/r/47225/diff/
> 
> 
> Testing
> ---
> 
> UTs, ITs and end to end test with hive cli
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>