[jira] [Created] (ATLAS-950) Atlas should support Solr that requires Kerberos authentication

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-950:
--

 Summary: Atlas should support Solr that requires Kerberos 
authentication
 Key: ATLAS-950
 URL: https://issues.apache.org/jira/browse/ATLAS-950
 Project: Atlas
  Issue Type: Bug
Reporter: Madhan Neethiraj


Currently Atlas uses Solr version 5.1.0 libraries, which does not support 
Kerberos authentication. To support Solr instances that require Kerberos 
authentication, Atlas should use recent Solr version libraries - like 5.5.1.

Details Solr Security can be found at: 
https://cwiki.apache.org/confluence/display/solr/Securing+Solr



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

[jira] [Comment Edited] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-919 at 6/25/16 1:08 AM:
-

When a deleted table is viewed, property "sd" is not displayed . Can you check 
this? That should also be displayed with a deleted icon. Rest looks fine to me


was (Author: suma.shivaprasad):
When a deleted table is viewed, property "sd" is not displayed . Can you check 
this? That should also be displayed with a deleted icon

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.patch, ATLAS-919.rebased.patch, Screen Shot 
> 2016-06-20 at 3.56.33 PM.png, Screen Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



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

[jira] [Commented] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-919:


When a deleted table is viewed, property "sd" is not displayed . Can you check 
this? That should also be displayed with a deleted icon

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.patch, ATLAS-919.rebased.patch, Screen Shot 
> 2016-06-20 at 3.56.33 PM.png, Screen Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



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

[jira] [Commented] (ATLAS-947) Return state information in inputs and outputs lineage API

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-947:


+1

> Return state information in inputs and outputs lineage API
> --
>
> Key: ATLAS-947
> URL: https://issues.apache.org/jira/browse/ATLAS-947
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-947.patch
>
>
> Return state of entity along with name in lineage inputs and outputs API



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

Re: Review Request 49191: ATLAS-947 Return state information in inputs and outputs lineage API

[Suma Shivaprasad]

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


Ship it!




Ship It!

- Suma Shivaprasad


On June 24, 2016, 10:12 a.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/49191/
> ---
> 
> (Updated June 24, 2016, 10:12 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-947
> https://issues.apache.org/jira/browse/ATLAS-947
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> State is returned in lineage APIs
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 2464646 
>   
> repository/src/main/java/org/apache/atlas/discovery/DataSetLineageService.java
>  a2f47f0 
>   
> repository/src/main/java/org/apache/atlas/discovery/graph/DefaultGraphPersistenceStrategy.java
>  90718ed 
>   
> repository/src/main/java/org/apache/atlas/repository/MetadataRepository.java 
> 43e9f85 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  a4bdef7 
>   
> repository/src/main/scala/org/apache/atlas/query/GraphPersistenceStrategies.scala
>  34d101a 
>   
> repository/src/test/java/org/apache/atlas/discovery/DataSetLineageServiceTest.java
>  3028dde 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
> 90b5815 
>   typesystem/src/test/java/org/apache/atlas/ApplicationPropertiesTest.java 
> 6d43359 
>   typesystem/src/test/resources/atlas-application.properties 28d8af3 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/DataSetLineageJerseyResourceIT.java
>  bc4f239 
> 
> Diff: https://reviews.apache.org/r/49191/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

[jira] [Commented] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server

[Shwetha G S (JIRA)]

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

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

You don't need to show number of pages. Most recent entries are returned in the 
first page. So, instead of showing pages as 1, 2, 3 etc, just show the next 
link which fetches the next page. If we have user requirements, we can change 
this to page count later.

> UI: Audit versioning does not paginate details from Atlas server
> 
>
> Key: ATLAS-847
> URL: https://issues.apache.org/jira/browse/ATLAS-847
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Kalyani Kashikar
>
> In ATLAS-664, the capability to view Audit events was added to the Atlas 
> admin UI. However, currently, the API call made only fetches the first 100 
> events (which is the default if no count is sent). In order to fetch the next 
> set of events, further API calls need to be made to the Audit API, by 
> providing additional parameters in the API. This JIRA is to track the 
> required changes in UI.



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

Re: [VOTE] Release Apache Atlas version 0.7-incubating

[Venkat Ranganathan]

+1
Verified signature/checksums.   Built and ran tests.Note that the zookeeper 
timeouts are too aggressive.   Changed to the following in 
typesystem/src/test/resources/atlas-application.properties for tests to pass

atlas.kafka.zookeeper.session.timeout.ms=3
atlas.kafka.zookeeper.sync.time.ms=1000
atlas.audit.zookeeper.session.timeout.ms=3

Venkat


On 6/23/16, 1:52 AM, "Shwetha Shivalingamurthy" 
 wrote:

>Please vote
>
>Regards,
>Shwetha
>
>
>
>On 22/06/16, 4:03 PM, "Shwetha Shivalingamurthy"
> wrote:
>
>>Hi All,
>>
>>I have created a build for Apache Atlas 0.7-incubating, release candidate
>>0. Thanks to everyone who have contributed to this release and also
>>tested this.
>>
>>The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha):
>>>c0/>https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.0-incubatin
>>g-rc0/
>>
>>The SHA512 checksum of the archive is
>>1B1F16A6 5F7A4EAE 057F410B DC4753B1 F1C0D49B 588B5C91 C8641634 77F0CDF8
>>15F46252
>> 863D6CEA C98863B2 3853F156 B18D212E 30159C47 ACB1E7BA C6F8DB91
>>
>>The commit id (ca9fea712d9a920e5949f16c32a759acd9222f19) to be voted upon:
>>https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=c
>>a9fea712d9a920e5949f16c32a759acd9222f19
>>
>>The tag to be voted upon:
>>https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=log;h=refs
>>/tags/release-0.7-rc0
>>
>>The list of fixed issues:
>>https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=rel
>>ease-log.txt;h=5d72620f1db75c3e032745c3f7c6cefa85b9505c;hb=refs/heads/0.7-
>>incubating
>>
>>Keys to verify the signature of the release artifact are available at:
>>http://www.apache.org/dist/incubator/atlas/KEYS
>>PGP release keys:
>>http://pgp.mit.edu/pks/lookup?op=vindex=0xA0E6F9F5D96BF0FD
>>
>>Note that this is a source only release and we are voting on the source
>>release-0.7-incubating-rc0.
>>
>>Please download, test, and try it out.
>>
>>Vote will be open for at least 72 hours (until the required number of
>>IPMC votes are obtained) till 26th June, 2016 10 AM PDT.
>>
>>[ ] +1 approve
>>[ ] +0 no opinion
>>[ ] -1 disapprove (and reason why)
>>
>>+1 from my side for the release.
>>
>>For folks not familiar with vetting a release, please refer to
>>http://incubator.apache.org/guides/releasemanagement.html#check-list
>>
>>Regards,
>>Shwetha
>

[jira] [Commented] (ATLAS-584) Integrate CSRF prevention filter

[Keval Bhatt (JIRA)]

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

Keval Bhatt commented on ATLAS-584:
---

Added error handling in new patch

> Integrate CSRF prevention filter
> 
>
> Key: ATLAS-584
> URL: https://issues.apache.org/jira/browse/ATLAS-584
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Keval Bhatt
> Attachments: ATLAS-584.1.patch, ATLAS-584.patch
>
>
> Atlas needs to provide protection for CSRF protection.



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

[jira] [Updated] (ATLAS-584) Integrate CSRF prevention filter

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-584:
--
Attachment: ATLAS-584.1.patch

> Integrate CSRF prevention filter
> 
>
> Key: ATLAS-584
> URL: https://issues.apache.org/jira/browse/ATLAS-584
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Keval Bhatt
> Attachments: ATLAS-584.1.patch, ATLAS-584.patch
>
>
> Atlas needs to provide protection for CSRF protection.



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

[jira] [Commented] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-919:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12813065/ATLAS-919.1.patch
  against master revision 7993de0.

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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 378 new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of 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/365//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/365//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/365//console

This message is automatically generated.

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.patch, ATLAS-919.rebased.patch, Screen Shot 
> 2016-06-20 at 3.56.33 PM.png, Screen Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



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

[jira] [Updated] (ATLAS-949) UI improvement for modal and tag styling in table

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-949:
---
Description: 
* Style change for Tag.
* Popup(Modal) beautify for assign term to Asset from search table  and same 
for schema.
* In table by default only one tag is shown and if there are more Tags they are 
shown by "..." button insted of  "Show more" -  "Show less" button.

> UI improvement for modal and tag styling in table
> -
>
> Key: ATLAS-949
> URL: https://issues.apache.org/jira/browse/ATLAS-949
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>
> * Style change for Tag.
> * Popup(Modal) beautify for assign term to Asset from search table  and same 
> for schema.
> * In table by default only one tag is shown and if there are more Tags they 
> are shown by "..." button insted of  "Show more" -  "Show less" button.



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

[jira] [Updated] (ATLAS-949) UI improvement for modal and tag styling in table

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-949:
---
Summary: UI improvement for modal and tag styling in table  (was: UI 
improvement for model and tag styling in table)

> UI improvement for modal and tag styling in table
> -
>
> Key: ATLAS-949
> URL: https://issues.apache.org/jira/browse/ATLAS-949
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>




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

[jira] [Updated] (ATLAS-949) UI improvement for model and tag styling in table

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-949:
---
Summary: UI improvement for model and tag styling in table  (was: UI 
improvement)

> UI improvement for model and tag styling in table
> -
>
> Key: ATLAS-949
> URL: https://issues.apache.org/jira/browse/ATLAS-949
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>




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

[jira] [Updated] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-919:
--
Attachment: ATLAS-919.1.patch

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.patch, ATLAS-919.rebased.patch, Screen Shot 
> 2016-06-20 at 3.56.33 PM.png, Screen Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



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

[jira] [Commented] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[Keval Bhatt (JIRA)]

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

Keval Bhatt commented on ATLAS-919:
---

[~suma.shivaprasad] I have created new patch against master which will solve 
the above problem.

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.patch, ATLAS-919.rebased.patch, Screen Shot 
> 2016-06-20 at 3.56.33 PM.png, Screen Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



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

[jira] [Commented] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar commented on ATLAS-847:


[~shwethags] I am afraid without {{totalCount}} in the first request itself I 
wont be able to create the pagination bar (which contains the number of pages) 
and also for number of pages we require the pageSize.

Generally the following info would be required for creating an efficient 
pagination widget:

* In the first API call OR a separate call get the following info:
** Total number of records : {{totalCount}}
** page size of table : {{pageSize}}, This can be done on client side also
* Once the {{totalCount}} is known, the pagination bar is created with number 
of boxes = {{totalCount}} / {{pageSize}}
* Now if user clicks on 4th page, an API request is made with {{startKey}} = 
{{pageSize}} * 4

If the {{totalCount}} is not available from the server end, creation of the 
pagination bar will not be possible and only client side pagination can be 
supported.



> UI: Audit versioning does not paginate details from Atlas server
> 
>
> Key: ATLAS-847
> URL: https://issues.apache.org/jira/browse/ATLAS-847
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Kalyani Kashikar
>
> In ATLAS-664, the capability to view Audit events was added to the Atlas 
> admin UI. However, currently, the API call made only fetches the first 100 
> events (which is the default if no count is sent). In order to fetch the next 
> set of events, further API calls need to be made to the Audit API, by 
> providing additional parameters in the API. This JIRA is to track the 
> required changes in UI.



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

Re: Review Request 48724: ATLAS-624 : UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Kalyani Kashikar]

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

(Updated June 24, 2016, 11:38 a.m.)


Review request for atlas, Ayub Pathan, Madhan Neethiraj, Mehul Parikh, 
Selvamohan Neethiraj, and Hemanth Yamijala.


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


Repository: atlas


Description
---

Tag search back tick character (`) added and search type changed to 'dsl'


Diffs (updated)
-

  dashboardv2/public/js/views/tag/TagDetailLayoutView.js 7e0f7ed 
  dashboardv2/public/js/views/tag/TagLayoutView.js 42b8078 

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


Testing
---

**Verified following scenarios:** 
1) DSL search gets invoked from Tags on action of "Search Tag".
2) Verified that is we perform "Search Tag" it doesn't invoke fulltext search 
call. 
3) After adding ` in search query - DSL search results are comming correctly.


Thanks,

Kalyani Kashikar

[jira] [Updated] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-624:
---
Attachment: ATLAS-624.2.patch

> UI: Clicking a tag hyperlink should always result in DSL search. In some 
> cases, results in full-text search.
> 
>
> Key: ATLAS-624
> URL: https://issues.apache.org/jira/browse/ATLAS-624
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-624.1.patch, ATLAS-624.2.patch, ATLAS-624.patch
>
>
> UI: Clicking a tag hyperlink should always result in DSL search.
> 1. Create a hive table with a column, Attach a tag to the column.
> 2. Now navigate to the schema tab of hive_table search result.
> 3. Click on the attached tag - This will result in full-text query search of 
> that tag, which will always return empty response. This should be ideally a 
> DSL search query which will show all the entities associated with that tag.
> Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is 
> clicked on atlas UI, this should result in DSL search only.
> UI snapshot for reference: 
> https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC



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

[jira] [Updated] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-624:
---
Attachment: (was: ATLAS-624.2.patch)

> UI: Clicking a tag hyperlink should always result in DSL search. In some 
> cases, results in full-text search.
> 
>
> Key: ATLAS-624
> URL: https://issues.apache.org/jira/browse/ATLAS-624
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-624.1.patch, ATLAS-624.patch
>
>
> UI: Clicking a tag hyperlink should always result in DSL search.
> 1. Create a hive table with a column, Attach a tag to the column.
> 2. Now navigate to the schema tab of hive_table search result.
> 3. Click on the attached tag - This will result in full-text query search of 
> that tag, which will always return empty response. This should be ideally a 
> DSL search query which will show all the entities associated with that tag.
> Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is 
> clicked on atlas UI, this should result in DSL search only.
> UI snapshot for reference: 
> https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC



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

[jira] [Updated] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-624:
---
Attachment: ATLAS-624.2.patch

[~yhemanth] I have rebase the patch. Please use  ATLAS-624.2.patch 

> UI: Clicking a tag hyperlink should always result in DSL search. In some 
> cases, results in full-text search.
> 
>
> Key: ATLAS-624
> URL: https://issues.apache.org/jira/browse/ATLAS-624
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-624.1.patch, ATLAS-624.2.patch, ATLAS-624.patch
>
>
> UI: Clicking a tag hyperlink should always result in DSL search.
> 1. Create a hive table with a column, Attach a tag to the column.
> 2. Now navigate to the schema tab of hive_table search result.
> 3. Click on the attached tag - This will result in full-text query search of 
> that tag, which will always return empty response. This should be ideally a 
> DSL search query which will show all the entities associated with that tag.
> Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is 
> clicked on atlas UI, this should result in DSL search only.
> UI snapshot for reference: 
> https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC



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

[jira] [Commented] (ATLAS-949) UI improvement

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-949:


[~Kalyanikashikar], can you please expand of the JIRA title and provide some 
description about what improvements you are looking at? It would help later for 
reviews, etc. Thanks!

> UI improvement
> --
>
> Key: ATLAS-949
> URL: https://issues.apache.org/jira/browse/ATLAS-949
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>




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

[jira] [Commented] (ATLAS-947) Return state information in inputs and outputs lineage API

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-947:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12813043/ATLAS-947.patch
  against master revision 7993de0.

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

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

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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 378 new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of 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/364//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/364//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/364//console

This message is automatically generated.

> Return state information in inputs and outputs lineage API
> --
>
> Key: ATLAS-947
> URL: https://issues.apache.org/jira/browse/ATLAS-947
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-947.patch
>
>
> Return state of entity along with name in lineage inputs and outputs API



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

[jira] [Resolved] (ATLAS-943) ATlas Build failure: Storm Bridge

[Shwetha G S (JIRA)]

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

Shwetha G S resolved ATLAS-943.
---
Resolution: Not A Problem

Resolving, please re-open if you see the issue again

> ATlas Build failure: Storm Bridge
> -
>
> Key: ATLAS-943
> URL: https://issues.apache.org/jira/browse/ATLAS-943
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: CentOS 7.2.1511
> Maven 3.3.9
> OpenJDK 1.7.0_101
> *fresh atlas clone*
>Reporter: Nigel Jones
>
> [INFO] Apache Atlas Storm Bridge .. FAILURE [02:34 
> min]
> [WARNING] FAILED 
> o.e.j.m.p.JettyWebAppContext@17d43cec{/,file:/home/ibmcloud/src/atlas/webapp/target/atlas-webapp-0.8-incubating-SNAPSHOT/,STARTING}{/home/ibmcloud/src/atlas/webapp/target/atlas-webapp-0.8-incubating-SNAPSHOT.war}:
>  java.lang.OutOfMemoryError: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.nio.HeapByteBuffer.(HeapByteBuffer.java:57)
> at java.nio.ByteBuffer.allocate(ByteBuffer.java:331)
> at kafka.log.SkimpyOffsetMap.(OffsetMap.scala:43)
> at kafka.log.LogCleaner$CleanerThread.(LogCleaner.scala:193)
> at kafka.log.LogCleaner$$anonfun$1.apply(LogCleaner.scala:83)
> at kafka.log.LogCleaner$$anonfun$1.apply(LogCleaner.scala:83)
> at 
>  etc. 
> Heap Space likely needs increasing for clean build/test
> Log file to be attached...



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

[jira] [Commented] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server

[Shwetha G S (JIRA)]

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

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

bq. For pagination it requires total number of records. How do I get that ?
The API doesn't return total number of records currently. Make an API call to 
check if there are any remaining records
bq. Regarding usage of "startKey" the output remain same when I tried 
startKey=any number
For the first page, don't set startKey. For the second page, startKey should be 
equal to the startKey specified in the last record of the previous call(made 
for first page)
bq. the api do not returns audit data in json
Here is the json response from audit API
{noformat}
{  
   "requestId":"qtp966396367-171 - a8c0fada-9c4b-4616-84b2-bccdf90ca54d",
   "events":[  
  {  
 "entityId":"c402c96b-72d8-4d6b-ad15-101b38870140",
 "timestamp":1466764733583,
 "user":"admin",
 "action":"TAG_ADD",
 "details":"Added trait: {\n  
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct\",\n
  \"typeName\":\"tag1\",\n  \"values\":{\n\n  }\n}",
 "eventKey":"c402c96b-72d8-4d6b-ad15-101b38870140:1466764733583",
 "entityDefinition":{  

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{  
   
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
   "id":"c402c96b-72d8-4d6b-ad15-101b38870140",
   "version":0,
   "typeName":"hive_column",
   "state":"ACTIVE"
},
"typeName":"hive_column",
"values":{  
   "name":"id",
   "qualifiedName":"default.t1.id@primary",
   "owner":"sshivalingamurthy",
   "type":"string",
   "table":{  
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"cebdf4a6-838c-45d7-b166-302c0e4c6c48",
  "version":0,
  "typeName":"hive_table",
  "state":"ACTIVE"
   }
},
"traitNames":[  
   "tag1"
],
"traits":{  
   "tag1":{  
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  "typeName":"tag1",
  "values":{  

  }
   }
}
 }
  },
  {  
 "entityId":"c402c96b-72d8-4d6b-ad15-101b38870140",
 "timestamp":1466764387184,
 "user":"sshivalingamurthy",
 "action":"ENTITY_UPDATE",
 "details":"Updated: {\n  
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
  \"id\":{\n
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n 
   \"id\":\"c402c96b-72d8-4d6b-ad15-101b38870140\",\n\"version\":0,\n
\"typeName\":\"hive_column\",\n\"state\":\"ACTIVE\"\n  },\n  
\"typeName\":\"hive_column\",\n  \"values\":{\n\"name\":\"id\",\n
\"description\":null,\n\"qualifiedName\":\"default.t1.id@primary\",\n
\"comment\":null,\n\"owner\":\"sshivalingamurthy\",\n
\"type\":\"string\",\n\"table\":{\n  
\"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n 
 \"id\":\"cebdf4a6-838c-45d7-b166-302c0e4c6c48\",\n  \"version\":0,\n   
   \"typeName\":\"hive_table\",\n  \"state\":\"ACTIVE\"\n}\n  },\n  
\"traitNames\":[\n\n  ],\n  \"traits\":{\n\n  }\n}",
 "eventKey":"c402c96b-72d8-4d6b-ad15-101b38870140:1466764387184",
 "entityDefinition":{  

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{  
   
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
   "id":"c402c96b-72d8-4d6b-ad15-101b38870140",
   "version":0,
   "typeName":"hive_column",
   "state":"ACTIVE"
},
"typeName":"hive_column",
"values":{  
   "name":"id",
   "qualifiedName":"default.t1.id@primary",
   "owner":"sshivalingamurthy",
   "type":"string",
   "table":{  
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"cebdf4a6-838c-45d7-b166-302c0e4c6c48",
  "version":0,
  "typeName":"hive_table",
  "state":"ACTIVE"
   }
},
"traitNames":[  

],
"traits":{  

}
 }
  },
  {  
 "entityId":"c402c96b-72d8-4d6b-ad15-101b38870140",
 "timestamp":1466764385464,
 "user":"sshivalingamurthy",
   

[jira] [Created] (ATLAS-949) UI improvement

[Kalyani Kashikar (JIRA)]

Kalyani Kashikar created ATLAS-949:
--

 Summary: UI improvement
 Key: ATLAS-949
 URL: https://issues.apache.org/jira/browse/ATLAS-949
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Kalyani Kashikar
Assignee: Kalyani Kashikar






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

[jira] [Commented] (ATLAS-947) Return state information in inputs and outputs lineage API

[Shwetha G S (JIRA)]

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

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

Here is a sample json
{noformat}
{  
   requestId:"qtp966396367-171 - 685b8b53-c999-4f78-bcb6-4849a44ec3d6",
   results:{  
  
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  typeName:"__tempQueryResultStruct17",
  values:{  
 vertices:{  
0a0f0924-bf6c-47d7-a93a-f06378896ad7:{  
   
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
   typeName:"__tempQueryResultStruct16",
   values:{  
  qualifiedName:"default.t2@primary",
  vertexId:{  
 
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
 typeName:"__IdType",
 values:{  
guid:"0a0f0924-bf6c-47d7-a93a-f06378896ad7",
state:"ACTIVE",
typeName:"hive_table"
 }
  },
  name:"t2"
   }
},
cebdf4a6-838c-45d7-b166-302c0e4c6c48:{  
   
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
   typeName:"__tempQueryResultStruct16",
   values:{  
  qualifiedName:"default.t1@primary",
  vertexId:{  
 
jsonClass:"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
 typeName:"__IdType",
 values:{  
guid:"cebdf4a6-838c-45d7-b166-302c0e4c6c48",
state:"ACTIVE",
typeName:"hive_table"
 }
  },
  name:"t1"
   }
}
 },
 edges:{  
4b5b2118-c899-40e5-b050-c47a4e3d82b6:[  
   "0a0f0924-bf6c-47d7-a93a-f06378896ad7"
],
cebdf4a6-838c-45d7-b166-302c0e4c6c48:[  
   "4b5b2118-c899-40e5-b050-c47a4e3d82b6"
]
 }
  }
   }
}
{noformat}

> Return state information in inputs and outputs lineage API
> --
>
> Key: ATLAS-947
> URL: https://issues.apache.org/jira/browse/ATLAS-947
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-947.patch
>
>
> Return state of entity along with name in lineage inputs and outputs API



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

[jira] [Updated] (ATLAS-947) Return state information in inputs and outputs lineage API

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-947:
--
Attachment: ATLAS-947.patch

> Return state information in inputs and outputs lineage API
> --
>
> Key: ATLAS-947
> URL: https://issues.apache.org/jira/browse/ATLAS-947
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-947.patch
>
>
> Return state of entity along with name in lineage inputs and outputs API



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

Re: Review Request 49191: ATLAS-947 Return state information in inputs and outputs lineage API

[Shwetha GS]

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

(Updated June 24, 2016, 10:12 a.m.)


Review request for atlas.


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


Repository: atlas


Description
---

State is returned in lineage APIs


Diffs (updated)
-

  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
2464646 
  
repository/src/main/java/org/apache/atlas/discovery/DataSetLineageService.java 
a2f47f0 
  
repository/src/main/java/org/apache/atlas/discovery/graph/DefaultGraphPersistenceStrategy.java
 90718ed 
  repository/src/main/java/org/apache/atlas/repository/MetadataRepository.java 
43e9f85 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
 a4bdef7 
  
repository/src/main/scala/org/apache/atlas/query/GraphPersistenceStrategies.scala
 34d101a 
  
repository/src/test/java/org/apache/atlas/discovery/DataSetLineageServiceTest.java
 3028dde 
  typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
90b5815 
  typesystem/src/test/java/org/apache/atlas/ApplicationPropertiesTest.java 
6d43359 
  typesystem/src/test/resources/atlas-application.properties 28d8af3 
  
webapp/src/test/java/org/apache/atlas/web/resources/DataSetLineageJerseyResourceIT.java
 bc4f239 

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


Testing
---

UTs


Thanks,

Shwetha GS

Review Request 49191: ATLAS-947 Return state information in inputs and outputs lineage API

[Shwetha GS]

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

Review request for atlas.


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


Repository: atlas


Description
---

State is returned in lineage APIs


Diffs
-

  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
2464646 
  
repository/src/main/java/org/apache/atlas/discovery/DataSetLineageService.java 
a2f47f0 
  
repository/src/main/java/org/apache/atlas/discovery/graph/DefaultGraphPersistenceStrategy.java
 90718ed 
  repository/src/main/java/org/apache/atlas/repository/MetadataRepository.java 
43e9f85 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
 a4bdef7 
  
repository/src/main/scala/org/apache/atlas/query/GraphPersistenceStrategies.scala
 34d101a 
  
repository/src/test/java/org/apache/atlas/discovery/DataSetLineageServiceTest.java
 3028dde 
  typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
90b5815 
  typesystem/src/test/java/org/apache/atlas/ApplicationPropertiesTest.java 
6d43359 
  typesystem/src/test/resources/atlas-application.properties 28d8af3 
  
webapp/src/test/java/org/apache/atlas/web/resources/DataSetLineageJerseyResourceIT.java
 bc4f239 

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


Testing
---

UTs


Thanks,

Shwetha GS

Re: [VOTE] Release Apache Atlas version 0.7-incubating

[Hemanth Yamijala]

Looks like it is specific to pentaho-aggdesigner-algorithm as Julian mentions 
on this thread - 
http://mail-archives.apache.org/mod_mbox/calcite-dev/201506.mbox/%3c1660003108.2156893.1434125478536.javamail.ya...@mail.yahoo.com%3E

Why it only comes for some folks is a mystery. 

I cleared org/pentaho from my .m2 repository and built it, it got downloaded 
fine from conjars.org. It seems like it picks up conjars due to calcite’s pom 
which is also a transitive dependency for Hive.

Thanks
hemanth




On 6/24/16, 2:13 PM, "Srikanth Sundarrajan"  wrote:

>Ah! didn't realize that I had the same issue back then as well. Will try on
>a different host & revert..
>
>Regards
>Srikanth Sundarrajan
>
>On Fri, Jun 24, 2016 at 2:11 PM Hemanth Yamijala 
>wrote:
>
>> Srikanth,
>> It looks like this is a similar issue you reported during the 0.6 release
>> as well [1]. Seems like an environment specific problem.
>>
>> [1] - http://markmail.org/thread/aiiugufhniv2n6gy
>>
>> Is there something similar to the environments where you are trying the
>> build?
>>
>> Thanks
>> hemanth
>>
>>
>>
>>
>> On 6/24/16, 2:01 PM, "Srikanth Sundarrajan"  wrote:
>>
>> >On Fri, Jun 24, 2016 at 1:59 PM Srikanth Sundarrajan 
>> >wrote:
>> >
>> >> Team,
>> >> I am unable to build from source. Seems like a transitive dependency
>> >> is not available on standard maven repos included by default in the
>> parent
>> >> pom. I am unable to complete the verification process to vote on the
>> >> release.
>> >>
>> >> Signature - OK
>> >> Checksums - OK
>> >> Build - Failed (details below)
>> >> Disclaimer, Licenses & Notices - OK
>> >> Rat check - clean
>> >>
>> >> Build Error:  (Detailed logs with debug, attached)
>> >> [ERROR] Failed to execute goal on project hive-bridge: Could not resolve
>> >> dependencies for project
>> org.apache.atlas:hive-bridge:jar:0.7-incubating:
>> >> Failure to find
>> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
>> >> in http://repo1.maven.org/maven2 was cached in the local repository,
>> >> resolution will not be reattempted until the update interval of central
>> has
>> >> elapsed or updates are forced -> [Help 1]
>> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute
>> >> goal on project hive-bridge: Could not resolve dependencies for project
>> >> org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
>> >> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
>> >> http://repo1.maven.org/maven2 was cached in the local repository,
>> >> resolution will not be reattempted until the update interval of central
>> has
>> >> elapsed or updates are forced
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> >> at
>> >>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
>> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
>> >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>> >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> at
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >> at
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >> at java.lang.reflect.Method.invoke(Method.java:606)
>> >> at
>> >>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> >> at
>> >>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> >> at
>> >>
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> >> at
>> >>
>> 

Re: [VOTE] Release Apache Atlas version 0.7-incubating

[Jean-Baptiste Onofré]

Did you add the staging repo itself in the pom.xml ?

Regards
JB

On 06/24/2016 10:31 AM, Srikanth Sundarrajan wrote:

On Fri, Jun 24, 2016 at 1:59 PM Srikanth Sundarrajan 
wrote:


Team,
 I am unable to build from source. Seems like a transitive dependency
is not available on standard maven repos included by default in the parent
pom. I am unable to complete the verification process to vote on the
release.

Signature - OK
Checksums - OK
Build - Failed (details below)
Disclaimer, Licenses & Notices - OK
Rat check - clean

Build Error:  (Detailed logs with debug, attached)
[ERROR] Failed to execute goal on project hive-bridge: Could not resolve
dependencies for project org.apache.atlas:hive-bridge:jar:0.7-incubating:
Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
in http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal on project hive-bridge: Could not resolve dependencies for project
org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced
 at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
 at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
 at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
 at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
 at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
 at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
 at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
 at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.project.DependencyResolutionException: Could
not resolve dependencies for project
org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced
 at
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:198)
 at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
 ... 22 more
Caused by: org.eclipse.aether.resolution.DependencyResolutionException:
Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
in http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced
 at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384)
 at
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:192)
 ... 23 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException:
Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
in http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be 

Re: [VOTE] Release Apache Atlas version 0.7-incubating

[Srikanth Sundarrajan]

Ah! didn't realize that I had the same issue back then as well. Will try on
a different host & revert..

Regards
Srikanth Sundarrajan

On Fri, Jun 24, 2016 at 2:11 PM Hemanth Yamijala 
wrote:

> Srikanth,
> It looks like this is a similar issue you reported during the 0.6 release
> as well [1]. Seems like an environment specific problem.
>
> [1] - http://markmail.org/thread/aiiugufhniv2n6gy
>
> Is there something similar to the environments where you are trying the
> build?
>
> Thanks
> hemanth
>
>
>
>
> On 6/24/16, 2:01 PM, "Srikanth Sundarrajan"  wrote:
>
> >On Fri, Jun 24, 2016 at 1:59 PM Srikanth Sundarrajan 
> >wrote:
> >
> >> Team,
> >> I am unable to build from source. Seems like a transitive dependency
> >> is not available on standard maven repos included by default in the
> parent
> >> pom. I am unable to complete the verification process to vote on the
> >> release.
> >>
> >> Signature - OK
> >> Checksums - OK
> >> Build - Failed (details below)
> >> Disclaimer, Licenses & Notices - OK
> >> Rat check - clean
> >>
> >> Build Error:  (Detailed logs with debug, attached)
> >> [ERROR] Failed to execute goal on project hive-bridge: Could not resolve
> >> dependencies for project
> org.apache.atlas:hive-bridge:jar:0.7-incubating:
> >> Failure to find
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
> >> in http://repo1.maven.org/maven2 was cached in the local repository,
> >> resolution will not be reattempted until the update interval of central
> has
> >> elapsed or updates are forced -> [Help 1]
> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> >> goal on project hive-bridge: Could not resolve dependencies for project
> >> org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
> >> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
> >> http://repo1.maven.org/maven2 was cached in the local repository,
> >> resolution will not be reattempted until the update interval of central
> has
> >> elapsed or updates are forced
> >> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
> >> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> >> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> >> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> >> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> at
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:606)
> >> at
> >>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> >> at
> >>
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> >> at
> >>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> >> at
> >>
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> >> Caused by: org.apache.maven.project.DependencyResolutionException: Could
> >> not resolve dependencies for project
> >> org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
> >> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
> >> http://repo1.maven.org/maven2 was cached in the local repository,
> >> resolution will not be reattempted until the update interval of central
> has
> >> elapsed or updates are forced
> >> at
> >>
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:198)
> >> at
> >>
> 

Re: [VOTE] Release Apache Atlas version 0.7-incubating

[Hemanth Yamijala]

Srikanth,
It looks like this is a similar issue you reported during the 0.6 release as 
well [1]. Seems like an environment specific problem.

[1] - http://markmail.org/thread/aiiugufhniv2n6gy

Is there something similar to the environments where you are trying the build?

Thanks
hemanth 




On 6/24/16, 2:01 PM, "Srikanth Sundarrajan"  wrote:

>On Fri, Jun 24, 2016 at 1:59 PM Srikanth Sundarrajan 
>wrote:
>
>> Team,
>> I am unable to build from source. Seems like a transitive dependency
>> is not available on standard maven repos included by default in the parent
>> pom. I am unable to complete the verification process to vote on the
>> release.
>>
>> Signature - OK
>> Checksums - OK
>> Build - Failed (details below)
>> Disclaimer, Licenses & Notices - OK
>> Rat check - clean
>>
>> Build Error:  (Detailed logs with debug, attached)
>> [ERROR] Failed to execute goal on project hive-bridge: Could not resolve
>> dependencies for project org.apache.atlas:hive-bridge:jar:0.7-incubating:
>> Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
>> in http://repo1.maven.org/maven2 was cached in the local repository,
>> resolution will not be reattempted until the update interval of central has
>> elapsed or updates are forced -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal on project hive-bridge: Could not resolve dependencies for project
>> org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
>> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
>> http://repo1.maven.org/maven2 was cached in the local repository,
>> resolution will not be reattempted until the update interval of central has
>> elapsed or updates are forced
>> at
>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: org.apache.maven.project.DependencyResolutionException: Could
>> not resolve dependencies for project
>> org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
>> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
>> http://repo1.maven.org/maven2 was cached in the local repository,
>> resolution will not be reattempted until the update interval of central has
>> elapsed or updates are forced
>> at
>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:198)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
>> ... 22 more
>> Caused by: org.eclipse.aether.resolution.DependencyResolutionException:
>> Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
>> in http://repo1.maven.org/maven2 was cached in the local repository,
>> resolution will not be reattempted until the update interval of central has
>> elapsed or updates are forced
>> at
>> 

Re: [VOTE] Release Apache Atlas version 0.7-incubating

[Srikanth Sundarrajan]

On Fri, Jun 24, 2016 at 1:59 PM Srikanth Sundarrajan 
wrote:

> Team,
> I am unable to build from source. Seems like a transitive dependency
> is not available on standard maven repos included by default in the parent
> pom. I am unable to complete the verification process to vote on the
> release.
>
> Signature - OK
> Checksums - OK
> Build - Failed (details below)
> Disclaimer, Licenses & Notices - OK
> Rat check - clean
>
> Build Error:  (Detailed logs with debug, attached)
> [ERROR] Failed to execute goal on project hive-bridge: Could not resolve
> dependencies for project org.apache.atlas:hive-bridge:jar:0.7-incubating:
> Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
> in http://repo1.maven.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project hive-bridge: Could not resolve dependencies for project
> org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
> http://repo1.maven.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could
> not resolve dependencies for project
> org.apache.atlas:hive-bridge:jar:0.7-incubating: Failure to find
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
> http://repo1.maven.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:198)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
> ... 22 more
> Caused by: org.eclipse.aether.resolution.DependencyResolutionException:
> Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
> in http://repo1.maven.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384)
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:192)
> ... 23 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException:
> Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
> in http://repo1.maven.org/maven2 was cached in the local repository,

Re: [VOTE] Release Apache Atlas version 0.7-incubating

[Ismaël Mejía]

+1 (non-binding),

It compiles, some tests fail (ubuntu 16.04 java: oracle-jdk-8):
Tests run: 203, Failures: 5, Errors: 0, Skipped: 26

Please don't forget to publish the artifacts on Maven Central (as it
happened with 0.6), those are essential for people writing integrations or
other products based on Atlas.

​Ismaël​


On Thu, Jun 23, 2016 at 11:53 PM, Selvamohan Neethiraj 
wrote:

> +1
>
> Downloaded source ;  Able to build successfully ; Validated the signature
> and checksum ….
>
> Thanks,
> Selva-
>
> From:  Shwetha Shivalingamurthy 
> Reply-To:  "dev@atlas.incubator.apache.org" <
> dev@atlas.incubator.apache.org>
> Date:  Wednesday, June 22, 2016 at 6:33 AM
> To:  "dev@atlas.incubator.apache.org" 
> Subject:  [VOTE] Release Apache Atlas version 0.7-incubating
>
> Hi All,
>
> I have created a build for Apache Atlas 0.7-incubating, release candidate
> 0. Thanks to everyone who have contributed to this release and also tested
> this.
>
> The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha):
> <
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.0-incubating-rc0/
> >
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.0-incubating-rc0/
>
> The SHA512 checksum of the archive is
> 1B1F16A6 5F7A4EAE 057F410B DC4753B1 F1C0D49B 588B5C91 C8641634 77F0CDF8
> 15F46252
>  863D6CEA C98863B2 3853F156 B18D212E 30159C47 ACB1E7BA C6F8DB91
>
> The commit id (ca9fea712d9a920e5949f16c32a759acd9222f19) to be voted upon:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=ca9fea712d9a920e5949f16c32a759acd9222f19
>
> The tag to be voted upon:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=log;h=refs/tags/release-0.7-rc0
>
> The list of fixed issues:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;h=5d72620f1db75c3e032745c3f7c6cefa85b9505c;hb=refs/heads/0.7-incubating
>
> Keys to verify the signature of the release artifact are available at:
> http://www.apache.org/dist/incubator/atlas/KEYS
> PGP release keys:
> http://pgp.mit.edu/pks/lookup?op=vindex=0xA0E6F9F5D96BF0FD
>
> Note that this is a source only release and we are voting on the source
> release-0.7-incubating-rc0.
>
> Please download, test, and try it out.
>
> Vote will be open for at least 72 hours (until the required number of IPMC
> votes are obtained) till 26th June, 2016 10 AM PDT.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> +1 from my side for the release.
>
> For folks not familiar with vetting a release, please refer to
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>
> Regards,
> Shwetha
>
>
>

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

[Shwetha G S (JIRA)]

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

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

Working on ATLAS-947, will give a patch and sample json that you can work with.

When are the cases where guid is not present in vertices object. If there is no 
guid, what API call is made to get the details. According to me, there 
shouldn't be any case where guid is not present in vertices object.

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



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

[jira] [Assigned] (ATLAS-947) Return state information in inputs and outputs lineage API

[Shwetha G S (JIRA)]

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

Shwetha G S reassigned ATLAS-947:
-

Assignee: Shwetha G S

> Return state information in inputs and outputs lineage API
> --
>
> Key: ATLAS-947
> URL: https://issues.apache.org/jira/browse/ATLAS-947
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
>
> Return state of entity along with name in lineage inputs and outputs API



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

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

[Apache Jenkins Server]

See 

Changes:

[hyamijala] ATLAS-806 Create default taxonomy at server startup (jspeidel via

--
[...truncated 3048 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 9 Scala sources and 49 Java sources to 

[WARNING] 
:129:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("adding entities={}", entities);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] 
:292:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("updating entity {}", entitiesUpdated);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[WARNING] 2 warnings
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 49 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 8 Scala sources and 27 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-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 27 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and