Re: [VOTE] Graduate Apache Atlas Project from Incubator

2017-05-26 Thread Selvamohan Neethiraj 
+1 

Selva-


On 5/24/17, 7:23 PM, "Suma Shivaprasad"  wrote:

Dear Atlas Community Members,

Following the discussion in Atlas community on graduating Apache Atlas
Project from Incubation to a Top Level Project, starting this
voting thread within the Atlas community. I appreciate mentors and
community members in making this happen and thanks for their
support. Apache Atlas Project has come a long way since entering into
incubation during May 2015 and the project summary shows the
details on this.

Please vote on the Apache Atlas Project resolution that is found in
bottom of this email.

[ ] +1 Graduate Apache Atlas from the Incubator.
[ ] +0 No opinion
[ ] -1 Don't graduate Apache Atlas from the Incubator ( please provide
the reason)

This VOTE will be opened for next 72 hours.

If this VOTE succeeds, a similar VOTE will be done in general@incubator
mailing list. If that succeeds, a resolution will be
included in the next Apache Board Meeting.

Here is my Vote +1 (binding)

Thanks all for your participation
Suma


Project Summary:

=
http://incubator.apache.org/projects/atlas.html

Project website:
=

http://atlas.incubator.apache.org

Project Documentation:
===

http://atlas.incubator.apache.org/index.html
Architecture - http://atlas.incubator.apache.org/Architecture.html
Installation guide - http://atlas.incubator.apache.org/InstallationSteps.
html
QuickStart Guide- http://atlas.incubator.apache.org/QuickStart.html
REST API - http://atlas.incubator.apache.org/api/v2/index.html
Atlas Release Guide - https://cwiki.apache.org/confluence/display/ATLAS/
Developer+Resources

Project maturity Assessment:
===

https://cwiki.apache.org/confluence/display/ATLAS/
Apache+Atlas+Project+Maturity+Model

Proposed PMC size: 38

Total number of committers  : 38 members
Total number of contributors : 62 members

PMC affiliation (* indicated chair)

* Hortonworks (13)
   IBM (3)
   Aetna(4)
   Freestone (3)
   Merck (2)
   Oracle(2)
   Target (2)
   Schlumberger(2)
   Dataguise(1)
   Inmobi(1)
   JPMC(1)
   MPR(1)
   SAP(1)
   SparklineData(1)
   Others(1)

1660 commits on master
80 contributors across all branches
Dev list averaged ~500-800 msgs/month in 2017
User list was created recently in April 2017. Hence not considering stats
for this.
1827 issues created

Committer¹s affiliation:
===
* Hortonworks (13)
   IBM (3)
   Aetna(4)
   Freestone (3)
   Merck (2)
   Oracle(2)
   Target (2)
   Schlumberger(2)
   Dataguise(1)
   Inmobi(1)
   JPMC(1)
   MPR(1)
   SAP(1)
   SparklineData(1)
   Others(1)


Apache Atlas Top Level Project Resolution:


Establish the Apache Atlas Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation¹s purpose to establish a
Project Management Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the public, related
to a data management platform That provides real-time, consistent access
to data-intensive applications throughout widely distributed cloud
architectures.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Atlas Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED,that the Apache Atlas Project be and hereby is responsible for
the creation and maintenance of software related to a data management
platform that provides real-time, consistent access to data-intensive
applications throughout widely distributed cloud architectures.

RESOLVED, that the office of "Vice President, Apache Atlas" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Atlas
Project, and to have primary responsibility for management of the projects
within the scope of responsibility of the Apache Atlas Project; and be it
Further.

>RESOLVED,that the persons listed immediately below be and hereby are
>appointed to serve as the initial members of the Apache Atlas Project:

Aaron Dossett adoss...@target.com 
Andrew Ahn a...@apache.org 
Anil Varma ava...@slb.com 
Arun C. Murthy acmur...@apache.org 
Apoorv

Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 0 (dev group vote)

2017-03-07 Thread Selvamohan Neethiraj 
+1 

• Extracted source from tag (release-0.8-rc0) and build successfully
• Verified Signature of the release-candidate artficat
• Verified Checksum specified in the release
• Verified that no binary file in the source release
• Verified the successful run of rat plugin

Thanks,
Selva-

On 3/7/17, 4:54 AM, "Madhan Neethiraj"  wrote:

Atlas team,

 

Apache Atlas 0.8 (incubating) release candidate #0 is now available for a 
vote within dev community. Links to the release artifacts are given below. Can 
you 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)

 

Here is my +1

 

Thanks,

Madhan

 

 

List of improvements and issues addressed in this release: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8-incubating%20ORDER%20BY%20key%20DESC
 

 

Git tag for the release: 
https://github.com/apache/incubator-atlas/tree/release-0.8-rc0

 

Sources for the release: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc0/apache-atlas-0.8-incubating-sources.tar.gz

 

Source release verification:

  PGP Signature:  
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc0/apache-atlas-0.8-incubating-sources.tar.gz.asc

  MD5 Hash: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc0/apache-atlas-0.8-incubating-sources.tar.gz.md5
 

 

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

Re: Changes to JIRA ServiceDesk

2017-01-30 Thread Selvamohan Neethiraj 
Unfortunately 

https://issues.apache.org/jira/servicedesk/agent/RANGER/people   throws - You 
don't have permission to access this Service Desk.

Can someone from INFRA can help with this request?

Thanks,
Selva-


On 1/30/17, 5:54 PM, "Pono Takamori"  wrote:

Greetings from Infra,
We recently began our upgrade path for modernizing JIRA and in the
process ServiceDesk was also upgraded.  Before this upgrade the use of
ServiceDesk was very straightforward for admins, but now we've
discovered that it has irrevocably changed the permission scheme for
ticket assignment.  Assignable users (for projects that use
ServiceDesk [0]) are not only definable by the project one user at a
time by a Project Administrator.
What this means for you is that you'll need to go to the Agents [1]
page for your project and add all users which should be assignable.
We apologize for the added work this upgrade caused, hopefully
Atlassian will tend to the issue [2].  Please let us know via e-mail
or Hipchat if you have any questions.

Thanks for your cooperation,
-Pono

[0] - The affected JIRA Projects are: ATLAS, CARBONDATA, INFRA, KYLIN,
OWC, RANGER AND SENSSOFT
[1] - https://issues.apache.org/jira/servicedesk/agent/INFRA/people
replacing INFRA with the key of your project
[2] - https://jira.atlassian.com/browse/JSD-861

[jira] [Updated] (ATLAS-1270) Atlas web server allows user to browse webapp directory

2016-11-05 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-1270:

Environment: (was: HDP 2.4.2 and HDP 2.5)

> Atlas web server allows user to browse webapp directory
> ---
>
> Key: ATLAS-1270
> URL: https://issues.apache.org/jira/browse/ATLAS-1270
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating, 0.7-incubating
>Reporter: Vipin Rathor
> Attachments: atlas-dir-listing-allowed.png, 
> atlas-dir-listing-forbidden-with-patch.png, atlas-disable-dir-list.patch
>
>
> Currently any (even non-authenticated) user can access the webapp directory 
> structure by pointing to URIs like http://localhost:21000/lib, 
> http://localhost:21000/js and http://localhost:21000/img
> This could lead to some serious exploits.
> As a fix, the embedded Jetty server (including the secure one) should disable 
> the directory listing.
> I'm submitting a basic patch which I tested with non-secure embedded server 
> only. Since this is my first patch, I'm looking for any feedback so that I 
> can submit better patches in future.
> Thanks.



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

[jira] [Updated] (ATLAS-1270) Atlas web server allows user to browse webapp directory

2016-11-05 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-1270:

Labels:   (was: security)

> Atlas web server allows user to browse webapp directory
> ---
>
> Key: ATLAS-1270
> URL: https://issues.apache.org/jira/browse/ATLAS-1270
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating, 0.7-incubating
>Reporter: Vipin Rathor
> Attachments: atlas-dir-listing-allowed.png, 
> atlas-dir-listing-forbidden-with-patch.png, atlas-disable-dir-list.patch
>
>
> Currently any (even non-authenticated) user can access the webapp directory 
> structure by pointing to URIs like http://localhost:21000/lib, 
> http://localhost:21000/js and http://localhost:21000/img
> This could lead to some serious exploits.
> As a fix, the embedded Jetty server (including the secure one) should disable 
> the directory listing.
> I'm submitting a basic patch which I tested with non-secure embedded server 
> only. Since this is my first patch, I'm looking for any feedback so that I 
> can submit better patches in future.
> Thanks.



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

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

2016-06-23 Thread Selvamohan Neethiraj 
+1   

Downloaded source ;  Able to build successfully ; Validated the signature and 
checksum ….

Thanks,
Selva-

From:  Shwetha Shivalingamurthy 
Reply-To:  "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/

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-661) REST API Authentication

2016-05-08 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-661:


+1 for the PATCH:   ATLAS-661.3.patch

> REST API Authentication
> ---
>
> Key: ATLAS-661
> URL: https://issues.apache.org/jira/browse/ATLAS-661
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-661.2.patch, ATLAS-661.3.patch, ATLAS-661.patch
>
>
> Atlas needs to authorize the REST API invocations; as necessary requests will 
> be forced to authenticate.



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

[jira] [Commented] (ATLAS-661) REST API Authentication

2016-05-08 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-661:


[~yhemanth] - Validated the patch - ATLAS-661.3.patch.  mvn install - seems to 
be passing all tests in general ... However, sometimes  
NegativeSSLAndKerberosTest seems to fail. But, if you re-run the test alone, it 
seems to be passing. I feel that there is some test sequence issues - where 
some state is not being reset correctly. We should spend sometime to identify 
this issue later.

+1 for the patch.  If the  NegativeSSLAndKerberosTest - fails on/off, can we 
disable the test until we are able to identify the test sequence issue ?

> REST API Authentication
> ---
>
> Key: ATLAS-661
> URL: https://issues.apache.org/jira/browse/ATLAS-661
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-661.2.patch, ATLAS-661.3.patch, ATLAS-661.patch
>
>
> Atlas needs to authorize the REST API invocations; as necessary requests will 
> be forced to authenticate.



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

[jira] [Commented] (ATLAS-759) HiveHookIT.testAlterTableChangeColumn is consistently failing on master

2016-05-08 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-759:


Tested with the attached patch -  ATLAS-759.patch -  All tests are successfully 
passing.

{code}
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 112.359 sec - 
in org.apache.atlas.hive.hook.HiveHookIT



[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 19:24 min
[INFO] Finished at: 2016-05-08T22:58:32-04:00
[INFO] Final Memory: 303M/3355M

.
[sneethir@mynext incubator-atlas]$ git status
# On branch master
# Changes not staged for commit:
#   (use "git add ..." to update what will be committed)
#   (use "git checkout -- ..." to discard changes in working directory)
#
#   modified:   
addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java
#
no changes added to commit (use "git add" and/or "git commit -a")

{code}


+1 for the patch

> HiveHookIT.testAlterTableChangeColumn is consistently failing on master
> ---
>
> Key: ATLAS-759
> URL: https://issues.apache.org/jira/browse/ATLAS-759
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-759.patch
>
>
> Running mvn clean install is failing in 
> HiveHookIT.testAlterTableChangeColumn. The exception is occurring due to a 
> lock timeout exception on the server side.



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

[jira] [Commented] (ATLAS-759) HiveHookIT.testAlterTableChangeColumn is consistently failing on master

2016-05-08 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-759:


Yes. [~yhemanth]. I can definitely see that the HiveIT is broken without this 
patch..

{code}
Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 171.784 sec 
<<< FAILURE! - in org.apache.atlas.hive.hook.HiveHookIT
testAlterTableChangeColumn(org.apache.atlas.hive.hook.HiveHookIT)  Time 
elapsed: 81.631 sec  <<< FAILURE!
java.lang.AssertionError: Assertions failed. Failing after waiting for timeout 
8 msecs
at org.apache.atlas.hive.hook.HiveHookIT.waitFor(HiveHookIT.java:1437)
at 
org.apache.atlas.hive.hook.HiveHookIT.assertEntityIsRegistered(HiveHookIT.java:1344)
at 
org.apache.atlas.hive.hook.HiveHookIT.assertColumnIsRegistered(HiveHookIT.java:272)
at 
org.apache.atlas.hive.hook.HiveHookIT.testAlterTableChangeColumn(HiveHookIT.java:733)
{code}

I will post - the result after the patch in few mins 

> HiveHookIT.testAlterTableChangeColumn is consistently failing on master
> ---
>
> Key: ATLAS-759
> URL: https://issues.apache.org/jira/browse/ATLAS-759
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-759.patch
>
>
> Running mvn clean install is failing in 
> HiveHookIT.testAlterTableChangeColumn. The exception is occurring due to a 
> lock timeout exception on the server side.



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

[jira] [Commented] (ATLAS-759) HiveHookIT.testAlterTableChangeColumn is consistently failing on master

2016-05-07 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-759:


+1 for [~yhemanth]'s  temporary workaround patch. After committing this patch, 
can we create another BUG/Improvement JIRA to locate and identify the (actual) 
issue ?

> HiveHookIT.testAlterTableChangeColumn is consistently failing on master
> ---
>
> Key: ATLAS-759
> URL: https://issues.apache.org/jira/browse/ATLAS-759
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-759.patch
>
>
> Running mvn clean install is failing in 
> HiveHookIT.testAlterTableChangeColumn. The exception is occurring due to a 
> lock timeout exception on the server side.



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

[jira] [Commented] (ATLAS-661) REST API Authentication

2016-05-07 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-661:


Thanks [~yhemanth].  I have validated most of your merge changes and am trying 
to run IT and will post the results once I am done with validating the changes.

> REST API Authentication
> ---
>
> Key: ATLAS-661
> URL: https://issues.apache.org/jira/browse/ATLAS-661
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-661.2.patch, ATLAS-661.3.patch, ATLAS-661.patch
>
>
> Atlas needs to authorize the REST API invocations; as necessary requests will 
> be forced to authenticate.



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

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

2016-05-06 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-491:
---
Attachment: 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch

Updated pom.xml to be able to apply patch on master branch
Removed author information in some of the Java Code

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



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

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

2016-05-06 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-491:
---
Attachment: (was: 
0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch)

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



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

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

2016-05-06 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-491:
---
Attachment: 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch

Fixed pom.xml to be able to merge with master branch
Removed author info
Added Apache2 License headers on source java file to pass RAT verification

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



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

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

2016-05-06 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-491:
---
Attachment: (was: 
0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch)

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



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

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

2016-05-06 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-491:
---
Attachment: 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch

simple pom.xml fixes to previous patch - to be able to apply on master branch

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



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

Re: Review Request 46700: ATLAS-497 : Simple Authorization

2016-05-05 Thread Selvamohan Neethiraj 

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


Ship it!




Ship It!

- Selvamohan Neethiraj


On May 5, 2016, 10:48 a.m., Saqeeb Shaikh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/46700/
> ---
> 
> (Updated May 5, 2016, 10:48 a.m.)
> 
> 
> Review request for atlas, Erik Bergenholtz, Shwetha GS, Selvamohan Neethiraj, 
> and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-497
> https://issues.apache.org/jira/browse/ATLAS-497
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Patch Contains** Simple file based authorization for Atlas REST APIs.
> 
> Implementation contains addition of policy based authorization, where 
> policy-store.txt contains policies for each group / user which will login to 
> Atlas. As initial implementation introducing permissions for 3 Groups of 
> Users : 
> 
> Data Scientist : Users in this Group will have Read only access to the Atlas 
> resources
> Data Steward : Users in this Group will have RWU (read, write, update) 
> accesses to the Atlas resources
> Admin : Users in this Group will have RWUD  (read, write, update, delete) 
> accesses to the Atlas resources
> 
> **Assuming following resources for various APIs**
>  
> TYPE :  for accessing traits,classes 
> ENTITY : for accessing entity, discovery, lineage APIs
> OPERATION : For APIs related to Admin (version, stack, rextergraph related 
> APIs)
> 
> 
> Diffs
> -
> 
>   distro/src/conf/atlas-application.properties 290105f 
>   distro/src/conf/policy-store.txt PRE-CREATION 
>   pom.xml 729b178 
>   webapp/src/main/java/org/apache/atlas/authorize/AtlasAccessRequest.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/AtlasAccessorTypes.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/AtlasActionTypes.java 
> PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/authorize/AtlasAuthorizationException.java
>  PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/authorize/AtlasAuthorizationUtils.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/AtlasAuthorizer.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/AtlasResourceTypes.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/PolicyDef.java PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/PolicyParser.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/PolicyUtil.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/authorize/SimpleAtlasAuthorizer.java 
> PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/util/FileReaderUtil.java PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/web/filters/AtlasAuthorizationFilter.java
>  PRE-CREATION 
>   webapp/src/test/java/org/apache/atlas/authorize/PolicyParserTest.java 
> PRE-CREATION 
>   webapp/src/test/java/org/apache/atlas/authorize/PolicyUtilTest.java 
> PRE-CREATION 
>   
> webapp/src/test/java/org/apache/atlas/authorize/SimpleAtlasAuthorizerTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/46700/diff/
> 
> 
> Testing
> ---
> 
> Verified authorization by logging in to Atlas as user of different groups. 
> Verified that Data Scientist should not be allowed to write / update or 
> delete  any of the resources. 
> Added test cases to cater to parsing of policies from the policy store. 
> 
> Verifed : mvn clean compile package -Pdist
> 
> 
> Thanks,
> 
> Saqeeb Shaikh
> 
>

[jira] [Commented] (ATLAS-469) Create a new release version for the next release

2016-04-29 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-469:


[~shwethags] - Since you have created '0.7-incubating', can you please mark 
this as CLOSED ?

> Create a new release version for the next release
> -
>
> Key: ATLAS-469
> URL: https://issues.apache.org/jira/browse/ATLAS-469
> Project: Atlas
>  Issue Type: Task
>    Reporter: Selvamohan Neethiraj
>Priority: Critical
>
> Currently, all changes are being tracked as version - 'trunk' ... Instead, I 
> suggest that we create the next possible release '0.7.0-incubating' and 
> create a roadmap for all features and bugfixes for the specific release 
> version.



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

[jira] [Updated] (ATLAS-681) update committer/ppmc members in the pom.xml

2016-04-20 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-681:
---
Attachment: (was: 
0001-ATLAS-681-update-to-ATLAS-team-members-in-the-pom.xm.patch)

> update committer/ppmc members in the pom.xml
> 
>
> Key: ATLAS-681
> URL: https://issues.apache.org/jira/browse/ATLAS-681
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>    Reporter: Selvamohan Neethiraj
>    Assignee: Selvamohan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-681-update-to-ATLAS-team-members-in-the-pom.xm.patch
>
>
> Update pom.xml with correct roles for current team members and add new 
> committers 



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

Re: Review Request 46302: ATLAS-681: update committer/ppmc members in the pom.xml

2016-04-16 Thread Selvamohan Neethiraj 

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

(Updated April 16, 2016, 1:38 p.m.)


Review request for atlas, Suresh Srinivasan and Venkat Ranganathan.


Changes
---

Updated email address for Venkat Ranganathan


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


Repository: atlas


Description
---

Updated committer/ppmc members in the pom.xml


Diffs (updated)
-

  pom.xml 2ccabc3 

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


Testing
---

Build using updated pom.xml completed successfully.


Thanks,

Selvamohan Neethiraj

[jira] [Updated] (ATLAS-681) update committer/ppmc members in the pom.xml

2016-04-16 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-681:
---
Attachment: 0001-ATLAS-681-update-to-ATLAS-team-members-in-the-pom.xm.patch

Patch to make 
-> initial committers as PPMC members
-> updated organization for team members
-> Updated role for all committers added after incubation of ATLAS
-> added new committer(s)

> update committer/ppmc members in the pom.xml
> 
>
> Key: ATLAS-681
> URL: https://issues.apache.org/jira/browse/ATLAS-681
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>    Reporter: Selvamohan Neethiraj
>Assignee: Selvamohan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-681-update-to-ATLAS-team-members-in-the-pom.xm.patch
>
>
> Update pom.xml with correct roles for current team members and add new 
> committers 



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

[jira] [Created] (ATLAS-681) update committer/ppmc members in the pom.xml

2016-04-16 Thread Selvamohan Neethiraj (JIRA) 
Selvamohan Neethiraj created ATLAS-681:
--

 Summary: update committer/ppmc members in the pom.xml
 Key: ATLAS-681
 URL: https://issues.apache.org/jira/browse/ATLAS-681
 Project: Atlas
  Issue Type: Task
Affects Versions: 0.7-incubating
Reporter: Selvamohan Neethiraj
Assignee: Selvamohan Neethiraj
 Fix For: 0.7-incubating


Update pom.xml with correct roles for current team members and add new 
committers 



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

[jira] [Commented] (ATLAS-679) Camera plugin changes body height

2016-04-15 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-679:


This seems to have landed on a wrong apache project   Can someone close 
this issue as INVALID ?

> Camera plugin changes body height
> -
>
> Key: ATLAS-679
> URL: https://issues.apache.org/jira/browse/ATLAS-679
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasoon Chaudhary
> Attachments: IMG_1451.jpg
>
>




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

[jira] [Created] (ATLAS-504) Create components for assigning JIRA(s) ...

2016-02-17 Thread Selvamohan Neethiraj (JIRA) 
Selvamohan Neethiraj created ATLAS-504:
--

 Summary: Create components for assigning JIRA(s) ...
 Key: ATLAS-504
 URL: https://issues.apache.org/jira/browse/ATLAS-504
 Project: Atlas
  Issue Type: Task
Reporter: Selvamohan Neethiraj
Priority: Minor
 Fix For: 0.7-incubating


Can we create a separate components for assigning the bugs in appropriate 
bucket ?

WebServer
falcon-bridge
hive-bridge
sqoop-bridge
storm-bridge
Client
server-api
typesystem
docs
titan







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

[jira] [Commented] (ATLAS-503) Not all Hive tables are not imported into Atlas when interrupted with search queries while importing.

2016-02-17 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-503:


[~ssainath] - Can you please provide us the exact version of ATLAS - you were 
using ? Seems like a Critical bug ... Changing the priority to Critical ...

> Not all Hive tables are not imported into Atlas when interrupted with search 
> queries while importing.  
> ---
>
> Key: ATLAS-503
> URL: https://issues.apache.org/jira/browse/ATLAS-503
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
> Attachments: hiv2atlaslogs.rtf
>
>
> On running a file containing 100 table creation commands using beeline -f , 
> all hive tables are created. But only 81 of them are imported into Atlas 
> (HiveHook enabled) when queries like "hive_table" is searched frequently 
> while the import process for the table is going on.  



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

[jira] [Updated] (ATLAS-503) Not all Hive tables are not imported into Atlas when interrupted with search queries while importing.

2016-02-17 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-503:
---
Priority: Critical  (was: Major)

> Not all Hive tables are not imported into Atlas when interrupted with search 
> queries while importing.  
> ---
>
> Key: ATLAS-503
> URL: https://issues.apache.org/jira/browse/ATLAS-503
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Priority: Critical
> Attachments: hiv2atlaslogs.rtf
>
>
> On running a file containing 100 table creation commands using beeline -f , 
> all hive tables are created. But only 81 of them are imported into Atlas 
> (HiveHook enabled) when queries like "hive_table" is searched frequently 
> while the import process for the table is going on.  



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

Re: [jira] [Commented] (ATLAS-486) Improvements to pom.xml to fix scm urls and update versions for buildnumber-maven-plugin

2016-02-16 Thread Selvamohan Neethiraj 
Thanks Suma. Uploaded new patch - 
https://issues.apache.org/jira/secure/attachment/12788179/0002-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch
 
With SkipTests be defined with false.

Can you please review and commit the patch ?

Thanks,
Selva-

From:  "Suma Shivaprasad (JIRA)" <j...@apache.org>
Reply-To:  "dev@atlas.incubator.apache.org" <dev@atlas.incubator.apache.org>
Date:  Wednesday, February 17, 2016 at 12:22 AM
To:  "dev@atlas.incubator.apache.org" <dev@atlas.incubator.apache.org>
Subject:  [jira] [Commented] (ATLAS-486) Improvements to pom.xml to fix scm 
urls and update versions for buildnumber-maven-plugin


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

Suma Shivaprasad commented on ATLAS-486:


Seems like skipTests is true by default. Shouldnt it be false?

 Improvements to pom.xml to fix scm urls and update versions for 
buildnumber-maven-plugin 
 
-

 Key: ATLAS-486
 URL: https://issues.apache.org/jira/browse/ATLAS-486
 Project: Atlas
  Issue Type: Improvement
Reporter: Selvamohan Neethiraj
Assignee: Selvamohan Neethiraj
 Fix For: 0.7-incubating

 Attachments: 
0001-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch


 Modify the pom.xml to fix scm url - which is missing (git) as part of the url
 Upgrade the plugin version of buildnumber-maven-plugin
 Parameterize skipTests ...



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

[jira] [Updated] (ATLAS-486) Improvements to pom.xml to fix scm urls and update versions for buildnumber-maven-plugin

2016-02-16 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-486:
---
Attachment: 0002-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch

New patch file w/ added fix to "skipTests to be false - by default"  

> Improvements to pom.xml to fix scm urls and update versions for 
> buildnumber-maven-plugin 
> -
>
> Key: ATLAS-486
> URL: https://issues.apache.org/jira/browse/ATLAS-486
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Selvamohan Neethiraj
>    Assignee: Selvamohan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch, 
> 0002-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch
>
>
> Modify the pom.xml to fix scm url - which is missing (git) as part of the url
> Upgrade the plugin version of buildnumber-maven-plugin
> Parameterize skipTests ...



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

FW: [jira] [Commented] (ATLAS-483) Remove client.properties

2016-02-16 Thread Selvamohan Neethiraj 
Since I am new to ATLAS project, I need someone help in understanding as why 
lot of the Junit test cases are failing ?

Is there a specific set of tools should exists on the box ? (Except JDK1.8, 
Maven, ….)

Thanks,
Selva-


From:  "ATLAS QA (JIRA)" 
Reply-To:  "dev@atlas.incubator.apache.org" 
Date:  Tuesday, February 16, 2016 at 7:20 AM
To:  "dev@atlas.incubator.apache.org" 
Subject:  [jira] [Commented] (ATLAS-483) Remove client.properties


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

ATLAS QA commented on ATLAS-483:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12788056/ATLAS-483.patch
  against master revision 21b403b.

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

{color:green}+1 tests included{color}.  The patch appears to include 3 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 376 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 :
 
./webapp/target/failsafe-reports/TEST-org.apache.atlas.web.resources.RexsterGraphJerseyResourceIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.web.resources.AdminJerseyResourceIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.notification.NotificationHookConsumerIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.web.resources.EntityJerseyResourceIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.web.resources.RexsterGraphJerseyResourceIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.web.resources.AdminJerseyResourceIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.notification.NotificationHookConsumerIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.web.resources.EntityJerseyResourceIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.web.resources.MetadataDiscoveryJerseyResourceIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.notification.EntityNotificationIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.examples.QuickStartIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.web.resources.HiveLineageJerseyResourceIT
./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.web.resources.TypesJerseyResourceIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.web.resources.MetadataDiscoveryJerseyResourceIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.notification.EntityNotificationIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.examples.QuickStartIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.web.resources.HiveLineageJerseyResourceIT
./webapp/target/failsafe-reports/TEST-org.apache.atlas.web.resources.TypesJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.RexsterGraphJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.AdminJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.EntityJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.MetadataDiscoveryJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.TypesJerseyResourceIT

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/15//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/15//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/15//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/15//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/15//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/15//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/15//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings:

[jira] [Commented] (ATLAS-486) Improvements to pom.xml to fix scm urls and update versions for buildnumber-maven-plugin

2016-02-15 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-486:


The above changes only maven pom.xml settings - does not need any additional 
unit tests to validate.

> Improvements to pom.xml to fix scm urls and update versions for 
> buildnumber-maven-plugin 
> -
>
> Key: ATLAS-486
> URL: https://issues.apache.org/jira/browse/ATLAS-486
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Selvamohan Neethiraj
>    Assignee: Selvamohan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch
>
>
> Modify the pom.xml to fix scm url - which is missing (git) as part of the url
> Upgrade the plugin version of buildnumber-maven-plugin
> Parameterize skipTests ...



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

[jira] [Updated] (ATLAS-486) Improvements to pom.xml to fix scm urls and update versions for buildnumber-maven-plugin

2016-02-15 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj updated ATLAS-486:
---
Attachment: 0001-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch

> Improvements to pom.xml to fix scm urls and update versions for 
> buildnumber-maven-plugin 
> -
>
> Key: ATLAS-486
> URL: https://issues.apache.org/jira/browse/ATLAS-486
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Selvamohan Neethiraj
>    Assignee: Selvamohan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: 
> 0001-ATLAS-486-updated-pom.xml-to-fix-scm-url-and-upgrade.patch
>
>
> Modify the pom.xml to fix scm url - which is missing (git) as part of the url
> Upgrade the plugin version of buildnumber-maven-plugin
> Parameterize skipTests ...



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

[jira] [Created] (ATLAS-486) Improvements to pom.xml to fix scm urls and update versions for buildnumber-maven-plugin

2016-02-15 Thread Selvamohan Neethiraj (JIRA) 
Selvamohan Neethiraj created ATLAS-486:
--

 Summary: Improvements to pom.xml to fix scm urls and update 
versions for buildnumber-maven-plugin 
 Key: ATLAS-486
 URL: https://issues.apache.org/jira/browse/ATLAS-486
 Project: Atlas
  Issue Type: Improvement
Reporter: Selvamohan Neethiraj
Assignee: Selvamohan Neethiraj
 Fix For: 0.7-incubating


Modify the pom.xml to fix scm url - which is missing (git) as part of the url
Upgrade the plugin version of buildnumber-maven-plugin
Parameterize skipTests ...



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

[jira] [Commented] (ATLAS-318) UI. Config file conatining UI: API endpoint + all api calls to be centralized -- config JS file for stand alone

2016-02-06 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-318:


The above comment is from an automated patch validation process.  This will 
ensure that, 
(a) The patch can be applied on master branch successfully w/out any error
(b) Has one or more Junit test cases - added/modified to validate the change
(c)  No javac compilation warnings are added - due to the patch [It compares 
the javac warnings before and after the patch]
(d)  No javadoc warnings are introduced by the patch 
(e)  No findbugs warnings are introduced by the patch
(f)   No Release Audit failures (like not having apache license headers in 
source) due to the patch
(g) No JUNIT tests are failing after applying the patch

This automated test is run on any patch that are attached to ATLAS jira - 
marked with PATCH_AVAIL status 

You should check and fix the patch and attach again to the JIRA and the 
validation process should automatically run and provides the feedback again.

You should check-in the patch only if:
(a) you get +1 for over-all patch 
OR 
(b) Have one of the ATLAS committers (other than the patch provider) to provide 
a +1 with enough justification.




> UI. Config file conatining UI: API endpoint + all api calls to be centralized 
> -- config JS file for stand alone
> ---
>
> Key: ATLAS-318
> URL: https://issues.apache.org/jira/browse/ATLAS-318
> Project: Atlas
>  Issue Type: Task
>Reporter: roshni gadiyar
>Assignee: Darshan Kumar
>Priority: Minor
>  Labels: Atlas-UI
> Attachments: ATLAS-318.patch
>
>
> Config file conatining API endpoint + all api calls to be centralized -- 
> config JS file for stand alone UI.



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

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

2016-02-03 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj commented on ATLAS-468:


validated the patch - by building the ATLAS and verified.

{code}
[INFO] 
[INFO] apache-atlas ... SUCCESS [  2.197 s]
[INFO] Apache Atlas Common  SUCCESS [  5.397 s]
[INFO] Apache Atlas Typesystem  SUCCESS [ 31.505 s]
[INFO] Apache Atlas Server API  SUCCESS [  2.762 s]
[INFO] Apache Atlas Client  SUCCESS [  7.060 s]
[INFO] Apache Atlas Notification .. SUCCESS [ 11.412 s]
[INFO] Apache Atlas Titan . SUCCESS [ 16.142 s]
[INFO] Apache Atlas Repository  SUCCESS [04:10 min]
[INFO] Apache Atlas UI  SUCCESS [ 35.791 s]
[INFO] Apache Atlas Web Application ... SUCCESS [03:16 min]
[INFO] Apache Atlas Documentation . SUCCESS [  3.535 s]
[INFO] Apache Atlas Hive Bridge ... SUCCESS [01:45 min]
[INFO] Apache Atlas Falcon Bridge . SUCCESS [ 28.005 s]
[INFO] Apache Atlas Sqoop Bridge .. SUCCESS [ 35.639 s]
[INFO] Apache Atlas Storm Bridge .. SUCCESS [ 58.438 s]
[INFO] Apache Atlas Distribution .. SUCCESS [  1.715 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 13:12 min
[INFO] Finished at: 2016-02-03T23:45:53-05:00
[INFO] Final Memory: 284M/3726M
[INFO] 
{code}

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



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