[jira] [Created] (ATLAS-1835) Unit tests not being run on Jenkins/mac

2017-05-26 Thread Apoorv Naik (JIRA) 
Apoorv Naik created ATLAS-1835:
--

 Summary: Unit tests not being run on Jenkins/mac
 Key: ATLAS-1835
 URL: https://issues.apache.org/jira/browse/ATLAS-1835
 Project: Atlas
  Issue Type: Bug
Reporter: Apoorv Naik
Assignee: Apoorv Naik


Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.35 sec - in 
org.apache.atlas.web.filters.AtlasCSRFPreventionFilterTest

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.393 sec - in 
org.apache.atlas.web.filters.AtlasAuthenticationSimpleFilterTest

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.366 sec - in 
org.apache.atlas.web.filters.AtlasAuthenticationKerberosFilterTest

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.34 sec - in 
org.apache.atlas.repository.impexp.ImportServiceReportingTest





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-05-26 Thread Apache Jenkins Server 
See 


Changes:

[apoorvnaik] ATLAS-1834: TestNG asserts over JUnit for consistency

--
[...truncated 274.01 KB...]
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 54 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding cannot be set as system property, use 
-Dfile.encoding=... instead

---
 T E S T S
---
Running org.apache.atlas.query.QueryProcessorTest
Running org.apache.atlas.query.GremlinTest
Running org.apache.atlas.query.BaseGremlinTest
Running org.apache.atlas.TestModules
Running org.apache.atlas.service.StoreBackedTypeCacheMetadataServiceTest
Running org.apache.atlas.query.ExpressionTest
Running org.apache.atlas.query.LineageQueryTest
Running org.apache.atlas.repository.impexp.ZipSourceTest
Running org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Running org.apache.atlas.repository.impexp.ExportServiceTest
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Running org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Running org.apache.atlas.service.DefaultMetadataServiceTest
Running org.apache.atlas.BaseRepositoryTest
Running org.apache.atlas.discovery.DataSetLineageServiceTest
Running org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
Running org.apache.atlas.query.ParserTest
Running org.apache.atlas.query.LexerTest
Running org.apache.atlas.repository.graph.Gremlin3QueryOptimizerTest
Running org.apache.atlas.repository.impexp.ImportServiceReportingTest
Running org.apache.atlas.repository.impexp.ImportServiceTest
Running org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryHATest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerTest
Running org.apache.atlas.repository.graph.GraphHelperTest
Running org.apache.atlas.repository.impexp.ZipSinkTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerMockTest
Running org.apache.atlas.repository.graph.AbstractGremlinQueryOptimizerTest
Running org.apache.atlas.repository.BaseTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateSoftDeleteTest
Running org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryTest
Running org.apache.atlas.repository.graph.GraphHelperMockTest
Running org.apache.atlas.RepositoryServiceLoadingTest
Running org.apache.atlas.repository.graph.Gremlin2QueryOptimizerTest
Running org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateV1Test
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateSoftDeleteV1Test
Running org.apache.atlas.repository.store.graph.v1.SoftDeleteHandlerV1Test
Running org.apache.atlas.repository.graph.GraphBackedRepositorySoftDeleteTest
Running org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1Test
Running org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
Running org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStoreTest
Running org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateHardDeleteTest
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Running org.apache.atlas.repository.store.graph.AtlasEntityDefStoreV1Test
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateHardDeleteV1Test
Running org.apache.atlas.repository.graph.TestIntSequence
Running

Re: [VOTE] Graduate Apache Atlas Project from Incubator

2017-05-26 Thread Sarath Subramanian 
+1 (binding)

Thanks to Atlas community for the next big step in the project.


Thanks,
Sarath Subramanian

On Wed, May 24, 2017 at 4:23 PM, Suma Shivaprasad <
sumasai.shivapra...@gmail.com> 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 Naik apoorvn...@apache.org 
> Ayub Pathan ayubpat...@apache.org 
> Barbara Stortz bsto...@sap.com 
> Chris Hyzer

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

2017-05-26 Thread Apoorv Naik (JIRA) 

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

Apoorv Naik updated ATLAS-1834:
---
Attachment: 0002-ATLAS-1834-TestNG-asserts-over-JUnit-for-consistency.patch

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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

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

2017-05-26 Thread Apoorv Naik (JIRA) 
Apoorv Naik created ATLAS-1834:
--

 Summary: TestNG asserts across tests instead on JUnit
 Key: ATLAS-1834
 URL: https://issues.apache.org/jira/browse/ATLAS-1834
 Project: Atlas
  Issue Type: Bug
Reporter: Apoorv Naik
Assignee: Apoorv Naik


Most of our tests use TestNG Asserts, only a handful of them are using JUnit. 
As a side-effect the builds on apache jenkins are failing because of the 
incorrect JUnit version getting picked from m2 repository, this causing certain 
tests to fail in-deterministically.

Changing all imports to TestNG



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Graduate Apache Atlas Project from Incubator

2017-05-26 Thread Madhan Neethiraj 
+1 (binding)

Thanks,
Madhan


On 5/24/17, 4: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

[jira] [Commented] (ATLAS-1821) Classification propagation from entity to a derivative or child entity

2017-05-26 Thread David Radley (JIRA) 

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

David Radley commented on ATLAS-1821:
-

[~jonesn] The example was one  [~Stefhan]  voiced in a recent call on this 
subject. This was the example of a case where he needed the Glossary term 
security level not to flow to the child asset.  

> Classification propagation from entity to a derivative or child entity
> --
>
> Key: ATLAS-1821
> URL: https://issues.apache.org/jira/browse/ATLAS-1821
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Reporter: Srikanth Venkat
> Fix For: 0.9-incubating
>
>
> User Story:
> As a data steward, I need a scalable way to quickly and efficiently propagate 
> classification across the information supply chain to support efficient 
> searches and classification based security for compliance and audit purposes. 
> This requires:
> 1. Classifications for derivative entities should be inherited from the 
> originator and to child entities from parent. 
> For example, if a Hive column is classified "Confidential" then resulting 
> column created from a CTAS operation should also be tagged "Confidential" to 
> maintain the classification of the original entity. In the case where 2 or 
> more entities are composed, the derivative entity should have the union of 
> all classifications of each source entity.
> 2. Business Terms:
> a. Child business terms should inherit the classifications associated with 
> the parent term.
> b. The option to propagate classification to child business terms in a 
> hierarchy should be provided
> c. Ability to update the propagated tags manually via UI or through the API
> d. Tagging a term should propagate to data assets that are already attached 
> to that business term as well
> 3. Data assets
> a. For all supported data asset types in Atlas, if a derivative asset is 
> created it should inherit the tags and attributes from the original asset.
> b. the option to propagate tags to child entities should be provided (e.g. if 
> you tag a folder in HDFS optionally tag all the files within it)
> c. Ability to update the propagated tags manually via UI or through the API
> d. Tagging a parent object should be inherited after child creation 
> dynamically (unless a flag is set not to do this)
> e. Derived data assets should have the tags of the original data asset.
> Conflict resolution - if there are different values for attributes on tags 
> (classifications) on upstream or parent entities used to derive a data asset 
> then user needs to be prompted for action to resolve the conflict. Once 
> resolved, the resolved value should be carried forth to derived assets.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (ATLAS-1821) Classification propagation from entity to a derivative or child entity

2017-05-26 Thread Nigel Jones (JIRA) 

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

Nigel Jones edited comment on ATLAS-1821 at 5/26/17 11:42 AM:
--

Srikanth,
 
I have some questions as to how tag propogation might work in the following 
scenario
 
For governance purposes I have a security classification "confidentiality"
This can be one of four values - public, internal, confidential, topsecret
 
I would apply it to a Database column ie "location" 
 
 
An asset cannot be classified with two different confidentialities
 
I see a few  approaches to this
 1a: preventing such a relationship being created
 1b: defining precedence when the data is retrieved (consumer centric 
interfaces might return only the "winner" whilst repository level generic 
interfaces might return a full list of relationships).  The precendence could 
be based on closeness to the entity and/or characteristics of the 
classification values (ie order)
 1c: allowing it and not specifying the meaning - this concerns me as different 
consumers may infer different things
 
Also how are we representing this characteristic of the classification?
 
Such a relationship could be created through the repository APIs. Recently 
there has also been a jira opened to discuss collections. This could also 
easily lead to the scenario above if tag propogation is allowed and IF 
collections are a first class object & can have classifications (as opposed to 
just being used to support set based operations whereby the actual columns 
would be updated... Which I'm ok with)
 
 - add entity to a collection with confidentiality=public
 - add entity to a a different  collection with confidentiality=topsecret
 
The same situation exists where classifications are associated with terms, if 
multiple terms are associated with the column.. Even if that isn't "likely 
"from a business perspective we need defined behaviour.
 
I see in the proposal above that
 * A union of all classifications is always presented. This does seem the 
simpler approach, but could lead to a dual classification of topsecret and 
public in the example above. If so we need to be aware of this and agree what 
it means. Purely down to the application (or higher api in the stack) to 
resolve?
 * conflict resolution is defined as a manual process. At the API level would 
this mean APIs would fail until a conflict is resolved. For example the term 
association causing the conflicting propogation would fail? The adding to a 
collection would fail? 
 
 
David,
 In your example can I check I understand your scenario
  * There is a "national insurance number" glossary term
  * this is classified as "confidential" (presumably using a confidentiality 
classification which can be one of the values I listed above)
  * the same "national insurance number" is mapped to two columns.
  * One of these columns is a clear-text representation of the national 
insurance number
  * One of these columns (so persisted in the database rather than computed at 
access time) is a masked form - perhaps just the first two characters
  * you assert we need rules
 
I'm not so sure Surely in this case those two columns are different 
business meanings? Either I would
 a) Create a different glossary term called "redacted national insurance 
number" & classify this as non-confidential
 b) Not even store the redacted form, and allow policies (ie in ranger) to do 
the masking at runtime
 
Even this scenario brings up tag propogation questions though... In a) above, 
should "redacted national insurance number" be related to "national insurance 
number". Yes I think it should. But should it inherit the classification. No. 
It could as a default of course, but then overriden to public. This brings us 
back to the original question of needing to control propogation.

I wonder if all inbound and outbound links need to the ability to
 * Allow outbound propogation"
 * Allow inbound propogation
 
Since both parties in the relationship need to have some say in this
 
Going back to the original point, some classifications may require to be 
unique, this is an additional attribute of the classification. Further it will 
automatically prevent inbound propogation of other instances of classifications 
of the same type. 
 
Apologies if I've not used the right terms as per the design 
doc/implementation, but hopefully you get the idea :-)




was (Author: jonesn):
Srikanth,

I have some questions as to how tag propogation might work in the following 
scenario

For governance purposes I have a security classification "confidentiality"
This can be one of four values - public, internal, confidential, topsecret

I would apply it to a Database column ie "location" 


An asset cannot be classified with two different confidentialities

I see a few  approaches to this 1a: preventing such a relationship being

[jira] [Commented] (ATLAS-1821) Classification propagation from entity to a derivative or child entity

2017-05-26 Thread Nigel Jones (JIRA) 

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

Nigel Jones commented on ATLAS-1821:


Srikanth,

I have some questions as to how tag propogation might work in the following 
scenario

For governance purposes I have a security classification "confidentiality"
This can be one of four values - public, internal, confidential, topsecret

I would apply it to a Database column ie "location" 


An asset cannot be classified with two different confidentialities

I see a few  approaches to this 1a: preventing such a relationship being 
created
 1b: defining precedence when the data is retrieved (consumer centric 
interfaces might return only the "winner" whilst repository level generic 
interfaces might return a full list of relationships).  The precendence could 
be based on closeness to the entity and/or characteristics of the 
classification values (ie order)
 1c: allowing it and not specifying the meaning - this concerns me as different 
consumers may infer different things

Also how are we representing this characteristic of the classification?

Such a relationship could be created through the repository APIs. Recently 
there has also been a jira opened to discuss collections. This could also 
easily lead to the scenario above if tag propogation is allowed and IF 
collections are a first class object & can have classifications (as opposed to 
just being used to support set based operations whereby the actual columns 
would be updated... Which I'm ok with)

 - add entity to a collection with confidentiality=public
 - add entity to a a different  collection with confidentiality=topsecret

The same situation exists where classifications are associated with terms, if 
multiple terms are associated with the column.. Even if that isn't "likely 
"from a business perspective we need defined behaviour.

I see in the proposal above that
 * A union of all classifications is always presented. This does seem the 
simpler approach, but could lead to a dual classification of topsecret and 
public in the example above. If so we need to be aware of this and agree what 
it means. Purely down to the application (or higher api in the stack) to 
resolve?
 * conflict resolution is defined as a manual process. At the API level would 
this mean APIs would fail until a conflict is resolved. For example the term 
association causing the conflicting propogation would fail? The adding to a 
collection would fail? 


David,
 In your example can I check I understand your scenario  * There is a 
"national insurance number" glossary term  * this is classified as 
"confidential" (presumably using a confidentiality classification which can be 
one of the values I listed above)
  * the same "national insurance number" is mapped to two columns.  * One of 
these columns is a clear-text representation of the national insurance number  
* One of these columns (so persisted in the database rather than computed at 
access time) is a masked form - perhaps just the first two characters
  * you assert we need rules

I'm not so sure Surely in this case those two columns are different 
business meanings? Either I would a) Create a different glossary term called 
"redacted national insurance number" & classify this as non-confidential b) 
Not even store the redacted form, and allow policies (ie in ranger) to do the 
masking at runtime

Even this scenario brings up tag propogation questions though... In a) above, 
should "redacted national insurance number" be related to "national insurance 
number". Yes I think it should. But should it inherit the classification. No. 
It could as a default of course, but then overriden to public. This brings us 
back to the original question of needing to control propogation.I wonder if 
all inbound and outbound links need to the ability to * Allow outbound 
propogation" * Allow inbound propogation

Since both parties in the relationship need to have some say in this

Going back to the original point, some classifications may require to be 
unique, this is an additional attribute of the classification. Further it will 
automatically prevent inbound propogation of other instances of classifications 
of the same type. 

Apologies if I've not used the right terms as per the design 
doc/implementation, but hopefully you get the idea :-)


> Classification propagation from entity to a derivative or child entity
> --
>
> Key: ATLAS-1821
> URL: https://issues.apache.org/jira/browse/ATLAS-1821
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Reporter: Srikanth Venkat
> Fix For: 0.9-incubating
>
>
> User Story:
> As a data steward, I need a scalable way to quickly and efficiently

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

2017-05-26 Thread Apache Jenkins Server 
See 


Changes:

[nixon] ATLAS-1810 : UI : Audit details of any tag event (Added,Updated) has

[nixon] ATLAS-1808:UI : All selected entities are assigned to tag when Assign

[nixon] ATLAS-1809 : UI : Update button in Edit tag attributes window should be

[nixon] ATLAS-1811 : UI : Audit Events are not shown in sorted order based on

[nixon] ATLAS-1817 : UI : n+1 pages are created, even though only n*25 instances

--
[...truncated 326.58 KB...]
[WARNING] var repo = new GraphBackedMetadataRepository(null, new 
AtlasGraphProvider().get());
[WARNING]^
[WARNING] 
:175:
 trait MetadataRepository in package repository is deprecated: see 
corresponding Javadoc for more information.
[WARNING] def setupTestGraph(repo : MetadataRepository): AtlasGraph[_,_] = {
[WARNING]   ^
[WARNING] four warnings found
[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 54 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding cannot be set as system property, use 
-Dfile.encoding=... instead

---
 T E S T S
---
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateHardDeleteTest
Running org.apache.atlas.repository.graph.Gremlin3QueryOptimizerTest
Running org.apache.atlas.service.DefaultMetadataServiceTest
Running org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryTest
Running org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStoreTest
Running org.apache.atlas.repository.graph.GraphHelperMockTest
Running org.apache.atlas.service.StoreBackedTypeCacheMetadataServiceTest
Running org.apache.atlas.services.MetricsServiceTest
Running org.apache.atlas.services.EntityDiscoveryServiceTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerMockTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateSoftDeleteTest
Running org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Running org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1Test
Running org.apache.atlas.repository.graph.GraphHelperTest
Running org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateV1Test
Running org.apache.atlas.BaseRepositoryTest
Running org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1Test
Running org.apache.atlas.repository.store.graph.AtlasEntityDefStoreV1Test
Running org.apache.atlas.repository.store.graph.v1.SoftDeleteHandlerV1Test
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Running org.apache.atlas.repository.graph.Gremlin2QueryOptimizerTest
Running org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
Running org.apache.atlas.repository.impexp.ImportServiceTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerTest
Running org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Running org.apache.atlas.repository.graph.AbstractGremlinQueryOptimizerTest
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateSoftDeleteV1Test
Running org.apache.atlas.util.CompiledQueryCacheKeyTest
Running

[jira] [Created] (ATLAS-1833) (Create Tag) - If a Tag is created without description then in update Description tag name appears.

2017-05-26 Thread Kalyani Kashikar (JIRA) 
Kalyani Kashikar created ATLAS-1833:
---

 Summary: (Create Tag) - If a Tag is created without description 
then in update Description tag name appears.
 Key: ATLAS-1833
 URL: https://issues.apache.org/jira/browse/ATLAS-1833
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Kalyani Kashikar
Assignee: Nixon Rodrigues


requestJSON -
{code}
{
"classificationDefs": [{
"name": "test2",
"description": "",
"superTypes": [],
"attributeDefs": []
}],
"entityDefs": [],
"enumDefs": [],
"structDefs": []
}
{code}
ResponseJSON :
{code}
{
"enumDefs": [],
"structDefs": [],
"classificationDefs": [{
"category": "CLASSIFICATION",
"guid": "cb2af955-d2de-4754-bcdf-58f76763c293",
"createTime": 1495795905288,
"updateTime": 1495795905288,
"version": 1,
"name": "test2",
"description": "test2",
"typeVersion": "1.0",
"attributeDefs": [],
"superTypes": []
}],
"entityDefs": []
}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1768) Create common types for Open Metadata

2017-05-26 Thread David Radley (JIRA) 

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

David Radley commented on ATLAS-1768:
-

[~mandy_chessell] Thanks for your quick responses. I am left with 2 thoughts : 
I am wondering why a sub category life cycle is not tied to the parents. What 
is the thinking here? I thought it would be a true tree; so we would stop the 
deletion of a parent if it had children or have explicit delete subtree API. I 
understand that the child categories could be moved to top level categories if 
the parent is deleted;  this seems odd, as categories half way down a hierarchy 
may not make a lot of sense as top level categories. If this end state is 
desired - I suggest the child category should be explicitly moved to the top 
prior and this move not occur as part of the parent category deletion. Also for 
soft deletes if the children categories are deleted prior to the parent - this 
leaves the graph reflecting the before state more accurately as the parent 
pointer would still point to the old parent.  

I am not seeing where Classifications have cardinality in the current Atlas 
model; I only see cardinality around attributeDefs (and soon to be 
relationshipDefs). I think adding cardinality to ClassificationDef would be 
useful - the Atlas code could then police this constraint.  


> Create common types for Open Metadata
> -
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: VirtualDataConnector
>
> This JIRA describes a proposal for standard types for open metadata entities 
> and relationships.  For example, glossaries, database definitions, rules, 
> policies, ...
> The value of having standard definitions for metadata is to enable type safe 
> APIs and business level UIs plus be able to exchange metadata between 
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and 
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and 
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see 
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common 
> definitions must be extensible - and we still need to support the ad hoc 
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new 
> types.  These are currently enumeration, struct, classification and entity.  
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to 
> this list.  The open metadata models make use of all of these meta-types.  
> These are represented by sterotypes on the classes of the open metadata 
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the 
> easiest way to view the models.
> Start here: 
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-05-26 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues updated ATLAS-1832:
---
Component/s: atlas-webui

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




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-05-26 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues updated ATLAS-1832:
---
Affects Version/s: 0.8-incubating

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




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-05-26 Thread Nixon Rodrigues (JIRA) 
Nixon Rodrigues created ATLAS-1832:
--

 Summary: If no attribute is present in tag  then showing 
edit-button for a tag in tags tab on entity page.
 Key: ATLAS-1832
 URL: https://issues.apache.org/jira/browse/ATLAS-1832
 Project: Atlas
  Issue Type: Bug
 Environment: Chrome
Reporter: Nixon Rodrigues
Assignee: Kalyani Kashikar
 Attachments: edit attribute for tag bug .png





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-05-26 Thread Apache Jenkins Server 
See 


Changes:

[kalyani.kashikar] Add committer Information

--
[...truncated 330.72 KB...]
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 54 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding cannot be set as system property, use 
-Dfile.encoding=... instead

---
 T E S T S
---
Running org.apache.atlas.discovery.DataSetLineageServiceTest
Running org.apache.atlas.TestModules
Running org.apache.atlas.query.ExpressionTest
Running org.apache.atlas.query.BaseGremlinTest
Running org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Running org.apache.atlas.repository.impexp.ImportServiceTest
Running org.apache.atlas.service.DefaultMetadataServiceTest
Running org.apache.atlas.query.ParserTest
Running org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryTest
Running org.apache.atlas.BaseRepositoryTest
Running org.apache.atlas.repository.impexp.ZipSourceTest
Running org.apache.atlas.query.LineageQueryTest
Running org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
Running org.apache.atlas.repository.impexp.ExportServiceTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateSoftDeleteTest
Running org.apache.atlas.query.LexerTest
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryHATest
Running org.apache.atlas.repository.BaseTest
Running org.apache.atlas.repository.impexp.ZipSinkTest
Running org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Running org.apache.atlas.query.GremlinTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerTest
Running org.apache.atlas.service.StoreBackedTypeCacheMetadataServiceTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerMockTest
Running org.apache.atlas.repository.graph.AbstractGremlinQueryOptimizerTest
Running org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Running org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Running org.apache.atlas.query.QueryProcessorTest
Running org.apache.atlas.repository.graph.GraphHelperMockTest
Running org.apache.atlas.repository.graph.GraphHelperTest
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateHardDeleteV1Test
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Running org.apache.atlas.repository.graph.GraphBackedRepositorySoftDeleteTest
Running org.apache.atlas.repository.store.graph.v1.SoftDeleteHandlerV1Test
Running org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
Running org.apache.atlas.repository.graph.Gremlin3QueryOptimizerTest
Running org.apache.atlas.repository.impexp.ImportServiceReportingTest
Running org.apache.atlas.repository.graph.Gremlin2QueryOptimizerTest
Running org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateV1Test
Running org.apache.atlas.repository.store.graph.AtlasEntityDefStoreV1Test
Running org.apache.atlas.RepositoryServiceLoadingTest
Running org.apache.atlas.repository.graph.TestIntSequence
Running org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1Test
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateSoftDeleteV1Test
Running org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStoreTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateHardDeleteTest
Running

[jira] [Commented] (ATLAS-1809) UI : Update button in Edit tag attributes window should be enabled only when any update is done

2017-05-26 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues commented on ATLAS-1809:


+1 for the patch.


> UI : Update button in Edit tag attributes window should be enabled only when 
> any update is done
> ---
>
> Key: ATLAS-1809
> URL: https://issues.apache.org/jira/browse/ATLAS-1809
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
>Priority: Minor
> Attachments: ATLAS-1809.patch
>
>
> Even though no update is made to any of the attributes of tag associated to 
> entity, "Update" button is enabled in Edit Tag window . Audit is also 
> generated with event 'Tag Updated'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1811) UI : Audit Events are not shown in sorted order based on time sometimes.

2017-05-26 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues commented on ATLAS-1811:


+1 for the patch.


> UI : Audit Events are not shown in sorted order based on time sometimes.
> 
>
> Key: ATLAS-1811
> URL: https://issues.apache.org/jira/browse/ATLAS-1811
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1811.patch, AuditDetailsUnordered.png
>
>
> Created an entity and made did many tag association , dis-association and tag 
> update to that entity. All audit details are captured but not displayed in 
> sorted order based on timestamp value present in audit response. A few 
> entries are missing order.
> Attached the screenshot .



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.

2017-05-26 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues commented on ATLAS-1817:


+1 for the patch.


> UI : n+1 pages are created, even though only n*25 instances are retrieved.
> --
>
> Key: ATLAS-1817
> URL: https://issues.apache.org/jira/browse/ATLAS-1817
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1817.patch
>
>
> 1.Created 50 tables.
> 2.First page showed 1-25 tables , second page 26 -50 tables .
> 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty 
> response.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1810) UI : Audit details of any tag event (Added,Updated) has only tag name and event.

2017-05-26 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues commented on ATLAS-1810:


+1 for the patch.

> UI : Audit details of any tag event (Added,Updated) has only tag name and 
> event.
> 
>
> Key: ATLAS-1810
> URL: https://issues.apache.org/jira/browse/ATLAS-1810
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
>Priority: Minor
> Attachments: ATLAS-1810.patch
>
>
> On clicking Details of Audit events like "Tag Added" , "Tag updated" in Audit 
> tab , Details window shows only the Audit event and tag name. Tag attributes 
> are not displayed. Since "Edit Attribute of Tag" feature is introduced, it 
> would be good to display the attributes of tag like it does for Entities.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1808) UI : All selected entities are assigned to tag when Assign Tag corresponding to 1 entity is clicked.

2017-05-26 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues commented on ATLAS-1808:


+1 for the patch.


> UI : All selected entities are assigned to tag when Assign Tag corresponding 
> to 1 entity is clicked.
> 
>
> Key: ATLAS-1808
> URL: https://issues.apache.org/jira/browse/ATLAS-1808
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Attachments: ATLAS-1808.1.patch, ATLAS-1808.patch
>
>
> Steps:
> 1. Searched for type hive_table which listed 10 results.
> 2. Selected all the entities (using check box).
> 3. Clicked on Assign tag button corresponding to the first result ex : table1 
> ( "+" sign button with class a.InputTagAdd.assignTag)
> 4. Selected the tag to be assigned ex:tag1
> 5. Expected tag1 would be assigned to only table1 though all the entities are 
> selected. But all the entities are assigned to tag1.
> Note : Didn't click on Button with text  " + Assign Tag" (class : 
> a.inputAssignTag.multiSelectTag.assignTag.btnAssign) after selecting multiple 
> entities.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)