Re: [VOTE] Release Apache Atlas version 1.2.0 - rc3

2019-06-04 Thread Srikanth Venkat
+1 for Atlas 1.2 rc3

Thanks to Atlas community for the timely much needed fixes in this release!

Cheers
Srikanth

Srikanth Venkat
Senior Director - Product Management
Cloudera


On Tue, Jun 4, 2019 at 8:53 PM Le Ma  wrote:

> + 1 for Apache Atlas 1.2.0 # 3
>
> - built successfully from the source tar file
> - ran quick_start_v1, data successfully shows up
> - validate basic search functionality
> - add/delete classification, results are expected.
>
> thanks,
> Le
>
> Ramesh Mani  于2019年6月4日周二 上午8:44写道:
>
> > +1  for Apache Atlas 1.2.0 rc3
> >
> > - Built successfully from the source tar file
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
> > - Verified the PGP and SHA
> >
> > Thanks,
> > Ramesh
> >
> > On Mon, Jun 3, 2019 at 5:10 AM Binit Gutka <
> > binit.gu...@freestoneinfotech.com> wrote:
> >
> > > +1 Release Apache Atlas 1.2.0 release candidate #3
> > >
> > > - Verified PGP signature.
> > > - Built successfully from the source tar file
> > > - Ran quick start and validated basic functionality.
> > > - Tested Atlas UI packaging in embedded-hbase mode.
> > > - Performed few basic search.
> > > - Lineage Export functionality tested.
> > > - Lineage Pan, Zoom, Filter, Search and settings functionality tested.
> > >
> > > Thanks.
> > >
> > > On Mon, Jun 3, 2019 at 1:41 PM Nixon Rodrigues <
> > > nixon.rodrig...@freestoneinfotech.com> wrote:
> > >
> > > > Atlas team,
> > > >
> > > > Apache Atlas 1.2.0 release candidate #3 is now available for a vote
> > > within
> > > > dev community.
> > > >
> > > > Following commits went into branch-1.0 since the last release
> candidate
> > > > (rc2):
> > > >
> > > > ATLAS-3180:- New Bulk retrieval API with servicetype parameter.
> > > > ATLAS-3227:- Bulk delete does not delete the indexes properly.
> > > >
> > > > Links to the release artifacts are given below. Please review and
> vote.
> > > >
> > > > The vote will be open for at least 72 hours or until necessary votes
> > are
> > > > reached.
> > > >   [ ] +1 approve
> > > >   [ ] +0 no opinion
> > > >   [ ] -1 disapprove (and reason why)
> > > >
> > > >
> > > > Thanks,
> > > > Nixon Rodrigues
> > > >
> > > >
> > > > List of issues addressed in this release:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC
> > > >
> > > > Git tag for the release:
> > > > https://github.com/apache/atlas/releases/tag/release-1.2.0-rc3
> > > >
> > > > Sources for the release:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
> > > >
> > > > Source release verification:
> > > >   PGP Signature:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.asc
> > > >   MD5 Hash:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.md5
> > > >   SHA512 Hash:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.sha512
> > > >
> > > > Keys to verify the signature of the release artifacts are available
> at:
> > > > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> > > >
> > >
> > >
> > > --
> > > *Thanks,*
> > > *Binit.*
> > >
> >
>


Re: [VOTE] Release Apache Atlas version 1.2.0 - rc3

2019-06-04 Thread Le Ma
+ 1 for Apache Atlas 1.2.0 # 3

- built successfully from the source tar file
- ran quick_start_v1, data successfully shows up
- validate basic search functionality
- add/delete classification, results are expected.

thanks,
Le

Ramesh Mani  于2019年6月4日周二 上午8:44写道:

> +1  for Apache Atlas 1.2.0 rc3
>
> - Built successfully from the source tar file
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
> - Verified the PGP and SHA
>
> Thanks,
> Ramesh
>
> On Mon, Jun 3, 2019 at 5:10 AM Binit Gutka <
> binit.gu...@freestoneinfotech.com> wrote:
>
> > +1 Release Apache Atlas 1.2.0 release candidate #3
> >
> > - Verified PGP signature.
> > - Built successfully from the source tar file
> > - Ran quick start and validated basic functionality.
> > - Tested Atlas UI packaging in embedded-hbase mode.
> > - Performed few basic search.
> > - Lineage Export functionality tested.
> > - Lineage Pan, Zoom, Filter, Search and settings functionality tested.
> >
> > Thanks.
> >
> > On Mon, Jun 3, 2019 at 1:41 PM Nixon Rodrigues <
> > nixon.rodrig...@freestoneinfotech.com> wrote:
> >
> > > Atlas team,
> > >
> > > Apache Atlas 1.2.0 release candidate #3 is now available for a vote
> > within
> > > dev community.
> > >
> > > Following commits went into branch-1.0 since the last release candidate
> > > (rc2):
> > >
> > > ATLAS-3180:- New Bulk retrieval API with servicetype parameter.
> > > ATLAS-3227:- Bulk delete does not delete the indexes properly.
> > >
> > > Links to the release artifacts are given below. Please review and vote.
> > >
> > > The vote will be open for at least 72 hours or until necessary votes
> are
> > > reached.
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove (and reason why)
> > >
> > >
> > > Thanks,
> > > Nixon Rodrigues
> > >
> > >
> > > List of issues addressed in this release:
> > >
> > >
> >
> https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC
> > >
> > > Git tag for the release:
> > > https://github.com/apache/atlas/releases/tag/release-1.2.0-rc3
> > >
> > > Sources for the release:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
> > >
> > > Source release verification:
> > >   PGP Signature:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.asc
> > >   MD5 Hash:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.md5
> > >   SHA512 Hash:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.sha512
> > >
> > > Keys to verify the signature of the release artifacts are available at:
> > > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> > >
> >
> >
> > --
> > *Thanks,*
> > *Binit.*
> >
>


[jira] [Commented] (ATLAS-3086) Regression : Atlas Hive Hook doesn't capture insert into table values() queries

2019-06-04 Thread Yu-Hsin Chang (JIRA)


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

Yu-Hsin Chang commented on ATLAS-3086:
--

This is an expected behavior. Check ATLAS-3188

> Regression : Atlas Hive Hook doesn't capture insert into table values() 
> queries
> ---
>
> Key: ATLAS-3086
> URL: https://issues.apache.org/jira/browse/ATLAS-3086
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: trunk
>
>
> Atlas Hive Hook doesn't capture the query "insert into table values()" . This 
> is a regression as this event was captured in 0.8
> Other queries like 
> "from table1 a insert overwrite table bkp_table select a.id",
> "insert into tableB select c1,c2 from tableA" , information is captured and 
> lineage is created in 1.0



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


[jira] [Updated] (ATLAS-3198) update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements

2019-06-04 Thread Yu-Hsin Chang (JIRA)


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

Yu-Hsin Chang updated ATLAS-3198:
-

Code review link: [https://reviews.apache.org/r/70784/]

> update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements 
> -
>
> Key: ATLAS-3198
> URL: https://issues.apache.org/jira/browse/ATLAS-3198
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Yu-Hsin Chang
>Priority: Critical
> Fix For: trunk
>
> Attachments: ATLAS-3198.patch, ATLAS_HOOK and ATLAS_ENTITIES 
> messages.xlsx
>
>
> With the recent changes, we have now stopped ingesting simple insert 
> operations since with this operation, there is no change in the metadata. 
> Ideally, we should be doing similar improvements w.r.t. update, delete and 
> truncate operations too. 
> Currently, for update/delete/truncate, we are pushing messages in both 
> ATLAS_HOOK as well as ATLAS_ENTITIES topic, which can be avoided. 
> If we stop ingesting updates/deletes/truncates, it will further help us 
> reduce the burden on Kafka and save CPU cycles
> I have created and attached an excel sheet, with the list of operations and 
> the corresponding messages generated in ATLAS_HOOK and ATLAS_ENTITIES topic, 
> along with suitable comments. 



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


Re: Review Request 70745: ATLAS-3243 :- Atlas to support UI access via Knox Trusted Proxy

2019-06-04 Thread Sarath Subramanian

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


Fix it, then Ship it!





webapp/src/main/java/org/apache/atlas/web/filters/AtlasAuthenticationFilter.java
Lines 347 (patched)


nit: remove additional new line(s). Same for line #763, 764


- Sarath Subramanian


On June 4, 2019, 7:52 a.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70745/
> ---
> 
> (Updated June 4, 2019, 7:52 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nikhil Bonte, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3243
> https://issues.apache.org/jira/browse/ATLAS-3243
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch provides changes required to support UI access Atlas via Trusted 
> Knox proxy, there some changes required in AtlasAuthenticationFilter.
> 
> 
> Diffs
> -
> 
>   
> webapp/src/main/java/org/apache/atlas/web/filters/AtlasAuthenticationFilter.java
>  782b5a06c 
> 
> 
> Diff: https://reviews.apache.org/r/70745/diff/2/
> 
> 
> Testing
> ---
> 
> Tested Atlas different scenario's
> 
> 1) curl call with kerberos.
> 2) curl Simple basic heaeder
> 3) Atlas login page.
> 4) curl with trusted proxy 
> 4) Atlas UI with Trusted Proxy with Knox shiroprovider.
> 5) Atlas UI with Trusted proxy with KnoxSSOCoookieProvider.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>



[jira] [Updated] (ATLAS-3198) update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements

2019-06-04 Thread Yu-Hsin Chang (JIRA)


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

Yu-Hsin Chang updated ATLAS-3198:
-
Attachment: ATLAS-3198.patch

> update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements 
> -
>
> Key: ATLAS-3198
> URL: https://issues.apache.org/jira/browse/ATLAS-3198
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Yu-Hsin Chang
>Priority: Critical
> Fix For: trunk
>
> Attachments: ATLAS-3198.patch, ATLAS_HOOK and ATLAS_ENTITIES 
> messages.xlsx
>
>
> With the recent changes, we have now stopped ingesting simple insert 
> operations since with this operation, there is no change in the metadata. 
> Ideally, we should be doing similar improvements w.r.t. update, delete and 
> truncate operations too. 
> Currently, for update/delete/truncate, we are pushing messages in both 
> ATLAS_HOOK as well as ATLAS_ENTITIES topic, which can be avoided. 
> If we stop ingesting updates/deletes/truncates, it will further help us 
> reduce the burden on Kafka and save CPU cycles
> I have created and attached an excel sheet, with the list of operations and 
> the corresponding messages generated in ATLAS_HOOK and ATLAS_ENTITIES topic, 
> along with suitable comments. 



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


Re: [VOTE] Release Apache Atlas version 1.2.0 - rc3

2019-06-04 Thread Ramesh Mani
+1  for Apache Atlas 1.2.0 rc3

- Built successfully from the source tar file
https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
- Verified the PGP and SHA

Thanks,
Ramesh

On Mon, Jun 3, 2019 at 5:10 AM Binit Gutka <
binit.gu...@freestoneinfotech.com> wrote:

> +1 Release Apache Atlas 1.2.0 release candidate #3
>
> - Verified PGP signature.
> - Built successfully from the source tar file
> - Ran quick start and validated basic functionality.
> - Tested Atlas UI packaging in embedded-hbase mode.
> - Performed few basic search.
> - Lineage Export functionality tested.
> - Lineage Pan, Zoom, Filter, Search and settings functionality tested.
>
> Thanks.
>
> On Mon, Jun 3, 2019 at 1:41 PM Nixon Rodrigues <
> nixon.rodrig...@freestoneinfotech.com> wrote:
>
> > Atlas team,
> >
> > Apache Atlas 1.2.0 release candidate #3 is now available for a vote
> within
> > dev community.
> >
> > Following commits went into branch-1.0 since the last release candidate
> > (rc2):
> >
> > ATLAS-3180:- New Bulk retrieval API with servicetype parameter.
> > ATLAS-3227:- Bulk delete does not delete the indexes properly.
> >
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove (and reason why)
> >
> >
> > Thanks,
> > Nixon Rodrigues
> >
> >
> > List of issues addressed in this release:
> >
> >
> https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC
> >
> > Git tag for the release:
> > https://github.com/apache/atlas/releases/tag/release-1.2.0-rc3
> >
> > Sources for the release:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
> >
> > Source release verification:
> >   PGP Signature:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.asc
> >   MD5 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.md5
> >   SHA512 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.sha512
> >
> > Keys to verify the signature of the release artifacts are available at:
> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> >
>
>
> --
> *Thanks,*
> *Binit.*
>


[jira] [Commented] (ATLAS-3260) When importing KAFKA metadata, the following error is reported

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-3260:
---

[~langxia], can you verify the kafka version, it should be kafka_2.11-2.0.0.jar

> When importing KAFKA metadata, the following error is reported
> --
>
> Key: ATLAS-3260
> URL: https://issues.apache.org/jira/browse/ATLAS-3260
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: He sheng
>Priority: Major
>
> Adding Kafka topic ATLAS_HOOK
> Exception in thread "main" java.lang.NoSuchMethodError: 
> kafka.utils.ZkUtils.getTopicPartitionCount(Ljava/lang/String;)Lscala/Option;
>     at 
> org.apache.atlas.kafka.bridge.KafkaBridge.getTopicEntity(KafkaBridge.java:231)
>     at 
> org.apache.atlas.kafka.bridge.KafkaBridge.createOrUpdateTopic(KafkaBridge.java:196)
>     at 
> org.apache.atlas.kafka.bridge.KafkaBridge.importTopic(KafkaBridge.java:182)
>     at org.apache.atlas.kafka.bridge.KafkaBridge.main(KafkaBridge.java:139)
> Failed to import Kafka Data Model!!!   
> thread
> !moz-extension://8260c77a-a03d-49f1-8b6d-70c335e701e7/static/drowDown.svg!
> [THred]
> !moz-extension://8260c77a-a03d-49f1-8b6d-70c335e701e7/static/sound.svg!
> 名词线; 丝; 线索; 绪; 细线; 缕; 运作; 丝状物
> 动词缕; 纫
> 定义
> 名词a long, thin strand of cotton, nylon, or other fibers used in sewing or 
> weaving.
> 动词pass a thread through the eye of (a needle) or through the needle and 
> guides of (a sewing machine).
> 同义词
> 名词cotton; filament; fiber; yarn; string; twine
> 动词pass; string; work; ease; push; poke
> 示例
> She sighed and let her hands rest on her lap, her fingers absently playing 
> with a loose *thread* of cotton.



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


[jira] [Commented] (ATLAS-3241) AtlasClientV2Test.java invalid directory

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-3241:
---

[~Zep], Thanks for the pull request. I have merged the changes.

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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


[jira] [Commented] (ATLAS-3241) AtlasClientV2Test.java invalid directory

2019-06-04 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-3241:


Commit 8b722eb87128660d3810535e206b693fc8f9419f in atlas's branch 
refs/heads/master from Diego Marino Monetti
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8b722eb ]

ATLAS-3241: Fix Invalid package name for AtlasClientV2Test.java


> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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


[jira] [Comment Edited] (ATLAS-3241) AtlasClientV2Test.java invalid directory

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian edited comment on ATLAS-3241 at 6/4/19 3:00 PM:
---

Precommit - 
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1166/console]


was (Author: sarath.ku...@gmail.com):
Precommit - 
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1165/console]

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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


[jira] [Commented] (ATLAS-3258) Update apache-rat-plugin to 0.13

2019-06-04 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-3258:


Commit c34e2411e9341871405f1520df99e88616362372 in atlas's branch 
refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c34e241 ]

ATLAS-3258: Update apache-rat-plugin to 0.13


> Update apache-rat-plugin to 0.13
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


Re: Review Request 70745: ATLAS-3243 :- Atlas to support UI access via Knox Trusted Proxy

2019-06-04 Thread Nixon Rodrigues

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

(Updated June 4, 2019, 2:52 p.m.)


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


Changes
---

Updated the patch with fix for Atlas UI with trusted proxy.


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


Repository: atlas


Description
---

This patch provides changes required to support UI access Atlas via Trusted 
Knox proxy, there some changes required in AtlasAuthenticationFilter.


Diffs (updated)
-

  
webapp/src/main/java/org/apache/atlas/web/filters/AtlasAuthenticationFilter.java
 782b5a06c 


Diff: https://reviews.apache.org/r/70745/diff/2/

Changes: https://reviews.apache.org/r/70745/diff/1-2/


Testing
---

Tested Atlas different scenario's

1) curl call with kerberos.
2) curl Simple basic heaeder
3) Atlas login page.
4) curl with trusted proxy 
4) Atlas UI with Trusted Proxy with Knox shiroprovider.
5) Atlas UI with Trusted proxy with KnoxSSOCoookieProvider.


Thanks,

Nixon Rodrigues



[jira] [Commented] (ATLAS-3258) Update apache-rat-plugin to 0.13

2019-06-04 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj commented on ATLAS-3258:
-

+1 for the patch.

> Update apache-rat-plugin to 0.13
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

2019-06-04 Thread Bolke de Bruin (JIRA)


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

Bolke de Bruin commented on ATLAS-3153:
---

[~saqeeb.shaikh136] Let me verify.

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Labels: authentication, authorization
> Attachments: 0001-ATLAS-3153-Add-keycloak-authentication.patch, 
> application.log, keycloak.json, openid_connect_atlas.md
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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


[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

2019-06-04 Thread Saqeeb Shaikh (JIRA)


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

Saqeeb Shaikh commented on ATLAS-3153:
--

[~bolke],

I tested the patch on HDP cluster with kerberos ON, encountered issues while 
forwarding the request to keycloak challenge page. The same setup on local 
(without kerberos ON) works well. Attached logs and keycloak.json. Can you 
please verify this setup on your end with kerberos ON.

PFA [^keycloak.json]  [^application.log]

^cc:[~madhan.neethiraj]^

 

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Labels: authentication, authorization
> Attachments: 0001-ATLAS-3153-Add-keycloak-authentication.patch, 
> application.log, keycloak.json, openid_connect_atlas.md
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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


[jira] [Updated] (ATLAS-3153) Support OpenID Connect directly rather than through Knox

2019-06-04 Thread Saqeeb Shaikh (JIRA)


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

Saqeeb Shaikh updated ATLAS-3153:
-
Attachment: application.log
keycloak.json

> Support OpenID Connect directly rather than through Knox
> 
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.0.0
>Reporter: Bolke de Bruin
>Priority: Major
>  Labels: authentication, authorization
> Attachments: 0001-ATLAS-3153-Add-keycloak-authentication.patch, 
> application.log, keycloak.json, openid_connect_atlas.md
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO 
> interoperability to Apache Knox. Knox uses JWT verification which could 
> easily be extended to allow for direct OpenID Connect support and doesn't 
> require organizations to deploy Knox.
> Required changes:
>  * Pickup bearer token from headers
>  * Improve and standardize redirecting
>  * Optionally: obtain certificates from well_known uri
>  * Optionally: obtain user groups from userinfo endpoint rather than UGI



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


[jira] [Updated] (ATLAS-3254) Atlas entity with large array of refs causes performance issues for lineage

2019-06-04 Thread Adam Rempter (JIRA)


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

Adam Rempter updated ATLAS-3254:

Issue Type: Bug  (was: Improvement)

> Atlas entity with large array of refs causes performance issues for lineage
> ---
>
> Key: ATLAS-3254
> URL: https://issues.apache.org/jira/browse/ATLAS-3254
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 1.0.0, 2.0.0
>Reporter: Adam Rempter
>Priority: Major
>  Labels: performance
>
> We use “aws_s3_pseudo_dir” type from 3020-aws_s3_typedefs.json model.
> It has following property: 
> "name":    "s3Objects",
> "typeName":    "array"
>  
> Now in AWS buckets you can have thousands of objects. This causes that 
> s3Objects array grows quite quickly, causing aws_s3_pseudo_dir entity Json to 
> rich easly few MBs.
>  
> Then we start seeing problems like:
>  * UI is dying on displaying entity properties or lineage
>  * Error in logs: audit record too long: entityType=aws_s3_pseudo_dir, 
> guid=24398271-6ba0-4db5-adfa-38e432dc55ce, size=1053931; maxSize=1048576. 
> entity attribute values not stored in audit (EntityAuditListenerV2:234)
>  * Some errors with write to HBase (java.lang.IllegalArgumentException: 
> KeyValue size too large, as workaround we set hbase.client.keyvalue.maxsize 
> param to 0)
>  * kafka consumer errors (we can of course set some parameters on consumer, 
> but I think it is just workaround)
> …
> Exception in NotificationHookConsumer (NotificationHookConsumer:332)
> org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be 
> completed since the group has already rebalanced and assigned the partitions 
> to another member. This means that the time between subsequen
> t calls to poll() was longer than the configured max.poll.interval.ms, which 
> typically implies that the poll loop is spending too much time message 
> processing. You can address this either by increasing the sessio
> n timeout or by reducing the maximum size of batches returned in poll() with 
> max.poll.records.
> …
> Specifying pseudo_dir is required for s3objects:
> name": "pseudoDirectory",
> "typeName": "aws_s3_pseudo_dir",
> "cardinality": "SINGLE",
> "isIndexable": false,
> *"isOptional": false,*
> "isUnique": false,
>  



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


[jira] [Created] (ATLAS-3261) Ranger Authorizer for Atlas is not checked for kafka messages

2019-06-04 Thread Adam Rempter (JIRA)
Adam Rempter created ATLAS-3261:
---

 Summary: Ranger Authorizer for Atlas is not checked for kafka 
messages
 Key: ATLAS-3261
 URL: https://issues.apache.org/jira/browse/ATLAS-3261
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 2.0.0, 1.1.0
Reporter: Adam Rempter


Atlas can be configured to authorize user actions with Ranger 
([https://atlas.apache.org/1.1.0/Atlas-Authorization-Ranger-Authorizer.html]).

 

When I use user via REST it works:

curl -X GET -u testuser:testuser 
http://localhost:21000/api/atlas/v2/entity/guid/f52151a0-fa08-4eab-b885-ece847a106e0
{"errorCode":"ATLAS-403-00-001","errorMessage":"testuser is not authorized to 
perform read entity: guid=f52151a0-fa08-4eab-b885-ece847a106e0"}

 

When I send lineage to ATLAS_HOOK, I can create lineage successfully:

2019-06-04 14:01:38,974 
2019-06-04T12:01:23.867Z|testuser|NotificationHookConsumer|POST|api/atlas/v2/entity/|200|15119

In above, I think user is taken from lineage message field user in json.

 

Of course above is valid if another policy in ranger  (kafka plugin) allows 
puting messages to ATLAS_HOOK topic. 

 

But if I have one user (technical account) to produce to kafka and I want to 
deny access in Atlas based on user from message, atlas ranger authorizer 
doens't work.

 

 

 

 



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


Re: Review Request 70768: ATLAS-3256 Modify export API to process with relationshipAttributes

2019-06-04 Thread Nikhil Bonte


> On June 3, 2019, 4:54 a.m., Ashutosh Mestry wrote:
> > repository/src/main/java/org/apache/atlas/repository/impexp/RelationshipAttributesExtractor.java
> > Lines 64 (patched)
> > 
> >
> > Won't this do fullFetch?

seperated logic to avoid confusion


- Nikhil


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


On May 31, 2019, 12:21 p.m., Nikhil Bonte wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70768/
> ---
> 
> (Updated May 31, 2019, 12:21 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, madhan, Nixon Rodrigues, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3256
> https://issues.apache.org/jira/browse/ATLAS-3256
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Please refer jira for description
> 
> Will add Performance improvement numbers soon.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/EntitiesExtractor.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
>  11289ea 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExtractStrategy.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/IncrementalExportEntityProvider.java
>  3a2a917 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/RelationshipAttributesExtractor.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/VertexExtractor.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/IncrementalExportEntityProviderTest.java
>  85ed5f9 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/RelationshipAttributesExtractorTest.java
>  PRE-CREATION 
>   repository/src/test/resources/hive_db_lineage.zip PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/70768/diff/3/
> 
> 
> Testing
> ---
> 
> Added UTs
> Test cases are passing
> 
> Manual testing approach:
> 1. exported data > data1.zip
> 2. cleaned hbase & solr
> 3. imported data1.zip & verified imported data
> 4. exported again > data2.zip
> 5. compared contents of data1.zip & data2.zip
> 
> 
> Thanks,
> 
> Nikhil Bonte
> 
>



Re: [VOTE] Release Apache Atlas version 1.2.0 - rc3

2019-06-04 Thread Nikhil Bonte
+1 Release Apache Atlas 1.2.0 release candidate #3

- Verified PGP signature.
- Built successfully from the source tar file
- Ran quick start and validated basic functionality.
- Performed few basic search.

Regards,
Nikhil P. Bonte

On Tue, Jun 4, 2019 at 12:19 PM Sarath Subramanian
 wrote:

> +1 for Apache Atlas 1.2.0-rc3
>
> - Validated Checksum and signature of binaries
> - No binaries found in source.
> - Build using embedded-hbase-solr profile and build was successful.
> - Able to run quickstart and view entities and lineage in atlas
> - Validated basic, advanced search, saved-search, classification
> propagation and metrics UI
>
>
> Thanks,
> Sarath
>
>
> On Mon, Jun 3, 2019 at 1:11 AM Nixon Rodrigues <
> nixon.rodrig...@freestoneinfotech.com> wrote:
>
> > Atlas team,
> >
> > Apache Atlas 1.2.0 release candidate #3 is now available for a vote
> within
> > dev community.
> >
> > Following commits went into branch-1.0 since the last release candidate
> > (rc2):
> >
> > ATLAS-3180:- New Bulk retrieval API with servicetype parameter.
> > ATLAS-3227:- Bulk delete does not delete the indexes properly.
> >
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove (and reason why)
> >
> >
> > Thanks,
> > Nixon Rodrigues
> >
> >
> > List of issues addressed in this release:
> >
> >
> https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC
> >
> > Git tag for the release:
> > https://github.com/apache/atlas/releases/tag/release-1.2.0-rc3
> >
> > Sources for the release:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
> >
> > Source release verification:
> >   PGP Signature:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.asc
> >   MD5 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.md5
> >   SHA512 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.sha512
> >
> > Keys to verify the signature of the release artifacts are available at:
> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> >
>


-- 
Regards
Nikhil P. Bonte


[jira] [Created] (ATLAS-3260) When importing KAFKA metadata, the following error is reported

2019-06-04 Thread He sheng (JIRA)
He sheng created ATLAS-3260:
---

 Summary: When importing KAFKA metadata, the following error is 
reported
 Key: ATLAS-3260
 URL: https://issues.apache.org/jira/browse/ATLAS-3260
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.1.0
Reporter: He sheng


Adding Kafka topic ATLAS_HOOK
Exception in thread "main" java.lang.NoSuchMethodError: 
kafka.utils.ZkUtils.getTopicPartitionCount(Ljava/lang/String;)Lscala/Option;
    at 
org.apache.atlas.kafka.bridge.KafkaBridge.getTopicEntity(KafkaBridge.java:231)
    at 
org.apache.atlas.kafka.bridge.KafkaBridge.createOrUpdateTopic(KafkaBridge.java:196)
    at 
org.apache.atlas.kafka.bridge.KafkaBridge.importTopic(KafkaBridge.java:182)
    at org.apache.atlas.kafka.bridge.KafkaBridge.main(KafkaBridge.java:139)
Failed to import Kafka Data Model!!!   
thread
!moz-extension://8260c77a-a03d-49f1-8b6d-70c335e701e7/static/drowDown.svg!
[THred]
!moz-extension://8260c77a-a03d-49f1-8b6d-70c335e701e7/static/sound.svg!
名词线; 丝; 线索; 绪; 细线; 缕; 运作; 丝状物
动词缕; 纫
定义
名词a long, thin strand of cotton, nylon, or other fibers used in sewing or 
weaving.
动词pass a thread through the eye of (a needle) or through the needle and guides 
of (a sewing machine).
同义词
名词cotton; filament; fiber; yarn; string; twine
动词pass; string; work; ease; push; poke
示例
She sighed and let her hands rest on her lap, her fingers absently playing with 
a loose *thread* of cotton.



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


[jira] [Comment Edited] (ATLAS-3258) Update apache-rat-plugin to 0.13

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian edited comment on ATLAS-3258 at 6/4/19 7:17 AM:
---

Updating the rat plugin version reduces verbosity during build time.

From:
{code:java}
[INFO] --- apache-rat-plugin:0.12:check (rat-check) @ hive-bridge ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 61 implicit excludes (use -debug for more details).
[INFO] Exclude: **/antlr4/**
[INFO] Exclude: **/dependency-reduced-pom.xml
[INFO] Exclude: **/javax.script.ScriptEngineFactory
[INFO] Exclude: .reviewboardrc
[INFO] Exclude: 3party-licenses/**
[INFO] Exclude: **/.cache
[INFO] Exclude: **/.cache-main
[INFO] Exclude: **/.cache-tests
[INFO] Exclude: **/.checkstyle
[INFO] Exclude: **/*.txt
[INFO] Exclude: **/*.json
[INFO] Exclude: .pc/**
[INFO] Exclude: debian/**
[INFO] Exclude: .svn/**
[INFO] Exclude: .git/**
[INFO] Exclude: .gitignore
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.twiki
[INFO] Exclude: **/*.md
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.log
[INFO] Exclude: **/target/**
[INFO] Exclude: **/target*/**
[INFO] Exclude: **/build/**
[INFO] Exclude: **/*.patch
[INFO] Exclude: derby.log
[INFO] Exclude: **/logs/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/mock/**
[INFO] Exclude: **/data/**
[INFO] Exclude: **/maven-eclipse.xml
[INFO] Exclude: **/.externalToolBuilders/**
[INFO] Exclude: **/build.log
[INFO] Exclude: **/.bowerrc
[INFO] Exclude: *.json
[INFO] Exclude: **/overlays/**
[INFO] Exclude: dev-support/**
[INFO] Exclude: **/users-credentials.properties
[INFO] Exclude: **/public/css/animate.min.css
[INFO] Exclude: **/public/css/bootstrap-sidebar.css
[INFO] Exclude: **/public/js/external_lib/**
[INFO] Exclude: **/node_modules/**
[INFO] Exclude: **/public/js/libs/**
[INFO] Exclude: **/atlas.data/**
[INFO] Exclude: **/${sys:atlas.data}/**
[INFO] Exclude: **/policy-store.txt
[INFO] Exclude: **/*rebel*.xml
[INFO] Exclude: **/*rebel*.xml.bak
[INFO] Exclude: **/test/resources/**
[INFO] 25 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 25 licenses.

{code}
 

To:
{code:java}
[INFO] --- apache-rat-plugin:0.13:check (rat-check) @ atlas-authorization ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 62 implicit excludes (use -debug for more details).
[INFO] 53 explicit excludes (use -debug for more details).
[INFO] 17 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 17 licenses.

{code}
 

 


was (Author: sarath.ku...@gmail.com):
Updating the rat plugin version reduces verbosity of the plugin.

From:

{code}

[INFO] --- apache-rat-plugin:0.12:check (rat-check) @ hive-bridge ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 61 implicit excludes (use -debug for more details).
[INFO] Exclude: **/antlr4/**
[INFO] Exclude: **/dependency-reduced-pom.xml
[INFO] Exclude: **/javax.script.ScriptEngineFactory
[INFO] Exclude: .reviewboardrc
[INFO] Exclude: 3party-licenses/**
[INFO] Exclude: **/.cache
[INFO] Exclude: **/.cache-main
[INFO] Exclude: **/.cache-tests
[INFO] Exclude: **/.checkstyle
[INFO] Exclude: **/*.txt
[INFO] Exclude: **/*.json
[INFO] Exclude: .pc/**
[INFO] Exclude: debian/**
[INFO] Exclude: .svn/**
[INFO] Exclude: .git/**
[INFO] Exclude: .gitignore
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.twiki
[INFO] Exclude: **/*.md
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.log
[INFO] Exclude: **/target/**
[INFO] Exclude: **/target*/**
[INFO] Exclude: **/build/**
[INFO] Exclude: **/*.patch
[INFO] Exclude: derby.log
[INFO] Exclude: **/logs/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/mock/**
[INFO] Exclude: **/data/**
[INFO] Exclude: **/maven-eclipse.xml
[INFO] Exclude: **/.externalToolBuilders/**
[INFO] Exclude: **/build.log
[INFO] Exclude: **/.bowerrc
[INFO] Exclude: *.json
[INFO] Exclude: **/overlays/**
[INFO] Exclude: dev-support/**
[INFO] Exclude: **/users-credentials.properties
[INFO] Exclude: **/public/css/animate.min.css
[INFO] Exclude: **/public/css/bootstrap-sidebar.css
[INFO] Exclude: **/public/js/external_lib/**
[INFO] Exclude: **/node_modules/**
[INFO] Exclude: **/public/js/libs/**
[INFO] Exclude: **/atlas.data/**
[INFO] Exclude: 

[jira] [Commented] (ATLAS-3258) Update apache-rat-plugin to 0.13

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-3258:
---

Precommit - 
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1167/console]

> Update apache-rat-plugin to 0.13
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


[jira] [Commented] (ATLAS-3220) Change hiveDDL Name and QualifiedName

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-3220:
---

Review - [https://reviews.apache.org/r/70681/]

Precommit - 
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1164/console]

> Change hiveDDL Name and QualifiedName
> -
>
> Key: ATLAS-3220
> URL: https://issues.apache.org/jira/browse/ATLAS-3220
> Project: Atlas
>  Issue Type: Bug
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
>
> Current hiveDDL entity use queryText as both name and qualifiedName, which 
> make info duplicated in the UI page of hiveDDL entity. 
> This change uses db/table 's qualifiedName and it timestamp as its new 
> qualifiedName.
> We could keep queryText as its name, which shows up at the relationship tab 
> of either table or db, users can easily find out queryText without clicking 
> into the hiveDDL entity ui page. If the queryText is too long, I hope 
> front-end could do some truncation/beautify.
>  



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


[jira] [Commented] (ATLAS-3220) Change hiveDDL Name and QualifiedName

2019-06-04 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-3220:


Commit 2968ad86de1de9e70c9c852ab55935129d38ab40 in atlas's branch 
refs/heads/master from Le Ma
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2968ad8 ]

ATLAS-3220 Change hiveDDL name and qualifiedName

Signed-off-by: Sarath Subramanian 


> Change hiveDDL Name and QualifiedName
> -
>
> Key: ATLAS-3220
> URL: https://issues.apache.org/jira/browse/ATLAS-3220
> Project: Atlas
>  Issue Type: Bug
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
>
> Current hiveDDL entity use queryText as both name and qualifiedName, which 
> make info duplicated in the UI page of hiveDDL entity. 
> This change uses db/table 's qualifiedName and it timestamp as its new 
> qualifiedName.
> We could keep queryText as its name, which shows up at the relationship tab 
> of either table or db, users can easily find out queryText without clicking 
> into the hiveDDL entity ui page. If the queryText is too long, I hope 
> front-end could do some truncation/beautify.
>  



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


[jira] [Resolved] (ATLAS-3220) Change hiveDDL Name and QualifiedName

2019-06-04 Thread Sarath Subramanian (JIRA)


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

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

> Change hiveDDL Name and QualifiedName
> -
>
> Key: ATLAS-3220
> URL: https://issues.apache.org/jira/browse/ATLAS-3220
> Project: Atlas
>  Issue Type: Bug
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
>
> Current hiveDDL entity use queryText as both name and qualifiedName, which 
> make info duplicated in the UI page of hiveDDL entity. 
> This change uses db/table 's qualifiedName and it timestamp as its new 
> qualifiedName.
> We could keep queryText as its name, which shows up at the relationship tab 
> of either table or db, users can easily find out queryText without clicking 
> into the hiveDDL entity ui page. If the queryText is too long, I hope 
> front-end could do some truncation/beautify.
>  



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


[jira] [Commented] (ATLAS-3258) Update apache-rat-plugin to 0.13

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-3258:
---

Updating the rat plugin version reduces verbosity of the plugin.

From:

{code}

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

{code}

 

To:

{code}
[INFO] --- apache-rat-plugin:0.13:check (rat-check) @ atlas-authorization ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 62 implicit excludes (use -debug for more details).
[INFO] 53 explicit excludes (use -debug for more details).
[INFO] 17 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 17 licenses.

{code}

 

 

> Update apache-rat-plugin to 0.13
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


[jira] [Updated] (ATLAS-3258) Using apache-rat-plugin 0.13 instead of 0.12

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-3258:
--
Attachment: ATLAS-3258.001.patch

> Using apache-rat-plugin 0.13 instead of 0.12
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


[jira] [Updated] (ATLAS-3258) Update apache-rat-plugin to 0.13

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-3258:
--
Summary: Update apache-rat-plugin to 0.13  (was: Using apache-rat-plugin 
0.13 instead of 0.12)

> Update apache-rat-plugin to 0.13
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


[jira] [Assigned] (ATLAS-3258) Using apache-rat-plugin 0.13 instead of 0.12

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian reassigned ATLAS-3258:
-

Assignee: Sarath Subramanian

> Using apache-rat-plugin 0.13 instead of 0.12
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


[jira] [Updated] (ATLAS-3258) Using apache-rat-plugin 0.13 instead of 0.12

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-3258:
--
Summary: Using apache-rat-plugin 0.13 instead of 0.12  (was: Using 
apache-rat-plugin 0.13 instead of 0,12)

> Using apache-rat-plugin 0.13 instead of 0.12
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Priority: Minor
> Fix For: 3.0.0
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



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


Re: [VOTE] Release Apache Atlas version 1.2.0 - rc3

2019-06-04 Thread Sarath Subramanian
+1 for Apache Atlas 1.2.0-rc3

- Validated Checksum and signature of binaries
- No binaries found in source.
- Build using embedded-hbase-solr profile and build was successful.
- Able to run quickstart and view entities and lineage in atlas
- Validated basic, advanced search, saved-search, classification
propagation and metrics UI


Thanks,
Sarath


On Mon, Jun 3, 2019 at 1:11 AM Nixon Rodrigues <
nixon.rodrig...@freestoneinfotech.com> wrote:

> Atlas team,
>
> Apache Atlas 1.2.0 release candidate #3 is now available for a vote within
> dev community.
>
> Following commits went into branch-1.0 since the last release candidate
> (rc2):
>
> ATLAS-3180:- New Bulk retrieval API with servicetype parameter.
> ATLAS-3227:- Bulk delete does not delete the indexes properly.
>
> Links to the release artifacts are given below. Please review and vote.
>
> The vote will be open for at least 72 hours or until necessary votes are
> reached.
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove (and reason why)
>
>
> Thanks,
> Nixon Rodrigues
>
>
> List of issues addressed in this release:
>
> https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC
>
> Git tag for the release:
> https://github.com/apache/atlas/releases/tag/release-1.2.0-rc3
>
> Sources for the release:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz
>
> Source release verification:
>   PGP Signature:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.asc
>   MD5 Hash:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.md5
>   SHA512 Hash:
>
> https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.sha512
>
> Keys to verify the signature of the release artifacts are available at:
> https://dist.apache.org/repos/dist/dev/atlas/KEYS
>


[jira] [Updated] (ATLAS-3241) AtlasClientV2Test.java invalid directory

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-3241:
--
Attachment: (was: ATLAS-3241.001.patch)

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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


[jira] [Updated] (ATLAS-3241) AtlasClientV2Test.java invalid directory

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-3241:
--
Attachment: ATLAS-3241.001.patch

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
> Attachments: ATLAS-3241.001.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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


[jira] [Assigned] (ATLAS-3241) AtlasClientV2Test.java invalid directory

2019-06-04 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian reassigned ATLAS-3241:
-

Assignee: Sarath Subramanian

> AtlasClientV2Test.java invalid directory
> 
>
> Key: ATLAS-3241
> URL: https://issues.apache.org/jira/browse/ATLAS-3241
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk, 2.1.0, 3.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0, trunk, 2.1.0, 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AtlasClientV2Test.java should have the following path
> {quote}client/client-v2 /src/test 
> /java/{color:#FF}org/apache/atlas{color}/AtlasClientV2Test.java 
> {quote}
> instead has
> {quote}client/client-v2 
> /src/test/java/{color:#FF}org.apache.atlas{color}/AtlasClientV2Test.
> {quote}
> Bug or, for some strange reason, intentional ?



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


Re: Atlas 0.8.4 release heads up

2019-06-04 Thread Sarath Subramanian
Thanks for taking this up Keval.

+1 for releasing Apache Atlas 0.8.4.


Thanks,
Sarath


On Mon, Jun 3, 2019 at 10:45 PM Keval Bhatt  wrote:

> Quick correction to the issue URL:
>
> https://issues.apache.org/jira/issues/?jql=project%3DATLAS%20AND%20resolution%3DFixed%20AND%20fixVersion%3D0.8.4%20ORDER%20BY%20key%20DESC
>
> Sorry for the mixup.
>
> On Mon, Jun 3, 2019 at 6:17 PM Keval Bhatt  wrote:
>
> > Atlas dev community,
> >
> > Since Atlas 0.8.3 was released, there are 49 commits
> > 
> >  on
> > branch-0.8 and 54 resolved issues
> > <
> https://issues.apache.org/jira/browse/ATLAS-1070?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.4%20ORDER%20BY%20key%20ASC>
> with
> > fix version 0.8.4 after 0.8.3 release.
> >
> > These bug fixes and improvements are important for stability and for
> other
> > dependent components that consume Atlas.
> >
> > I propose that we should do a 0.8.4 release from branch-0.8 and the
> > tentative release completion date would be 18th Jun 2019.
> >
> > I volunteer to be the release manager for Apache Atlas 0.8.4 release.
> >
> > Let me know your thoughts and concerns if any.
> >
> > Regards
> >
>


[jira] [Updated] (ATLAS-3228) UI: Dots appearing in select column in Search page

2019-06-04 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues updated ATLAS-3228:
---
Fix Version/s: (was: 2.1.0)

> UI: Dots appearing in select column in Search page 
> ---
>
> Key: ATLAS-3228
> URL: https://issues.apache.org/jira/browse/ATLAS-3228
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Rahul Kurup
>Assignee: Binit Gutka
>Priority: Minor
> Fix For: trunk
>
> Attachments: ATLAS-3228.patch, dotsieselectcolumn.png
>
>
> In IE 10 and 11, dots are visible. Please see attached screenshot. 
> !dotsieselectcolumn.png!



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


[jira] [Commented] (ATLAS-3228) UI: Dots appearing in select column in Search page

2019-06-04 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-3228:


Commit af25456d7a2110d27295c1249cec3795bfb5b51e in atlas's branch 
refs/heads/master from gutkaBinit
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=af25456 ]

ATLAS-3228 UI: Dots appearing in select column in Search page.

Signed-off-by: nixonrodrigues 


> UI: Dots appearing in select column in Search page 
> ---
>
> Key: ATLAS-3228
> URL: https://issues.apache.org/jira/browse/ATLAS-3228
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Rahul Kurup
>Assignee: Binit Gutka
>Priority: Minor
> Attachments: ATLAS-3228.patch, dotsieselectcolumn.png
>
>
> In IE 10 and 11, dots are visible. Please see attached screenshot. 
> !dotsieselectcolumn.png!



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


[jira] [Commented] (ATLAS-3248) UI: Number of Search Page results not matching set Page limit

2019-06-04 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-3248:


Commit eced9a6945934a9930de137976b744ca2aeacec3 in atlas's branch 
refs/heads/master from gutkaBinit
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=eced9a6 ]

ATLAS-3248 UI: Number of Search Page results not matching set Page limit.

Signed-off-by: nixonrodrigues 


> UI: Number of Search Page results not matching set Page limit
> -
>
> Key: ATLAS-3248
> URL: https://issues.apache.org/jira/browse/ATLAS-3248
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Binit Gutka
>Priority: Major
> Attachments: ATLAS-3248.patch
>
>
> The number of results being displayed does not match the Page Limit option if 
> Page Limit option is set to any value other than 25.



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