[jira] [Created] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-2730:
--

 Summary: Invalid timezone / start time / end time is accepted by 
classification API
 Key: ATLAS-2730
 URL: https://issues.apache.org/jira/browse/ATLAS-2730
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 1.0.0
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: trunk






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

[jira] [Updated] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-2730:
---
Issue Type: Bug  (was: New Feature)

> Invalid timezone / start time / end time is accepted by classification API
> --
>
> Key: ATLAS-2730
> URL: https://issues.apache.org/jira/browse/ATLAS-2730
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: trunk
>
>




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

Build failed in Jenkins: PreCommit-ATLAS-Build-Test #461-master-0001-ATLAS-2730-Timeboundry-datetime-timezone-validation.patch

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2728: UI renders integer attribute values as date -

[madhan] ATLAS-2729: fix - audit logging fails for large entities

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

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 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

---
 T E S T S
---
Running org.apache.atlas.repository.migration.TypesWithCollectionsFinderTest
Running org.apache.atlas.repository.migration.RelationshipCacheGeneratorTest
Running org.apache.atlas.repository.migration.TypesWithClassificationTest
Running org.apache.atlas.repository.migration.HiveParititionTest
Running org.apache.atlas.repository.impexp.TypeAttributeDifferenceTest
Running org.apache.atlas.repository.migration.MigrationProgressServiceTest
Running org.apache.atlas.repository.migration.PathTest
Running org.apache.atlas.repository.impexp.ZipSinkTest
Running org.apache.atlas.glossary.GlossaryServiceTest
Running 
org.apache.atlas.repository.store.graph.v2.InverseReferenceUpdateSoftDeleteV2Test
Running 
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2BulkImportPercentTest
Running org.apache.atlas.repository.impexp.UniqueListTest
Running org.apache.atlas.glossary.PaginationHelperTest
Running org.apache.atlas.repository.migration.TypesDefScrubberTest
Running org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2Test
Running 
org.apache.atlas.repository.store.graph.v2.InverseReferenceUpdateHardDeleteV2Test
Running org.apache.atlas.repository.audit.CassandraAuditRepositoryTest
Running org.apache.atlas.repository.store.graph.v2.AtlasComplexAttributesTest
Running org.apache.atlas.repository.migration.HiveStocksTest
Running org.apache.atlas.repository.impexp.ZipSourceTest
Running org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreV2Test
Running org.apache.atlas.repository.store.graph.v2.AtlasEntityDefStoreV2Test
Running org.apache.atlas.utils.TestResourceFileUtils
Running 
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipDefStoreV2Test
Running 
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreHardDeleteV2Test
Running org.apache.atlas.repository.impexp.ImportTransformsTest
Running org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Running org.apache.atlas.repository.userprofile.UserProfileServiceTest
Running org.apache.atlas.repository.store.graph.v2.InverseReferenceUpdateV2Test
Running org.apache.atlas.services.MetricsServiceTest
Running org.apache.atlas.repository.impexp.AtlasImportRequestTest
Running org.apache.atlas.repository.impexp.ImportTransformerTest
Running org.apache.atlas.query.DSLParsingTest
Running org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStoreTest
Running org.apache.atlas.query.DSLQueriesTest
Running org.apache.atlas.repository.impexp.ImportTransformerJSONTest
Running org.apache.atlas.TestModules
Running org.apache.atlas.query.GremlinQueryComposerTest
Running org.apache.atlas.repository.impexp.ExportServiceTest
Running 
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreSoftDeleteV2Test
Running org.apache.atlas.repository.impexp.ImportServiceTest
Running org.apache.atlas.repository.migration.ComplexAttributesTest
Running org.apache.atlas.repository.tagpropagation.ClassificationPropagationTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.548 sec - in 
org.apache.atlas.repository.store.graph.v2.AtlasRelationsh

[jira] [Created] (ATLAS-2731) UI : attributes on table's detailsPage buffers forever due no access on that entity type

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-2731:
--

 Summary: UI : attributes on table's detailsPage buffers forever 
due no access on that entity type
 Key: ATLAS-2731
 URL: https://issues.apache.org/jira/browse/ATLAS-2731
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 1.0.0
Reporter: Nixon Rodrigues
 Fix For: trunk


1. Create a Resource based policy for Atlas in Ranger with Entity-id as 
qualifiedName of a table, with all permissions , entity-type= * 
,entity-classification=* for "admin" user. (Attached the screenshot of the 
policy)
2. Log into Atlas as admin and access table's detailsPage.
3. db attribute value keeps loading forever and there is an "admin is not 
authorized to perform read entity: guid=" error notification.



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

Re: Problem deleting edges with 1.0.0 - pre rc

[David Radley]

Hi Pierre,
Just so I am clear, does"Entity A -> Composition Relationship -> Entity B" 
mean that B or A is the container?

If B is the container then - you should be able to delete A. You are 
saying that B can be deleted and leaves its part A. If this is the case 
then I would suggest that the code could be enhanced to either stop this 
sort of deletion or delete it and all of its composed parts. I suggest 
this is not a stopper for v1.0, as you have a circumvention where you 
manually delete each entity. 

If this is an issue - I suggest looking at AtlasEntityStoreV1 deleteById 
to add some checking around composition relationships prior to deletion, 

   all the best, David. 
 




From:   Pierre Padovani 
To: dev@atlas.apache.org
Date:   31/05/2018 17:47
Subject:Re: Problem deleting edges with 1.0.0 - pre rc



Sorry for the spam... One last data point. It looks like the deletion of B
is the issue. I can delete A, but this doesn't delete B.

On Thu, May 31, 2018 at 11:21 AM, Pierre Padovani <
pierre.padov...@civitaslearning.com> wrote:

> The level we are using is a few weeks old, but I didn't see an issue 
that
> fixed this in the interim.
>
> Problem:
>
> Entity A -> Composition Relationship -> Entity B
>
> Delete Entity A and Entity B
>
> I get the following exception trace:
>
> java.lang.IllegalArgumentException: Invalid edge label
> r:DiscoveryPackTables: expected 2 or 3 label components but found 1 at
> 
org.apache.atlas.repository.graph.AtlasEdgeLabel.(AtlasEdgeLabel.java:37)
> at org.apache.atlas.repository.store.graph.v1.DeleteHandlerV1.
> getAttributeForEdge(DeleteHandlerV1.java:722) at
> 
org.apache.atlas.repository.store.graph.v1.DeleteHandlerV1.deleteVertex(DeleteHandlerV1.java:865)
> at org.apache.atlas.repository.store.graph.v1.DeleteHandlerV1.
> deleteTypeVertex(DeleteHandlerV1.java:718) at 
org.apache.atlas.repository.
> store.graph.v1.DeleteHandlerV1.deleteEntities(DeleteHandlerV1.java:140)
> at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.
> deleteVertices(AtlasEntityStoreV1.java:704) at
> 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.deleteById(AtlasEntityStoreV1.java:297)
> at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1$$
> FastClassBySpringCGLIB$$80c00649.invoke() at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.
> invokeJoinpoint(CglibAopProxy.java:738) at org.springframework.aop.
> 
framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at org.apache.atlas.GraphTransactionInterceptor.invoke(
> GraphTransactionInterceptor.java:75) at 
org.springframework.aop.framework.
> ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at org.springframework.aop.framework.CglibAopProxy$
> DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673) at
> org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1$$
> EnhancerBySpringCGLIB$$2072786c.deleteById() at
> org.apache.atlas.web.rest.EntityREST.deleteByGuid(EntityREST.java:327) 
at
> sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43) at 
java.lang.reflect.Method.invoke(Method.java:498)
> at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(
> JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.
> model.method.dispatch.AbstractResourceMethodDispatch
> 
Provider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at com.sun.jersey.server.impl.model.method.dispatch.
> 
ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.
> accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.
> uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.
> accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.
> uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(
> RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.
> 
application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at com.sun.jersey.server.impl.application.WebApplicationImpl._
> handleRequest(WebApplicationImpl.java:1473) at 
com.sun.jersey.server.impl.
> 
application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at com.sun.jersey.server.impl.application.WebApplicationImpl.
> handleRequest(WebApplicationImpl.java:1409) at
> 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at com.sun.jersey.spi.container.servlet.ServletContainer.
> service(ServletContainer.java:558) at com.sun.jersey.spi.container.
> servlet.ServletContainer.service(ServletContainer.java:733) at
> javax.servlet.http.HttpServlet.servi

Re: Problem deleting edges with 1.0.0 - pre rc

[Graham Wallis]

Hi David - I think is already fixed.


Best regards,
  Graham

Graham Wallis
IBM Analytics
Internet: graham_wal...@uk.ibm.com 
IBM Laboratories, Hursley Park, Hursley, Hampshire SO21 2JN
Tel: +44 7741 379735




From:   David Radley 
To: dev@atlas.apache.org
Date:   01/06/2018 10:55
Subject:Re: Problem deleting edges with 1.0.0 - pre rc



Hi Pierre,
Just so I am clear, does"Entity A -> Composition Relationship -> Entity B" 

mean that B or A is the container?

If B is the container then - you should be able to delete A. You are 
saying that B can be deleted and leaves its part A. If this is the case 
then I would suggest that the code could be enhanced to either stop this 
sort of deletion or delete it and all of its composed parts. I suggest 
this is not a stopper for v1.0, as you have a circumvention where you 
manually delete each entity. 

If this is an issue - I suggest looking at AtlasEntityStoreV1 deleteById 
to add some checking around composition relationships prior to deletion, 

   all the best, David. 
 




From:   Pierre Padovani 
To: dev@atlas.apache.org
Date:   31/05/2018 17:47
Subject:Re: Problem deleting edges with 1.0.0 - pre rc



Sorry for the spam... One last data point. It looks like the deletion of B
is the issue. I can delete A, but this doesn't delete B.

On Thu, May 31, 2018 at 11:21 AM, Pierre Padovani <
pierre.padov...@civitaslearning.com> wrote:

> The level we are using is a few weeks old, but I didn't see an issue 
that
> fixed this in the interim.
>
> Problem:
>
> Entity A -> Composition Relationship -> Entity B
>
> Delete Entity A and Entity B
>
> I get the following exception trace:
>
> java.lang.IllegalArgumentException: Invalid edge label
> r:DiscoveryPackTables: expected 2 or 3 label components but found 1 at
> 
org.apache.atlas.repository.graph.AtlasEdgeLabel.(AtlasEdgeLabel.java:37)
> at org.apache.atlas.repository.store.graph.v1.DeleteHandlerV1.
> getAttributeForEdge(DeleteHandlerV1.java:722) at
> 
org.apache.atlas.repository.store.graph.v1.DeleteHandlerV1.deleteVertex(DeleteHandlerV1.java:865)
> at org.apache.atlas.repository.store.graph.v1.DeleteHandlerV1.
> deleteTypeVertex(DeleteHandlerV1.java:718) at 
org.apache.atlas.repository.
> store.graph.v1.DeleteHandlerV1.deleteEntities(DeleteHandlerV1.java:140)
> at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.
> deleteVertices(AtlasEntityStoreV1.java:704) at
> 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.deleteById(AtlasEntityStoreV1.java:297)
> at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1$$
> FastClassBySpringCGLIB$$80c00649.invoke() at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.
> invokeJoinpoint(CglibAopProxy.java:738) at org.springframework.aop.
> 
framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at org.apache.atlas.GraphTransactionInterceptor.invoke(
> GraphTransactionInterceptor.java:75) at 
org.springframework.aop.framework.
> ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at org.springframework.aop.framework.CglibAopProxy$
> DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673) at
> org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1$$
> EnhancerBySpringCGLIB$$2072786c.deleteById() at
> org.apache.atlas.web.rest.EntityREST.deleteByGuid(EntityREST.java:327) 
at
> sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43) at 
java.lang.reflect.Method.invoke(Method.java:498)
> at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(
> JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.
> model.method.dispatch.AbstractResourceMethodDispatch
> 
Provider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at com.sun.jersey.server.impl.model.method.dispatch.
> 
ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.
> accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.
> uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.
> accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.
> uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(
> RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.
> 
application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at com.sun.jersey.server.impl.application.WebApplicationImpl._
> handleRequest(WebApplicationImpl.java:1473) at 
com.sun.jersey.server.impl.
> 
application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at com.sun.jersey.server.impl.application.WebApplicationImpl.
> handleReq

Re: [VOTE] Release Apache Atlas version 1.0.0 - rc2

[David Radley]

Thanks Madhan for putting out the release candidate 2 for Apache Atlas 1.0


  - Built with embedded-hbase-solr profile successfully with no test 
failures
  - built with clean install with no test failures.
  - Ran quick start and the UI.

+1 for release candidate #2.

all the best, David. 

From:   Sarath Subramanian 
To: dev@atlas.apache.org
Date:   31/05/2018 17:17
Subject:Re: [VOTE] Release Apache Atlas version 1.0.0 - rc2



Thanks Madhan for putting out the release candidate 2 for Apache Atlas 1.0

   - Verified checksum and signature
   - Built with embedded-hbase-solr profile successfully with no test
   failures.
   - Validated new functionalities - glossary, relationships, lineage, tag
   propagation and UI enhancements

+1 for release candidate #2.


Thanks,
Sarath Subramanian


On Wed, May 30, 2018 at 12:31 AM, Madhan Neethiraj 
wrote:

> Atlas team,
>
> Apache Atlas 1.0.0 release candidate #2 is now available for a vote 
within
> dev community.
>
> Following commit went into branch-1.0 since the last release candidate,
> #1, was sent yesterday.
>   ATLAS-2726: updated migration-import to add __name property to
> classification edges
>
> Links to the release artifacts are given below. Please review and vote.
>
> The vote will be open for at least 72 hours or until necessary votes are
> reached.
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove (and reason why)
>
> Thanks,
> Madhan
>
>
> List of issues addressed in this release: 
https://issues.apache.org/

> jira/issues/?jql=project%20%3D%20Atlas%20AND%20resolution%
> 20!%3D%20Unresolved%20%20AND%20fixVersion%20%3D%201.0.0%
> 20ORDER%20BY%20key%20DESC
>
> Git tag for the release: 
https://github.com/apache/

> atlas/tree/release-1.0.0-rc2
>
> Sources for the release: 
https://dist.apache.org/repos/

> dist/dev/atlas/1.0.0-rc2/apache-atlas-1.0.0-sources.tar.gz
>
> Documentation for the release: 
http://atlas.apache.org/1.0.0-

> rc0/index.html
>
> Source release verification:
>   PGP Signature: 
https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/

> apache-atlas-1.0.0-sources.tar.gz.asc
>   SHA512 Hash: 
https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/

> apache-atlas-1.0.0-sources.tar.gz.sha512
>
> Keys to verify the signature of the release artifacts are available at:
> 
https://dist.apache.org/repos/dist/dev/atlas/KEYS

>
>
>
>



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [VOTE] Release Apache Atlas version 1.0.0 - rc2

[Nixon Rodrigues]

+1 for 1.0.0-rc2.

Thanks Madhan for putting Atlas 1.0.0 for release.

Nixon Rodrigues


On Fri, Jun 1, 2018, 5:20 PM David Radley  wrote:

> Thanks Madhan for putting out the release candidate 2 for Apache Atlas 1.0
>
>
>   - Built with embedded-hbase-solr profile successfully with no test
> failures
>   - built with clean install with no test failures.
>   - Ran quick start and the UI.
>
> +1 for release candidate #2.
>
> all the best, David.
>
> From:   Sarath Subramanian 
> To: dev@atlas.apache.org
> Date:   31/05/2018 17:17
> Subject:Re: [VOTE] Release Apache Atlas version 1.0.0 - rc2
>
>
>
> Thanks Madhan for putting out the release candidate 2 for Apache Atlas 1.0
>
>- Verified checksum and signature
>- Built with embedded-hbase-solr profile successfully with no test
>failures.
>- Validated new functionalities - glossary, relationships, lineage, tag
>propagation and UI enhancements
>
> +1 for release candidate #2.
>
>
> Thanks,
> Sarath Subramanian
>
>
> On Wed, May 30, 2018 at 12:31 AM, Madhan Neethiraj 
> wrote:
>
> > Atlas team,
> >
> > Apache Atlas 1.0.0 release candidate #2 is now available for a vote
> within
> > dev community.
> >
> > Following commit went into branch-1.0 since the last release candidate,
> > #1, was sent yesterday.
> >   ATLAS-2726: updated migration-import to add __name property to
> > classification edges
> >
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove (and reason why)
> >
> > Thanks,
> > Madhan
> >
> >
> > List of issues addressed in this release:
> https://issues.apache.org/
>
> > jira/issues/?jql=project%20%3D%20Atlas%20AND%20resolution%
> > 20!%3D%20Unresolved%20%20AND%20fixVersion%20%3D%201.0.0%
> > 20ORDER%20BY%20key%20DESC
> >
> > Git tag for the release:
> https://github.com/apache/
>
> > atlas/tree/release-1.0.0-rc2
> >
> > Sources for the release:
> https://dist.apache.org/repos/
>
> > dist/dev/atlas/1.0.0-rc2/apache-atlas-1.0.0-sources.tar.gz
> >
> > Documentation for the release:
> http://atlas.apache.org/1.0.0-
>
> > rc0/index.html
> >
> > Source release verification:
> >   PGP Signature:
> https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/
>
> > apache-atlas-1.0.0-sources.tar.gz.asc
> >   SHA512 Hash:
> https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/
>
> > apache-atlas-1.0.0-sources.tar.gz.sha512
> >
> > Keys to verify the signature of the release artifacts are available at:
> >
> https://dist.apache.org/repos/dist/dev/atlas/KEYS
>
> >
> >
> >
> >
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>

Jenkins build is back to normal : PreCommit-ATLAS-Build-Test #462-master-0001-ATLAS-2730-Timeboundry-datetime-timezone-validation.patch

[Apache Jenkins Server]

See 

Review Request 67410: ATLAS-2730 : TimeBoundry date time validation during addclassification and updateClassifcation of entity.

[Nixon Rodrigues]

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

Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, Ruchi 
Solani, and Sarath Subramanian.


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


Repository: atlas


Description
---

This patch includes validation of classifcation TimeBoundry date time timezone 
during addclassification and updateClassifcation of entity.


Diffs
-

  intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 06b43458b 
  repository/pom.xml a6ee43f61 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
 5e33cf59f 
  repository/src/main/java/org/apache/atlas/util/DateTimeUtil.java PRE-CREATION 


Diff: https://reviews.apache.org/r/67410/diff/1/


Testing
---

Tested adding / updating classifcation with / invalid / without 
TimeBoundry/datetime timezeone from UI and from API.
Existing UT and IT passing.
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/462/console


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-2730:
---
Attachment: ATLAS-2730.patch

> Invalid timezone / start time / end time is accepted by classification API
> --
>
> Key: ATLAS-2730
> URL: https://issues.apache.org/jira/browse/ATLAS-2730
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-2730.patch
>
>




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

[jira] [Assigned] (ATLAS-2731) UI : attributes on table's detailsPage buffers forever due no access on that entity type

[Abhishek Kadam (JIRA)]

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

Abhishek Kadam reassigned ATLAS-2731:
-

Assignee: Abhishek Kadam

> UI : attributes on table's detailsPage buffers forever due no access on that 
> entity type
> 
>
> Key: ATLAS-2731
> URL: https://issues.apache.org/jira/browse/ATLAS-2731
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: trunk
>
>
> 1. Create a Resource based policy for Atlas in Ranger with Entity-id as 
> qualifiedName of a table, with all permissions , entity-type= * 
> ,entity-classification=* for "admin" user. (Attached the screenshot of the 
> policy)
> 2. Log into Atlas as admin and access table's detailsPage.
> 3. db attribute value keeps loading forever and there is an "admin is not 
> authorized to perform read entity: guid=" error notification.



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

[jira] [Updated] (ATLAS-2731) UI : attributes on table's detailsPage buffers forever due no access on that entity type

[Abhishek Kadam (JIRA)]

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

Abhishek Kadam updated ATLAS-2731:
--
Fix Version/s: (was: trunk)

> UI : attributes on table's detailsPage buffers forever due no access on that 
> entity type
> 
>
> Key: ATLAS-2731
> URL: https://issues.apache.org/jira/browse/ATLAS-2731
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Abhishek Kadam
>Priority: Major
> Attachments: ATLAS-2731.patch
>
>
> 1. Create a Resource based policy for Atlas in Ranger with Entity-id as 
> qualifiedName of a table, with all permissions , entity-type= * 
> ,entity-classification=* for "admin" user. (Attached the screenshot of the 
> policy)
> 2. Log into Atlas as admin and access table's detailsPage.
> 3. db attribute value keeps loading forever and there is an "admin is not 
> authorized to perform read entity: guid=" error notification.



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

[jira] [Updated] (ATLAS-2731) UI : attributes on table's detailsPage buffers forever due no access on that entity type

[Abhishek Kadam (JIRA)]

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

Abhishek Kadam updated ATLAS-2731:
--
Attachment: ATLAS-2731.patch

> UI : attributes on table's detailsPage buffers forever due no access on that 
> entity type
> 
>
> Key: ATLAS-2731
> URL: https://issues.apache.org/jira/browse/ATLAS-2731
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Abhishek Kadam
>Priority: Major
> Attachments: ATLAS-2731.patch
>
>
> 1. Create a Resource based policy for Atlas in Ranger with Entity-id as 
> qualifiedName of a table, with all permissions , entity-type= * 
> ,entity-classification=* for "admin" user. (Attached the screenshot of the 
> policy)
> 2. Log into Atlas as admin and access table's detailsPage.
> 3. db attribute value keeps loading forever and there is an "admin is not 
> authorized to perform read entity: guid=" error notification.



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

Re: Add me as a contributor

[Abhishek Kadam]

Hi Madhan,

I have submitted the patch ATLAS-2731
, but I am not able to
change the status of the Jira.

Thanks,
Abhishek

On Wed, May 30, 2018 at 9:32 PM, Madhan Neethiraj  wrote:

> Abhishek,
>
> Thanks for your interest in contributing to Apache Atlas. You have been
> added as a contributor. Welcome to Apache Atlas community!
>
> Regards,
> Madhan
>
>
>
>
> On 5/30/18, 8:52 AM, "Abhishek Kadam"  wrote:
>
> Atlas Team, Please add me as a contributor for Apache Atlas project. My
> jira id is abhib4
> *Thanks and Regards,*
> *Abhishek Kadam*
>
>
>
>


-- 
*Thanks and Regards,*
*Abhishek Kadam*

*(8652340908)*

Performance of relationships

[Pierre Padovani]

All,

I decided to spend a few cycles performing from basic performance tests to
help us refine our type system. The goal was to determine how we would add
relationships to our entities and if we would use the new relationship APIs
or not. The test was simple. I created a type called container and a type
called child both extending DataSet. I think created an instance of
container, and added one child at a time to the container recording the
cost of the add, and the cost of fetching the container after each add.

There were three tests run:

- Legacy - Assign the entities to the attributes in the attribute map
- Hybrid - Leave the legacy attributes in the type system, and use the
relationship APIs
- V2 - Remove the legacy attributes and use the relationship APIs

Here are the results for 100 children:



Is there a reason we are continuing to use legacy attributes in the type
system(s) we are shipping with Atlas? From a performance perspective this
does not seem like a reasonable thing to do.

Thanks!

Pierre

Re: Performance of relationships

[Pierre Padovani]

I was in a hurry writing the previous email and realized that I did not
specify that the relationship type was COMPOSITION.

On Fri, Jun 1, 2018 at 2:37 PM, Pierre Padovani <
pierre.padov...@civitaslearning.com> wrote:

> All,
>
> I decided to spend a few cycles performing from basic performance tests to
> help us refine our type system. The goal was to determine how we would add
> relationships to our entities and if we would use the new relationship APIs
> or not. The test was simple. I created a type called container and a type
> called child both extending DataSet. I think created an instance of
> container, and added one child at a time to the container recording the
> cost of the add, and the cost of fetching the container after each add.
>
> There were three tests run:
>
> - Legacy - Assign the entities to the attributes in the attribute map
> - Hybrid - Leave the legacy attributes in the type system, and use the
> relationship APIs
> - V2 - Remove the legacy attributes and use the relationship APIs
>
> Here are the results for 100 children:
>
>
>
> Is there a reason we are continuing to use legacy attributes in the type
> system(s) we are shipping with Atlas? From a performance perspective this
> does not seem like a reasonable thing to do.
>
> Thanks!
>
> Pierre
>
>

Re: Performance of relationships

[Apoorv Naik]

Can you share the text of the benchmarks you performed ? My email is not 
rendering the attached image.

From: Pierre Padovani 
Reply-To: "dev@atlas.apache.org" 
Date: Friday, June 1, 2018 at 12:49 PM
To: "dev@atlas.apache.org" 
Subject: Re: Performance of relationships

I was in a hurry writing the previous email and realized that I did not specify 
that the relationship type was COMPOSITION.

On Fri, Jun 1, 2018 at 2:37 PM, Pierre Padovani 
mailto:pierre.padov...@civitaslearning.com>>
 wrote:
All,

I decided to spend a few cycles performing from basic performance tests to help 
us refine our type system. The goal was to determine how we would add 
relationships to our entities and if we would use the new relationship APIs or 
not. The test was simple. I created a type called container and a type called 
child both extending DataSet. I think created an instance of container, and 
added one child at a time to the container recording the cost of the add, and 
the cost of fetching the container after each add.

There were three tests run:

- Legacy - Assign the entities to the attributes in the attribute map
- Hybrid - Leave the legacy attributes in the type system, and use the 
relationship APIs
- V2 - Remove the legacy attributes and use the relationship APIs

Here are the results for 100 children:

[cid:ii_jhwdc79w0_163bcd934880f531]

Is there a reason we are continuing to use legacy attributes in the type 
system(s) we are shipping with Atlas? From a performance perspective this does 
not seem like a reasonable thing to do.

Thanks!

Pierre

[jira] [Created] (ATLAS-2732) Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line

[Ramesh Mani (JIRA)]

Ramesh Mani created ATLAS-2732:
--

 Summary: Handle kerberos security arguments in import-hbase.sh / 
import-hive.sh passed via command line
 Key: ATLAS-2732
 URL: https://issues.apache.org/jira/browse/ATLAS-2732
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: trunk
Reporter: Ramesh Mani
Assignee: Ramesh Mani
 Fix For: trunk


Handle kerberos security arguments in import-hbase.sh / import-hive.sh . 
Current when passed externally via command line import scripts fails with 
exceptions.

e.g

./import-hive.sh -d TEST_ATLAS_PATCH -t test 
-Djava.security.krb5.conf=/etc/krb5.conf 
-Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf

./import-hbase.sh -Djava.security.krb5.conf=/etc/krb5.conf 
-Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf -f 
/tmp/hbase.txt



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

[jira] [Updated] (ATLAS-2732) Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2732:
---
Attachment: 0001-ATLAS-2732-Handle-kerberos-security-arguments-in-imp.patch

> Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed 
> via command line
> --
>
> Key: ATLAS-2732
> URL: https://issues.apache.org/jira/browse/ATLAS-2732
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> 0001-ATLAS-2732-Handle-kerberos-security-arguments-in-imp.patch
>
>
> Handle kerberos security arguments in import-hbase.sh / import-hive.sh . 
> Current when passed externally via command line import scripts fails with 
> exceptions.
> e.g
> ./import-hive.sh -d TEST_ATLAS_PATCH -t test 
> -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf
> ./import-hbase.sh -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf -f 
> /tmp/hbase.txt



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

Review Request 67422: ATLAS-2732:Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line

[Ramesh Mani]

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

Review request for atlas, Madhan Neethiraj and Nixon Rodrigues.


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


Repository: atlas


Description
---

ATLAS-2732:Handle kerberos security arguments in import-hbase.sh / 
import-hive.sh passed via command line


Diffs
-

  addons/hbase-bridge/src/bin/import-hbase.sh 0a5989f 
  addons/hive-bridge/src/bin/import-hive.sh 98f4c84 


Diff: https://reviews.apache.org/r/67422/diff/1/


Testing
---

Tested in Local VM


Thanks,

Ramesh Mani

Re: Review Request 67422: ATLAS-2732:Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line

[Madhan Neethiraj]

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




addons/hbase-bridge/src/bin/import-hbase.sh
Line 130 (original), 129 (patched)


Instead of specifically looking for "-D", consider the following to collect 
arguments for the import tool in IMPORT_ARGS and the rest in JVM_ARGS:

#!/bin/bash

IMPORT_ARGS=
JVM_ARGS=

while true
do
  option=$1
  shift

  case "$option" in
-d) IMPORT_ARGS="$IMPORT_ARGS -d $1"; shift;;
-t) IMPORT_ARGS="$IMPORT_ARGS -t $1"; shift;;
--database) IMPORT_ARGS="$IMPORT_ARGS --database $1"; shift;;
--table) IMPORT_ARGS="$IMPORT_ARGS --table $1"; shift;;
"") break;;
*) JVM_ARGS="$JVM_ARGS $option"
  esac
done

echo JVM_ARGS=$JVM_ARGS
echo IMPORT_ARGS=$IMPORT_ARGS


- Madhan Neethiraj


On June 2, 2018, 1:31 a.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67422/
> ---
> 
> (Updated June 2, 2018, 1:31 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-2732
> https://issues.apache.org/jira/browse/ATLAS-2732
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2732:Handle kerberos security arguments in import-hbase.sh / 
> import-hive.sh passed via command line
> 
> 
> Diffs
> -
> 
>   addons/hbase-bridge/src/bin/import-hbase.sh 0a5989f 
>   addons/hive-bridge/src/bin/import-hive.sh 98f4c84 
> 
> 
> Diff: https://reviews.apache.org/r/67422/diff/1/
> 
> 
> Testing
> ---
> 
> Tested in Local VM
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

Re: Review Request 67410: ATLAS-2730 : TimeBoundry date time validation during addclassification and updateClassifcation of entity.

[Madhan Neethiraj]

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




repository/src/main/java/org/apache/atlas/util/DateTimeUtil.java
Lines 36 (patched)


- ValidateTimeBoundry() ==> validateTimeBoundry()
- replace startDate/endDate/timeZonStr with "TimeBoundary timeBoundary"



repository/src/main/java/org/apache/atlas/util/DateTimeUtil.java
Lines 39 (patched)


startDate and endDate can be null. It is not an error condition. Only 
validation required is that, when both values are specified, startDate should 
not be later than endDate.



repository/src/main/java/org/apache/atlas/util/DateTimeUtil.java
Lines 44 (patched)


timeZone can be null or empty - which is treated as local-timezone.


- Madhan Neethiraj


On June 1, 2018, 12:29 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67410/
> ---
> 
> (Updated June 1, 2018, 12:29 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, 
> Ruchi Solani, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2730
> https://issues.apache.org/jira/browse/ATLAS-2730
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch includes validation of classifcation TimeBoundry date time 
> timezone during addclassification and updateClassifcation of entity.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 06b43458b 
>   repository/pom.xml a6ee43f61 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
>  5e33cf59f 
>   repository/src/main/java/org/apache/atlas/util/DateTimeUtil.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/67410/diff/1/
> 
> 
> Testing
> ---
> 
> Tested adding / updating classifcation with / invalid / without 
> TimeBoundry/datetime timezeone from UI and from API.
> Existing UT and IT passing.
> https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/462/console
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>