Re: Review Request 48550: ATLAS-869 - Make LDAP/AD properties to be configurable.

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On June 10, 2016, 1:10 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48550/
> ---
> 
> (Updated June 10, 2016, 1:10 p.m.)
> 
> 
> Review request for atlas, Gautam Borad, Madhan Neethiraj, Mehul Parikh, 
> Shwetha GS, Suma Shivaprasad, and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-869
> https://issues.apache.org/jira/browse/ATLAS-869
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently the LDAP/AD configartion properties are  in atlas-admin-site.xml, 
> which is bundled with webapp.
> End user should be able to configure it, it has been moved to 
> atlas-application.properties now.
> 
> 
> Diffs
> -
> 
>   distro/src/conf/atlas-application.properties bdd02d6 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasADAuthenticationProvider.java
>  34063b0 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java
>  6037858 
>   webapp/src/main/resources/atlas-admin-site.xml c4b4be7 
>   webapp/src/main/webapp/WEB-INF/applicationContext.xml 004c3a8 
> 
> Diff: https://reviews.apache.org/r/48550/diff/
> 
> 
> Testing
> ---
> 
> Tested login via FILE/LDAP/AD authentication methods.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

Re: Review Request 48550: ATLAS-869 - Make LDAP/AD properties to be configurable.

[Hemanth Yamijala]

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




distro/src/conf/atlas-application.properties (line 98)


I don't think we should hardcode these. Can you please remove?


- Hemanth Yamijala


On June 10, 2016, 1:10 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48550/
> ---
> 
> (Updated June 10, 2016, 1:10 p.m.)
> 
> 
> Review request for atlas, Gautam Borad, Madhan Neethiraj, Mehul Parikh, 
> Shwetha GS, Suma Shivaprasad, and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-869
> https://issues.apache.org/jira/browse/ATLAS-869
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently the LDAP/AD configartion properties are  in atlas-admin-site.xml, 
> which is bundled with webapp.
> End user should be able to configure it, it has been moved to 
> atlas-application.properties now.
> 
> 
> Diffs
> -
> 
>   distro/src/conf/atlas-application.properties bdd02d6 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasADAuthenticationProvider.java
>  34063b0 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java
>  6037858 
>   webapp/src/main/resources/atlas-admin-site.xml c4b4be7 
>   webapp/src/main/webapp/WEB-INF/applicationContext.xml 004c3a8 
> 
> Diff: https://reviews.apache.org/r/48550/diff/
> 
> 
> Testing
> ---
> 
> Tested login via FILE/LDAP/AD authentication methods.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

[jira] [Assigned] (ATLAS-893) UI: Gets stuck when navigating to and from the Taxonomies tab

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-893:
-

Assignee: Keval Bhatt

> UI: Gets stuck when navigating to and from the Taxonomies tab
> -
>
> Key: ATLAS-893
> URL: https://issues.apache.org/jira/browse/ATLAS-893
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Keval Bhatt
>
> A regular way of using the business taxonomy and terms is to do the following:
> * Create a taxonomy
> * Create some terms (hierarchical if needed)
> * Import a few entities - quick_start, hive etc.
> * Associate assets with terms
> * Search for assets selecting the terms
> 
> These activities require navigating between the Taxonomy and Search tabs on 
> the left pane. Sometimes, I notice that moving to the Taxonomy tab results in 
> a spinner on the selected term and it doesn't vanish until a refresh. The UI 
> is inaccessible at this time. 
> There is no activity on the server at this time - so it doesn't seem a 
> backend issue. Also, a browser refresh *always* fixes the issue.
> Its just hard to tell exactly when this happens, so I can't give more 
> specific steps to reproduce the problem, unfortunately.



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

Re: Review Request 48550: ATLAS-869 - Make LDAP/AD properties to be configurable.

[Nixon Rodrigues]

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

(Updated June 13, 2016, 11:03 a.m.)


Review request for atlas, Gautam Borad, Madhan Neethiraj, Mehul Parikh, Shwetha 
GS, Suma Shivaprasad, and Hemanth Yamijala.


Changes
---

Changes include removal of LDAP/AD properties.


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


Repository: atlas


Description
---

Currently the LDAP/AD configartion properties are  in atlas-admin-site.xml, 
which is bundled with webapp.
End user should be able to configure it, it has been moved to 
atlas-application.properties now.


Diffs (updated)
-

  distro/src/conf/atlas-application.properties 2b90086 
  
webapp/src/main/java/org/apache/atlas/web/security/AtlasADAuthenticationProvider.java
 34063b0 
  
webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java
 6037858 
  webapp/src/main/resources/atlas-admin-site.xml c4b4be7 
  webapp/src/main/webapp/WEB-INF/applicationContext.xml 004c3a8 

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


Testing
---

Tested login via FILE/LDAP/AD authentication methods.


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-869) Make LDAP/AD properties to be configurable.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-869:
--
Attachment: ATLAS-869.1.patch

> Make LDAP/AD properties to be configurable.
> ---
>
> Key: ATLAS-869
> URL: https://issues.apache.org/jira/browse/ATLAS-869
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-869.1.patch, ATLAS-869.patch
>
>
> Currently the LDAP/AD related properties  are in atlas-admin-site.xml which 
> is bundled with webapp.
> End user should be able to configure it.



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

[jira] [Updated] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[Vimal Sharma (JIRA)]

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

Vimal Sharma updated ATLAS-688:
---
Attachment: ATLAS-688.patch

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Attachments: ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



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

[jira] [Commented] (ATLAS-837) Enhance Sqoop addon to handle export operation

[Shwetha G S (JIRA)]

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

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

Verified end to end flow. Export will work only with SQOOP-2936, however the 
patch compiles without SQOOP-2936. So, committing this

> Enhance Sqoop addon to handle export operation
> --
>
> Key: ATLAS-837
> URL: https://issues.apache.org/jira/browse/ATLAS-837
> Project: Atlas
>  Issue Type: Bug
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: ATLAS-837.patch
>
>
> Sqoop is adding change to publish hcatalog export data in SQOOP-2936.   
> Enhancing the Sqoop Hook to support it.   No change in Sqoop proces model but 
> based on operation the inputs/outputs will be swapped



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

[jira] [Created] (ATLAS-896) SqoopHookIT as integration test

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-896:
-

 Summary: SqoopHookIT as integration test
 Key: ATLAS-896
 URL: https://issues.apache.org/jira/browse/ATLAS-896
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S


SqoopHookIT can use derby as external db and should use sqoop commands to test 
the end to end flow. It currently just prepares the data and call sqoop hook. 
Instead, it should use sqoop command execution to prepare the data



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

Re: Review Request 48550: ATLAS-869 - Make LDAP/AD properties to be configurable.

[Nixon Rodrigues]

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

(Updated June 13, 2016, 12:36 p.m.)


Review request for atlas, Gautam Borad, Madhan Neethiraj, Mehul Parikh, Shwetha 
GS, Suma Shivaprasad, and Hemanth Yamijala.


Changes
---

Changes includes setting example values to LDAP/AD properties


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


Repository: atlas


Description
---

Currently the LDAP/AD configartion properties are  in atlas-admin-site.xml, 
which is bundled with webapp.
End user should be able to configure it, it has been moved to 
atlas-application.properties now.


Diffs (updated)
-

  distro/src/conf/atlas-application.properties 2b90086 
  
webapp/src/main/java/org/apache/atlas/web/security/AtlasADAuthenticationProvider.java
 34063b0 
  
webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java
 6037858 
  webapp/src/main/resources/atlas-admin-site.xml c4b4be7 
  webapp/src/main/webapp/WEB-INF/applicationContext.xml 004c3a8 

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


Testing
---

Tested login via FILE/LDAP/AD authentication methods.


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-869) Make LDAP/AD properties to be configurable.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-869:
--
Attachment: ATLAS-869.2.patch

> Make LDAP/AD properties to be configurable.
> ---
>
> Key: ATLAS-869
> URL: https://issues.apache.org/jira/browse/ATLAS-869
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-869.1.patch, ATLAS-869.2.patch, ATLAS-869.patch
>
>
> Currently the LDAP/AD related properties  are in atlas-admin-site.xml which 
> is bundled with webapp.
> End user should be able to configure it.



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

Re: Review Request 48550: ATLAS-869 - Make LDAP/AD properties to be configurable.

[Hemanth Yamijala]

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


Ship it!




Ship It!

- Hemanth Yamijala


On June 13, 2016, 12:36 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48550/
> ---
> 
> (Updated June 13, 2016, 12:36 p.m.)
> 
> 
> Review request for atlas, Gautam Borad, Madhan Neethiraj, Mehul Parikh, 
> Shwetha GS, Suma Shivaprasad, and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-869
> https://issues.apache.org/jira/browse/ATLAS-869
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently the LDAP/AD configartion properties are  in atlas-admin-site.xml, 
> which is bundled with webapp.
> End user should be able to configure it, it has been moved to 
> atlas-application.properties now.
> 
> 
> Diffs
> -
> 
>   distro/src/conf/atlas-application.properties 2b90086 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasADAuthenticationProvider.java
>  34063b0 
>   
> webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java
>  6037858 
>   webapp/src/main/resources/atlas-admin-site.xml c4b4be7 
>   webapp/src/main/webapp/WEB-INF/applicationContext.xml 004c3a8 
> 
> Diff: https://reviews.apache.org/r/48550/diff/
> 
> 
> Testing
> ---
> 
> Tested login via FILE/LDAP/AD authentication methods.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

[jira] [Commented] (ATLAS-869) Make LDAP/AD properties to be configurable.

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-869:


+1 for changes on the last patch. Will run tests and commit.

> Make LDAP/AD properties to be configurable.
> ---
>
> Key: ATLAS-869
> URL: https://issues.apache.org/jira/browse/ATLAS-869
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-869.1.patch, ATLAS-869.2.patch, ATLAS-869.patch
>
>
> Currently the LDAP/AD related properties  are in atlas-admin-site.xml which 
> is bundled with webapp.
> End user should be able to configure it.



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

[jira] [Created] (ATLAS-897) Atlas UI: Feature to associate multiple assets with a term.

[Kalyani Kashikar (JIRA)]

Kalyani Kashikar created ATLAS-897:
--

 Summary: Atlas UI: Feature to associate multiple assets with a 
term. 
 Key: ATLAS-897
 URL: https://issues.apache.org/jira/browse/ATLAS-897
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Kalyani Kashikar
Assignee: Kalyani Kashikar
 Fix For: 0.7-incubating


Right now user needs to go to each entity to associate a term. We need a 
feature to  associate same term to multiple assets.



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

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

[Apache Jenkins Server]

See 

Changes:

[hyamijala] ATLAS-869 Make LDAP/AD properties to be configurable. 
(nixonrodrigues

--
[...truncated 5926 lines...]
[INFO] Using incremental compilation
[INFO] Compiling 56 Java sources to 

[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:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 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-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 41 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [2947 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-webapp ---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.
[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.web.service.ActiveInstanceElectorServiceTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec - in 
org.apache.atlas.web.service.ActiveInstanceElectorServiceTest
Running org.apache.atlas.web.service.CuratorFactoryTest
Tests run: 3, Failures: 0, Errors: 0,

Re: Review Request 48533: Business Catalog Update

[John Speidel]

> On June 11, 2016, 6:38 a.m., Hemanth Yamijala wrote:
> > webapp/src/main/java/org/apache/atlas/web/resources/TaxonomyService.java, 
> > line 104
> > 
> >
> > I don't know if this was intended, but here we are not using the 
> > InstanceRequest constructor that sends updateProperties separately. As a 
> > result, if a 'name' attribute of taxonomy is attempted to be modified, this 
> > silently passes through validation and returns back with a 200 without 
> > changing anything. Should we handle this?

Yeah, this is a mistake. I had started to converge taxonomy and term updates 
but ran out of time and didn't notice that the validation check wouldn't work. 
I will fix taxonomy update to use the same mechanism as term updates.


- John


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


On June 10, 2016, 9:09 p.m., John Speidel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48533/
> ---
> 
> (Updated June 10, 2016, 9:09 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-794
> https://issues.apache.org/jira/browse/ATLAS-794
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Allows for updating of taxonomy and term property values, excluding the name 
> property.
> 
> 
> Diffs
> -
> 
>   catalog/src/main/java/org/apache/atlas/catalog/AtlasTypeSystem.java 3a58488 
>   catalog/src/main/java/org/apache/atlas/catalog/BaseRequest.java 9ccb4e3 
>   catalog/src/main/java/org/apache/atlas/catalog/BaseResourceProvider.java 
> ad2f7f4 
>   catalog/src/main/java/org/apache/atlas/catalog/CollectionRequest.java 
> b1be1ae 
>   catalog/src/main/java/org/apache/atlas/catalog/DefaultTypeSystem.java 
> a28a32b 
>   catalog/src/main/java/org/apache/atlas/catalog/EntityResourceProvider.java 
> c8d6f68 
>   
> catalog/src/main/java/org/apache/atlas/catalog/EntityTagResourceProvider.java 
> f73f80b 
>   catalog/src/main/java/org/apache/atlas/catalog/InstanceRequest.java 01583c4 
>   catalog/src/main/java/org/apache/atlas/catalog/Request.java 7dc781a 
>   catalog/src/main/java/org/apache/atlas/catalog/ResourceProvider.java 
> 9c809c0 
>   
> catalog/src/main/java/org/apache/atlas/catalog/TaxonomyResourceProvider.java 
> 0d63336 
>   catalog/src/main/java/org/apache/atlas/catalog/TermResourceProvider.java 
> 0c72de6 
>   catalog/src/main/java/org/apache/atlas/catalog/VertexWrapper.java 6e5d28e 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/BaseResourceDefinition.java
>  32d6f30 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/EntityResourceDefinition.java
>  cf55f1f 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/ResourceDefinition.java
>  f310c5a 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/TaxonomyResourceDefinition.java
>  a3fbdf1 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/TermResourceDefinition.java
>  19dd049 
>   catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityQuery.java 
> c24b99a 
>   
> catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityTagQuery.java 
> df216c0 
>   catalog/src/main/java/org/apache/atlas/catalog/query/AtlasQuery.java 
> af14697 
>   catalog/src/main/java/org/apache/atlas/catalog/query/AtlasTermQuery.java 
> b761dcc 
>   catalog/src/main/java/org/apache/atlas/catalog/query/BaseQuery.java ba8e0e7 
>   catalog/src/main/java/org/apache/atlas/catalog/query/QueryFactory.java 
> 39ce11a 
>   catalog/src/test/java/org/apache/atlas/catalog/CollectionRequestTest.java 
> 0a2bace 
>   
> catalog/src/test/java/org/apache/atlas/catalog/EntityResourceProviderTest.java
>  2f29103 
>   
> catalog/src/test/java/org/apache/atlas/catalog/EntityTagResourceProviderTest.java
>  78204a6 
>   catalog/src/test/java/org/apache/atlas/catalog/InstanceRequestTest.java 
> 5ccec02 
>   
> catalog/src/test/java/org/apache/atlas/catalog/TaxonomyResourceProviderTest.java
>  a714a8c 
>   
> catalog/src/test/java/org/apache/atlas/catalog/TermResourceProviderTest.java 
> 235bde4 
>   catalog/src/test/java/org/apache/atlas/catalog/VertexWrapperTest.java 
> 64935a6 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/EntityResourceDefinitionTest.java
>  303e2ba 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/EntityTagResourceDefinitionTest.java
>  954262f 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/TaxonomyResourceDefinitionTest.java
>  bc6f74c 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/TermResourceDefinitionTest.java
>  52deadf 
>   
> catalog/src/test/java/org/apache/a

[jira] [Commented] (ATLAS-806) Business Taxonomy related types should be registered one time on server startup.

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-806:


To give some more details:

ATLAS-512 introduced the class {{ReservedTypesRegistrar}}. This looks at the 
JSON definitions of types to be pre-registered at server startup. The JSON 
definitions of types are created at build time using the {{exec-maven-plugin}} 
in the hooks - for example in hive hook's pom.xml we make a call to the 
{{HiveDataModelGenerator}} to generate the JSON. The generated JSONs are copied 
during build time into a {{models}} directory that is package in Atlas. The 
types registrar checks to see if the types are registered and if so, does not 
do any modifications. Hence, running them multiple times does not cause any 
adverse behavior.

Possibly this method can be extended for this JIRA, not just for the business 
taxonomy type registration, but also the registration of the default taxonomy 
instance.

> Business Taxonomy related types should be registered one time on server 
> startup.
> 
>
> Key: ATLAS-806
> URL: https://issues.apache.org/jira/browse/ATLAS-806
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
>
> The Taxonomy type is currently being registered on the first call to the API. 
> We have seen this could have issues if calls are made in parallel - as could 
> happen in a web situation. Atlas already has the necessary framework to 
> register types at startup time which was introduced as part of ATLAS-512. 
> This should be used here.



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

[jira] [Commented] (ATLAS-806) Business Taxonomy related types should be registered one time on server startup.

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-806:


An alternative approach could be to see if a Business Taxonomy initializer can 
be registered with Guice and be eagerly initialized. The only catch would be in 
a HA scenario where two instances might try to register the same object at the 
same time. In order to handle this, this can be registered as an 
{{ActiveStateChangeHandler}}. Any implementation of this interface can be used 
as a model for how to use it. An example implementation is the 
{{HBaseBasedAuditRepository}} class.

> Business Taxonomy related types should be registered one time on server 
> startup.
> 
>
> Key: ATLAS-806
> URL: https://issues.apache.org/jira/browse/ATLAS-806
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
>
> The Taxonomy type is currently being registered on the first call to the API. 
> We have seen this could have issues if calls are made in parallel - as could 
> happen in a web situation. Atlas already has the necessary framework to 
> register types at startup time which was introduced as part of ATLAS-512. 
> This should be used here.



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

[jira] [Created] (ATLAS-898) Add IN clause to DSL grammar

[David Kantor (JIRA)]

David Kantor created ATLAS-898:
--

 Summary: Add IN clause to DSL grammar
 Key: ATLAS-898
 URL: https://issues.apache.org/jira/browse/ATLAS-898
 Project: Atlas
  Issue Type: Improvement
Reporter: David Kantor


Add DSL support for the IN clause, to allow queries to search on a list of 
values e.g. 
{{Department where __guid in (guid1, guid2, guid3)}}



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

[jira] [Commented] (ATLAS-831) Search issues with business terms

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-831:


Another issue is that searching for tags also returns terms as terms are 
modeled as tags.

> Search issues with business terms
> -
>
> Key: ATLAS-831
> URL: https://issues.apache.org/jira/browse/ATLAS-831
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Critical
>
> With ATLAS-821 in, there are a couple of issues that we need to think from 
> the business terms search perspective. This might involve changes between 
> core, taxonomy API and UI. Hence, not filing against any one area.
> * Searching for assets associated with a business term returns the taxonomy 
> object it is assigned to. This is an artifact of our associating the 'master 
> copy' of the business term against the taxonomy object - to root it for 
> lookups.
> * More importantly, searching for assets associated to a parent path in the 
> business term does not return assets associated to the children. For e.g. if 
> a term 'a.b.c' is associated with an asset A, then searching for 'a.b' does 
> not return A.



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

[jira] [Updated] (ATLAS-515) Ability to initialize Kafka topics with more than 1 replica

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-515:
---
Attachment: ATLAS-515-3.patch

This patch adds security support to the initialization code. Essentially if the 
deployment is in a Kerberized environment, it will launch with the Kafka 
service principal and keytab to execute the Kafka topic initialization code.

> Ability to initialize Kafka topics with more than 1 replica
> ---
>
> Key: ATLAS-515
> URL: https://issues.apache.org/jira/browse/ATLAS-515
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-515-1.patch, ATLAS-515-2.patch, ATLAS-515-3.patch, 
> ATLAS-515-poc.patch, ATLAS-515.patch
>
>
> Atlas uses two Kafka topics - ATLAS_HOOK and ATLAS_ENTITIES for communicating 
> with its upstream and downstream dependencies. If not explicitly created, 
> these topics are setup with a single replica. From a HA perspective, this 
> becomes a problem. This JIRA is to request for a mechanism for creating 
> topics with more than 1 replica. 



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

Re: Review Request 48280: ATLAS-515: Ability to initialize Kafka topics with more than 1 replica

[Hemanth Yamijala]

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

(Updated June 13, 2016, 4:35 p.m.)


Review request for atlas.


Changes
---

Updated the patch to handle Kerberized Kafka clusters.


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


Repository: atlas


Description
---

Attached patch provides a method to automatically create Kafka topics 
ATLAS_HOOK and ATLAS_ENTITIES with configured number of replicas.


Diffs (updated)
-

  common/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java 3dbab17 
  distro/src/bin/atlas_client_cmdline.py f109ad3 
  distro/src/bin/atlas_config.py fab4046 
  distro/src/bin/atlas_kafka_setup.py PRE-CREATION 
  distro/src/bin/atlas_kafka_setup_hook.py PRE-CREATION 
  distro/src/conf/atlas-application.properties 2b90086 
  distro/src/main/assemblies/standalone-package.xml 1c7b2c5 
  docs/src/site/twiki/Configuration.twiki 7150483 
  docs/src/site/twiki/InstallationSteps.twiki 518c380 
  notification/pom.xml b3738db 
  notification/src/main/java/org/apache/atlas/hook/AtlasTopicCreator.java 
PRE-CREATION 
  notification/src/test/java/org/apache/atlas/hook/AtlasTopicCreatorTest.java 
PRE-CREATION 
  pom.xml e13345e 

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


Testing
---

* Started multiple Kafka brokers on single machine, configured number of 
replicas to be 2, started Atlas server and verified they got created correctly.
* Started multiple Kafka brokers on single machine, configured number of 
replicas to be 2, started Hive hook and verified it created ATLAS_HOOK 
correctly. Then started Atlas server and verified it by-passed ATLAS_HOOK 
creation, but did ATLAS_ENTITIES creation.
* Started one Kafka broker, onfigured number of replicas to be 2, started Atlas 
server and verified it received an exception as expected. But topic could still 
get auto-created and continued.
* Started 2 instances of Atlas server concurrently and verified topic creation 
is working fine.
* Existing UTs/ITs/new UTs pass.


Thanks,

Hemanth Yamijala

[jira] [Commented] (ATLAS-831) Search issues with business terms

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-831:


[~yhemanth], [~shwethags], [~suma.shivaprasad] - what do you suggest to address 
these issues? Should search support additional filter to specify whether to 
restrict the results to tags or terms?

> Search issues with business terms
> -
>
> Key: ATLAS-831
> URL: https://issues.apache.org/jira/browse/ATLAS-831
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Critical
>
> With ATLAS-821 in, there are a couple of issues that we need to think from 
> the business terms search perspective. This might involve changes between 
> core, taxonomy API and UI. Hence, not filing against any one area.
> * Searching for assets associated with a business term returns the taxonomy 
> object it is assigned to. This is an artifact of our associating the 'master 
> copy' of the business term against the taxonomy object - to root it for 
> lookups.
> * More importantly, searching for assets associated to a parent path in the 
> business term does not return assets associated to the children. For e.g. if 
> a term 'a.b.c' is associated with an asset A, then searching for 'a.b' does 
> not return A.



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

[jira] [Updated] (ATLAS-831) Search issues with business terms

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-831:
---
Assignee: Shwetha G S

> Search issues with business terms
> -
>
> Key: ATLAS-831
> URL: https://issues.apache.org/jira/browse/ATLAS-831
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
>Priority: Critical
>
> With ATLAS-821 in, there are a couple of issues that we need to think from 
> the business terms search perspective. This might involve changes between 
> core, taxonomy API and UI. Hence, not filing against any one area.
> * Searching for assets associated with a business term returns the taxonomy 
> object it is assigned to. This is an artifact of our associating the 'master 
> copy' of the business term against the taxonomy object - to root it for 
> lookups.
> * More importantly, searching for assets associated to a parent path in the 
> business term does not return assets associated to the children. For e.g. if 
> a term 'a.b.c' is associated with an asset A, then searching for 'a.b' does 
> not return A.



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

[jira] [Updated] (ATLAS-831) Search issues with business terms

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-831:
--
Assignee: (was: Shwetha G S)

> Search issues with business terms
> -
>
> Key: ATLAS-831
> URL: https://issues.apache.org/jira/browse/ATLAS-831
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Critical
>
> With ATLAS-821 in, there are a couple of issues that we need to think from 
> the business terms search perspective. This might involve changes between 
> core, taxonomy API and UI. Hence, not filing against any one area.
> * Searching for assets associated with a business term returns the taxonomy 
> object it is assigned to. This is an artifact of our associating the 'master 
> copy' of the business term against the taxonomy object - to root it for 
> lookups.
> * More importantly, searching for assets associated to a parent path in the 
> business term does not return assets associated to the children. For e.g. if 
> a term 'a.b.c' is associated with an asset A, then searching for 'a.b' does 
> not return A.



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

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

[Apache Jenkins Server]

See 

Changes:

[sshivalingamurthy] ATLAS-837 Enhance Sqoop addon to handle export operation 
(venkatnrangan

--
[...truncated 5926 lines...]
[INFO] Using incremental compilation
[INFO] Compiling 56 Java sources to 

[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:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 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-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 41 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [981 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-webapp ---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.
[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.web.service.ActiveInstanceElectorServiceTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.266 sec - in 
org.apache.atlas.web.service.ActiveInstanceElectorServiceTest
Running org.apache.atlas.web.service.CuratorFactoryTest
Tests run: 3, Failures: 0, E

[jira] [Commented] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-688:


@Vimal Sharma pom.xml also needs to change to remove bridge/hive packaging. 
Also ATLAS_HOME will not be available if the ATLAS server and hive server are 
in different hosts . Can you pls revert that change and expect ATLAS_CONF to be 
set explicitly.

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Attachments: ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



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

[jira] [Comment Edited] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-688 at 6/13/16 6:54 PM:
-

[~svimal2106] pom.xml also needs to change to remove bridge/hive packaging. 
Also ATLAS_HOME will not be available if the ATLAS server and hive server are 
in different hosts . Can you pls revert that change and expect ATLAS_CONF to be 
set explicitly.


was (Author: suma.shivaprasad):
@Vimal Sharma pom.xml also needs to change to remove bridge/hive packaging. 
Also ATLAS_HOME will not be available if the ATLAS server and hive server are 
in different hosts . Can you pls revert that change and expect ATLAS_CONF to be 
set explicitly.

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Attachments: ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



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

Re: Review Request 48280: ATLAS-515: Ability to initialize Kafka topics with more than 1 replica

[Suma Shivaprasad]

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


Ship it!




Ship It!

- Suma Shivaprasad


On June 13, 2016, 4:35 p.m., Hemanth Yamijala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48280/
> ---
> 
> (Updated June 13, 2016, 4:35 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-515
> https://issues.apache.org/jira/browse/ATLAS-515
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Attached patch provides a method to automatically create Kafka topics 
> ATLAS_HOOK and ATLAS_ENTITIES with configured number of replicas.
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java 3dbab17 
>   distro/src/bin/atlas_client_cmdline.py f109ad3 
>   distro/src/bin/atlas_config.py fab4046 
>   distro/src/bin/atlas_kafka_setup.py PRE-CREATION 
>   distro/src/bin/atlas_kafka_setup_hook.py PRE-CREATION 
>   distro/src/conf/atlas-application.properties 2b90086 
>   distro/src/main/assemblies/standalone-package.xml 1c7b2c5 
>   docs/src/site/twiki/Configuration.twiki 7150483 
>   docs/src/site/twiki/InstallationSteps.twiki 518c380 
>   notification/pom.xml b3738db 
>   notification/src/main/java/org/apache/atlas/hook/AtlasTopicCreator.java 
> PRE-CREATION 
>   notification/src/test/java/org/apache/atlas/hook/AtlasTopicCreatorTest.java 
> PRE-CREATION 
>   pom.xml e13345e 
> 
> Diff: https://reviews.apache.org/r/48280/diff/
> 
> 
> Testing
> ---
> 
> * Started multiple Kafka brokers on single machine, configured number of 
> replicas to be 2, started Atlas server and verified they got created 
> correctly.
> * Started multiple Kafka brokers on single machine, configured number of 
> replicas to be 2, started Hive hook and verified it created ATLAS_HOOK 
> correctly. Then started Atlas server and verified it by-passed ATLAS_HOOK 
> creation, but did ATLAS_ENTITIES creation.
> * Started one Kafka broker, onfigured number of replicas to be 2, started 
> Atlas server and verified it received an exception as expected. But topic 
> could still get auto-created and continued.
> * Started 2 instances of Atlas server concurrently and verified topic 
> creation is working fine.
> * Existing UTs/ITs/new UTs pass.
> 
> 
> Thanks,
> 
> Hemanth Yamijala
> 
>

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-542:
---
Attachment: ATLAS-542.2.patch

Thanks [~yhemanth] . Fixed review comments

> Make qualifiedName and name consistent across all Datasets and Process
> --
>
> Key: ATLAS-542
> URL: https://issues.apache.org/jira/browse/ATLAS-542
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-542.1.patch, ATLAS-542.2.patch, ATLAS-542.patch
>
>
> Currently hive_db, hive_column has qualifiedName holding the fully qualified 
> Name and name having the shorter name. 
> However hive_table has the fully qualified Name in "name" and shorter Name in 
> tableName. We should make this consistent for better search experience by 
> removing tableName and keep it consistent with db, column
> Same with hive_process, storm_topology, falcon_process - needs to have a 
> qualifiedName 



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

[jira] [Updated] (ATLAS-888) NPE in NotificationHookConsumer

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-888:
---
Attachment: ATLAS-888.patch

> NPE in NotificationHookConsumer
> ---
>
> Key: ATLAS-888
> URL: https://issues.apache.org/jira/browse/ATLAS-888
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-888.patch
>
>
> 2016-06-08 15:54:22,375 ERROR - [NotificationHookConsumer thread-0:] ~ Unable 
> to persist entity instance (EntityResource:137)
> java.lang.NullPointerException
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:652)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:203)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:187)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2016-06-08 15:54:22,376 WARN  - [NotificationHookConsumer thread-0:] ~ Error 
> handling message 
> org.apache.atlas.notification.hook.HookNotification$EntityCreateRequest@6b8492f1
>  (NotificationHookConsumer:233)
> org.apache.atlas.AtlasServiceException: Metadata service API CREATE_ENTITY 
> failed with status 500(Internal Server Error) Response Body 
> (java.lang.NullPointerException
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:652)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:203)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:187)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> )
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:122)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:652)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:203)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:187)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)



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

[jira] [Updated] (ATLAS-794) Business Catalog Update

[John Speidel (JIRA)]

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

John Speidel updated ATLAS-794:
---
Attachment: ATLAS-794-3.patch

Changes to address 400 response when attempting to update taxonomy name.

> Business Catalog Update
> ---
>
> Key: ATLAS-794
> URL: https://issues.apache.org/jira/browse/ATLAS-794
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-794-2.patch, ATLAS-794-3.patch, ATLAS-794.patch
>
>
> Business Catalog should support Update of all fields of a Term



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

[jira] [Comment Edited] (ATLAS-794) Business Catalog Update

[John Speidel (JIRA)]

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

John Speidel edited comment on ATLAS-794 at 6/13/16 7:29 PM:
-

New patch (ATLAS-794-3.patch) with changes to address 400 response when 
attempting to update taxonomy name.


was (Author: jspeidel):
Changes to address 400 response when attempting to update taxonomy name.

> Business Catalog Update
> ---
>
> Key: ATLAS-794
> URL: https://issues.apache.org/jira/browse/ATLAS-794
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-794-2.patch, ATLAS-794-3.patch, ATLAS-794.patch
>
>
> Business Catalog should support Update of all fields of a Term



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

Re: Review Request 48533: Business Catalog Update

[John Speidel]

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

(Updated June 13, 2016, 7:29 p.m.)


Review request for atlas and Hemanth Yamijala.


Changes
---

New patch addresses 400 response when attempting to update taxonomy name


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


Repository: atlas


Description
---

Allows for updating of taxonomy and term property values, excluding the name 
property.


Diffs (updated)
-

  catalog/src/main/java/org/apache/atlas/catalog/BaseRequest.java 9ccb4e3 
  catalog/src/main/java/org/apache/atlas/catalog/BaseResourceProvider.java 
ad2f7f4 
  catalog/src/main/java/org/apache/atlas/catalog/CollectionRequest.java b1be1ae 
  catalog/src/main/java/org/apache/atlas/catalog/DefaultTypeSystem.java a28a32b 
  catalog/src/main/java/org/apache/atlas/catalog/EntityResourceProvider.java 
c8d6f68 
  catalog/src/main/java/org/apache/atlas/catalog/EntityTagResourceProvider.java 
f73f80b 
  catalog/src/main/java/org/apache/atlas/catalog/InstanceRequest.java 01583c4 
  catalog/src/main/java/org/apache/atlas/catalog/Request.java 7dc781a 
  catalog/src/main/java/org/apache/atlas/catalog/ResourceProvider.java 9c809c0 
  catalog/src/main/java/org/apache/atlas/catalog/TaxonomyResourceProvider.java 
0d63336 
  catalog/src/main/java/org/apache/atlas/catalog/TermResourceProvider.java 
0c72de6 
  catalog/src/main/java/org/apache/atlas/catalog/VertexWrapper.java 6e5d28e 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/BaseResourceDefinition.java
 32d6f30 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/EntityResourceDefinition.java
 cf55f1f 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/ResourceDefinition.java
 f310c5a 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/TaxonomyResourceDefinition.java
 a3fbdf1 
  
catalog/src/main/java/org/apache/atlas/catalog/definition/TermResourceDefinition.java
 19dd049 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityQuery.java 
c24b99a 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityTagQuery.java 
df216c0 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasQuery.java af14697 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasTermQuery.java 
b761dcc 
  catalog/src/main/java/org/apache/atlas/catalog/query/BaseQuery.java ba8e0e7 
  catalog/src/main/java/org/apache/atlas/catalog/query/QueryFactory.java 
39ce11a 
  catalog/src/test/java/org/apache/atlas/catalog/CollectionRequestTest.java 
0a2bace 
  
catalog/src/test/java/org/apache/atlas/catalog/EntityResourceProviderTest.java 
2f29103 
  
catalog/src/test/java/org/apache/atlas/catalog/EntityTagResourceProviderTest.java
 78204a6 
  catalog/src/test/java/org/apache/atlas/catalog/InstanceRequestTest.java 
5ccec02 
  
catalog/src/test/java/org/apache/atlas/catalog/TaxonomyResourceProviderTest.java
 a714a8c 
  catalog/src/test/java/org/apache/atlas/catalog/TermResourceProviderTest.java 
235bde4 
  catalog/src/test/java/org/apache/atlas/catalog/VertexWrapperTest.java 64935a6 
  
catalog/src/test/java/org/apache/atlas/catalog/definition/EntityResourceDefinitionTest.java
 303e2ba 
  
catalog/src/test/java/org/apache/atlas/catalog/definition/EntityTagResourceDefinitionTest.java
 954262f 
  
catalog/src/test/java/org/apache/atlas/catalog/definition/TaxonomyResourceDefinitionTest.java
 bc6f74c 
  
catalog/src/test/java/org/apache/atlas/catalog/definition/TermResourceDefinitionTest.java
 52deadf 
  
catalog/src/test/java/org/apache/atlas/catalog/query/AtlasEntityQueryTest.java 
149134c 
  webapp/src/main/java/org/apache/atlas/web/resources/BaseService.java 2a65538 
  webapp/src/main/java/org/apache/atlas/web/resources/TaxonomyService.java 
f995198 
  webapp/src/test/java/org/apache/atlas/web/resources/TaxonomyServiceTest.java 
a967805 

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


Testing
---

Added new unit tests.
All unit tests pass.
Manual functional tests including create/update/delete/get of 
taxonomies/terms/tags.


Thanks,

John Speidel

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-542:
---
Attachment: ATLAS-542.3.patch

Fixed some documentation issues as well

> Make qualifiedName and name consistent across all Datasets and Process
> --
>
> Key: ATLAS-542
> URL: https://issues.apache.org/jira/browse/ATLAS-542
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-542.1.patch, ATLAS-542.2.patch, ATLAS-542.3.patch, 
> ATLAS-542.patch
>
>
> Currently hive_db, hive_column has qualifiedName holding the fully qualified 
> Name and name having the shorter name. 
> However hive_table has the fully qualified Name in "name" and shorter Name in 
> tableName. We should make this consistent for better search experience by 
> removing tableName and keep it consistent with db, column
> Same with hive_process, storm_topology, falcon_process - needs to have a 
> qualifiedName 



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

[jira] [Updated] (ATLAS-890) Log received messages in case of error

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-890:
---
Summary: Log received messages in case of error  (was: Log received 
messages in case of error in Notification Hook Consumer)

> Log received messages in case of error
> --
>
> Key: ATLAS-890
> URL: https://issues.apache.org/jira/browse/ATLAS-890
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> This will be useful for further debugging



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

[jira] [Updated] (ATLAS-890) Log received messages in case of error

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-890:
---
Description: This will be useful for further debugging whenever an error 
occurs on ATLAS writes  (was: This will be useful for further debugging)

> Log received messages in case of error
> --
>
> Key: ATLAS-890
> URL: https://issues.apache.org/jira/browse/ATLAS-890
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
>
> This will be useful for further debugging whenever an error occurs on ATLAS 
> writes



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

[jira] [Commented] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-688:


Also pls update documentation to use import-hive.sh from hive server host 
instead of ATLAS host. 

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Attachments: ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



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

[jira] [Updated] (ATLAS-884) Process registration should call Entity update instead of create

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-884:
---
Attachment: ATLAS-884.1.patch

Thanks [~shwethags] . Added 2 tests - one to update with the same query, input 
and output tables and another one to CTAS, drop output table, rerun CTAS. the 
second test case's asserts might need to be fixed in ATLAS-876.

> Process registration should call Entity update instead of create
> 
>
> Key: ATLAS-884
> URL: https://issues.apache.org/jira/browse/ATLAS-884
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating, 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-884.1.patch, ATLAS-884.patch
>
>
> Process registration in hive hook currently calls Entity create . But should 
> call update entity instead 



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

[jira] [Created] (ATLAS-899) Fix Hive Hook documentation

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-899:
--

 Summary: Fix Hive Hook documentation
 Key: ATLAS-899
 URL: https://issues.apache.org/jira/browse/ATLAS-899
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Suma Shivaprasad
Assignee: Suma Shivaprasad
 Fix For: 0.7-incubating


Hive Hook docs need to be fixed since there were model changes 



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

[jira] [Updated] (ATLAS-890) Log received messages in case of error

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-890:
---
Attachment: ATLAS-890.patch

> Log received messages in case of error
> --
>
> Key: ATLAS-890
> URL: https://issues.apache.org/jira/browse/ATLAS-890
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-890.patch
>
>
> This will be useful for further debugging whenever an error occurs on ATLAS 
> writes



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

[jira] [Assigned] (ATLAS-877) CreateTime of an entity(for example hive table) changes for every update

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad reassigned ATLAS-877:
--

Assignee: Suma Shivaprasad  (was: Shwetha G S)

> CreateTime of an entity(for example hive table) changes for every update
> 
>
> Key: ATLAS-877
> URL: https://issues.apache.org/jira/browse/ATLAS-877
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Suma Shivaprasad
>Priority: Critical
> Fix For: 0.7-incubating
>
>
> Each time a hive table is updated(example column renamed), create time of 
> table is also updated.
> UI snapshot: https://monosnap.com/file/6NoT86CNpHgQmlyfBQTSUa1y3Ncc2Y
> hive table metadata snapshot from hive cli
> {noformat}
> 0: jdbc:hive2://localhost:1/default> describe formatted 
> column_changepgwcbgq1bd;
> OK
> +---+-+---+--+
> |   col_name|  
> data_type  |comment|
> +---+-+---+--+
> | # col_name| data_type   
> | comment   |
> |   | NULL
> | NULL  |
> | a3| int 
> |   |
> | b | int 
> |   |
> | c | int 
> |   |
> | d | int 
> |   |
> | e | int 
> |   |
> | f | int 
> |   |
> |   | NULL
> | NULL  |
> | # Detailed Table Information  | NULL
> | NULL  |
> | Database: | db2pgwcbgq1bd   
> | NULL  |
> | Owner:| apathan 
> | NULL  |
> | CreateTime:   | Wed Jun 08 12:41:28 IST 2016
> | NULL  |
> | LastAccessTime:   | UNKNOWN 
> | NULL  |
> | Protect Mode: | None
> | NULL  |
> | Retention:| 0   
> | NULL  |
> | Location: | 
> hdfs://localhost:9000/user/hive/warehouse/db2pgwcbgq1bd.db/column_changepgwcbgq1bd
>   | NULL  |
> | Table Type:   | MANAGED_TABLE   
> | NULL  |
> | Table Parameters: | NULL
> | NULL  |
> |   | COLUMN_STATS_ACCURATE   
> | false |
> |   | last_modified_by
> | apathan   |
> |   | last_modified_time  
> | 1465370834|
> |   | numFiles
> | 0 |
> |   | numR

[jira] [Updated] (ATLAS-882) with multiple taxonomies, UI does not allow associating terms with entities. "Add Terms" drop down shows all the taxonomies

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-882:
---
Assignee: Keval Bhatt

> with multiple taxonomies, UI does not allow associating terms with entities. 
> "Add Terms" drop down shows all the taxonomies
> ---
>
> Key: ATLAS-882
> URL: https://issues.apache.org/jira/browse/ATLAS-882
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-08 at 4.20.45 PM.png
>
>
> with multiple taxonomies, UI does not allow associating terms with entities. 
> "Add Terms" drop down shows all the taxonomies
> Attaching UI snapshot.
> Create multiple taxonomies with terms and try associating terms to entities, 
> UI does not allow it.



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

[jira] [Updated] (ATLAS-881) UI: not displaying multiple taxonomies

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-881:
---
Assignee: Keval Bhatt

> UI: not displaying multiple taxonomies
> --
>
> Key: ATLAS-881
> URL: https://issues.apache.org/jira/browse/ATLAS-881
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
>
> UI: not displaying multiple taxonomies
> API response returns multiple taxonomies
> {noformat}
> curl 'http://localhost:21000/api/atlas/v1/taxonomies/' -H 'Cookie: 
> JSESSIONID=19eplhd4dz8mueh7466qcbjwf' -H 'Accept-Encoding: gzip, deflate, 
> sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 
> (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) 
> Chrome/50.0.2661.102 Safari/537.36' -H 'Accept: application/json, 
> text/javascript, */*; q=0.01' -H 'Referer: http://localhost:21000/index.html' 
> -H 'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive' 
> --compressed | python -m json.tool
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100   3310   3310 0   4096  0 --:--:-- --:--:-- --:--:--  4137
> [
> {
> "href": "http://localhost:21000/api/atlas/v1/taxonomies/empty";,
> "name": "empty"
> },
> {
> "href": "http://localhost:21000/api/atlas/v1/taxonomies/tax1";,
> "name": "tax1"
> },
> {
> "href": "http://localhost:21000/api/atlas/v1/taxonomies/default";,
> "name": "default"
> }
> ]
> {noformat}
> UI snapshot: https://monosnap.com/file/1M6dOB8D08IPMqkqj3LsCr8VYvXWJG



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

[jira] [Updated] (ATLAS-734) DSL queries are currently case sensitive, from customer's perspective it is better to make them case insensitive

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-734:
---
Fix Version/s: (was: 0.7-incubating)

> DSL queries are currently case sensitive, from customer's perspective it is 
> better to make them case insensitive
> 
>
> Key: ATLAS-734
> URL: https://issues.apache.org/jira/browse/ATLAS-734
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>
> DSL queries are currently case sensitive, from customer's perspective it is 
> better to make them case insensitive.
> For example: hive_table DSL query would succeed but hive_Table DSL query will 
> fail.



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

[jira] [Updated] (ATLAS-725) UI : Filter out or highlight deleted entities in search result outputs(dsl, text) , schema view, and lineage graph

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-725:
---
 Assignee: Keval Bhatt
Affects Version/s: 0.7-incubating
 Priority: Blocker  (was: Major)

> UI : Filter out or highlight deleted entities in search result outputs(dsl, 
> text) , schema view, and lineage graph
> --
>
> Key: ATLAS-725
> URL: https://issues.apache.org/jira/browse/ATLAS-725
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> As part of soft deletes, the entities deleted are also being returned in the 
> search results, entity definition GET json, schema outputs and lineage graph 
> results. These need to be highlighted in a different notation



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

[jira] [Updated] (ATLAS-725) UI : Filter out or highlight deleted entities in search result outputs(dsl, text) , schema view, and lineage graph

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-725:
---
Assignee: Andrew Ahn  (was: Keval Bhatt)

> UI : Filter out or highlight deleted entities in search result outputs(dsl, 
> text) , schema view, and lineage graph
> --
>
> Key: ATLAS-725
> URL: https://issues.apache.org/jira/browse/ATLAS-725
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Andrew Ahn
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> As part of soft deletes, the entities deleted are also being returned in the 
> search results, entity definition GET json, schema outputs and lineage graph 
> results. These need to be highlighted in a different notation



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

[jira] [Commented] (ATLAS-725) UI : Filter out or highlight deleted entities in search result outputs(dsl, text) , schema view, and lineage graph

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-725:


[~aahn] can you please comment on how deleted entities should be handled in the 
UI?

> UI : Filter out or highlight deleted entities in search result outputs(dsl, 
> text) , schema view, and lineage graph
> --
>
> Key: ATLAS-725
> URL: https://issues.apache.org/jira/browse/ATLAS-725
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Andrew Ahn
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> As part of soft deletes, the entities deleted are also being returned in the 
> search results, entity definition GET json, schema outputs and lineage graph 
> results. These need to be highlighted in a different notation



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

[jira] [Resolved] (ATLAS-685) UI : HDFS datasets are not displayed correctly

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad resolved ATLAS-685.

Resolution: Invalid

Issue no loner exists in new ATLAS UI

> UI : HDFS datasets are not displayed correctly
> --
>
> Key: ATLAS-685
> URL: https://issues.apache.org/jira/browse/ATLAS-685
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-04-08 at 2.40.24 PM.png
>
>
> While testing HDFS datasets, found that the table alignment etc is not done 
> correctly and also need to decide on what attributes need to be displayed here



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

Re: Review Request 48533: Business Catalog Update

[Hemanth Yamijala]

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


Ship it!




Ship It!

- Hemanth Yamijala


On June 13, 2016, 7:29 p.m., John Speidel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48533/
> ---
> 
> (Updated June 13, 2016, 7:29 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-794
> https://issues.apache.org/jira/browse/ATLAS-794
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Allows for updating of taxonomy and term property values, excluding the name 
> property.
> 
> 
> Diffs
> -
> 
>   catalog/src/main/java/org/apache/atlas/catalog/BaseRequest.java 9ccb4e3 
>   catalog/src/main/java/org/apache/atlas/catalog/BaseResourceProvider.java 
> ad2f7f4 
>   catalog/src/main/java/org/apache/atlas/catalog/CollectionRequest.java 
> b1be1ae 
>   catalog/src/main/java/org/apache/atlas/catalog/DefaultTypeSystem.java 
> a28a32b 
>   catalog/src/main/java/org/apache/atlas/catalog/EntityResourceProvider.java 
> c8d6f68 
>   
> catalog/src/main/java/org/apache/atlas/catalog/EntityTagResourceProvider.java 
> f73f80b 
>   catalog/src/main/java/org/apache/atlas/catalog/InstanceRequest.java 01583c4 
>   catalog/src/main/java/org/apache/atlas/catalog/Request.java 7dc781a 
>   catalog/src/main/java/org/apache/atlas/catalog/ResourceProvider.java 
> 9c809c0 
>   
> catalog/src/main/java/org/apache/atlas/catalog/TaxonomyResourceProvider.java 
> 0d63336 
>   catalog/src/main/java/org/apache/atlas/catalog/TermResourceProvider.java 
> 0c72de6 
>   catalog/src/main/java/org/apache/atlas/catalog/VertexWrapper.java 6e5d28e 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/BaseResourceDefinition.java
>  32d6f30 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/EntityResourceDefinition.java
>  cf55f1f 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/ResourceDefinition.java
>  f310c5a 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/TaxonomyResourceDefinition.java
>  a3fbdf1 
>   
> catalog/src/main/java/org/apache/atlas/catalog/definition/TermResourceDefinition.java
>  19dd049 
>   catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityQuery.java 
> c24b99a 
>   
> catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityTagQuery.java 
> df216c0 
>   catalog/src/main/java/org/apache/atlas/catalog/query/AtlasQuery.java 
> af14697 
>   catalog/src/main/java/org/apache/atlas/catalog/query/AtlasTermQuery.java 
> b761dcc 
>   catalog/src/main/java/org/apache/atlas/catalog/query/BaseQuery.java ba8e0e7 
>   catalog/src/main/java/org/apache/atlas/catalog/query/QueryFactory.java 
> 39ce11a 
>   catalog/src/test/java/org/apache/atlas/catalog/CollectionRequestTest.java 
> 0a2bace 
>   
> catalog/src/test/java/org/apache/atlas/catalog/EntityResourceProviderTest.java
>  2f29103 
>   
> catalog/src/test/java/org/apache/atlas/catalog/EntityTagResourceProviderTest.java
>  78204a6 
>   catalog/src/test/java/org/apache/atlas/catalog/InstanceRequestTest.java 
> 5ccec02 
>   
> catalog/src/test/java/org/apache/atlas/catalog/TaxonomyResourceProviderTest.java
>  a714a8c 
>   
> catalog/src/test/java/org/apache/atlas/catalog/TermResourceProviderTest.java 
> 235bde4 
>   catalog/src/test/java/org/apache/atlas/catalog/VertexWrapperTest.java 
> 64935a6 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/EntityResourceDefinitionTest.java
>  303e2ba 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/EntityTagResourceDefinitionTest.java
>  954262f 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/TaxonomyResourceDefinitionTest.java
>  bc6f74c 
>   
> catalog/src/test/java/org/apache/atlas/catalog/definition/TermResourceDefinitionTest.java
>  52deadf 
>   
> catalog/src/test/java/org/apache/atlas/catalog/query/AtlasEntityQueryTest.java
>  149134c 
>   webapp/src/main/java/org/apache/atlas/web/resources/BaseService.java 
> 2a65538 
>   webapp/src/main/java/org/apache/atlas/web/resources/TaxonomyService.java 
> f995198 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/TaxonomyServiceTest.java 
> a967805 
> 
> Diff: https://reviews.apache.org/r/48533/diff/
> 
> 
> Testing
> ---
> 
> Added new unit tests.
> All unit tests pass.
> Manual functional tests including create/update/delete/get of 
> taxonomies/terms/tags.
> 
> 
> Thanks,
> 
> John Speidel
> 
>

[jira] [Commented] (ATLAS-794) Business Catalog Update

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-794:


I verified the latest patch and it addresses the issue with taxonomy name 
update. +1 from my end.

> Business Catalog Update
> ---
>
> Key: ATLAS-794
> URL: https://issues.apache.org/jira/browse/ATLAS-794
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-794-2.patch, ATLAS-794-3.patch, ATLAS-794.patch
>
>
> Business Catalog should support Update of all fields of a Term



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

[jira] [Commented] (ATLAS-505) Create Entity response from API should match the data in ATLAS_ENTITIES kafka topic when some attributes are set to null

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-505:


[~shwethags], you have marked this as fixed for 0.7 release. From what I 
understand given the consumers of ATLAS_ENTITIES and the API would be likely 
different, is this an important issue to fix? Also any change now to 
ATLAS_ENTITIES implies consumers may need to change, or test at a minimum. I 
would prefer punting this out of 0.7, unless there is a really good reason you 
think they should be the same.

> Create Entity response from API should match the data in ATLAS_ENTITIES kafka 
> topic when some attributes are set to null
> 
>
> Key: ATLAS-505
> URL: https://issues.apache.org/jira/browse/ATLAS-505
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Chethana
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: Type.txt, input_output.txt
>
>
> create a type in atlas 
> create an entity of type
> Make sure this entity is pushed to atlas topic
> The response from create entity API and data pushed to kafka queue should 
> match
> This could be possibly caused by different JSON libraries used between 
> Notification and API classes



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

[jira] [Updated] (ATLAS-567) create upgrade.sh that can be referenced in the documentation

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-567:
---
Fix Version/s: (was: 0.7-incubating)

> create upgrade.sh that can be referenced in the documentation
> -
>
> Key: ATLAS-567
> URL: https://issues.apache.org/jira/browse/ATLAS-567
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Erik Bergenholtz
>Priority: Critical
> Attachments: ATLAS-567.patch
>
>
> In order to prepare for future upgrades, it would be nice to have an 
> "upgrade" file that can be invoked that will (in the future) take care of any 
> upgrade steps.
> A first cut of the file will yield an empty file that can be augmented as 
> necessary. This script will also be invoked by external coordinators such as 
> Ambari.



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

[jira] [Commented] (ATLAS-567) create upgrade.sh that can be referenced in the documentation

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-567:


Removed this from 0.7 queue as there is nothing identified to date. We can add 
this back once we know more.

> create upgrade.sh that can be referenced in the documentation
> -
>
> Key: ATLAS-567
> URL: https://issues.apache.org/jira/browse/ATLAS-567
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Erik Bergenholtz
>Priority: Critical
> Attachments: ATLAS-567.patch
>
>
> In order to prepare for future upgrades, it would be nice to have an 
> "upgrade" file that can be invoked that will (in the future) take care of any 
> upgrade steps.
> A first cut of the file will yield an empty file that can be augmented as 
> necessary. This script will also be invoked by external coordinators such as 
> Ambari.



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

[jira] [Resolved] (ATLAS-691) Update Utilities to support authentication

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-691.

Resolution: Duplicate

Resolved via ATLAS-497 and ATLAS-820.

> Update Utilities to support authentication
> --
>
> Key: ATLAS-691
> URL: https://issues.apache.org/jira/browse/ATLAS-691
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> The various atlas/bin utilities need to be able to pass credentials in order 
> to properly authenticate once REST API authentication is enabled.



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

[jira] [Updated] (ATLAS-808) Not all properties of a business term are used when a term instance is associated to an entity

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-808:
---
Fix Version/s: (was: 0.7-incubating)

> Not all properties of a business term are used when a term instance is 
> associated to an entity
> --
>
> Key: ATLAS-808
> URL: https://issues.apache.org/jira/browse/ATLAS-808
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>Priority: Critical
>
> When a business term is defined, it is defined with a certain set of 
> properties. When the same term is associated to an entity, an instance is 
> created, but only the name and description attributes are copied over to the 
> instance. This will result in missing other attributes.



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

[jira] [Commented] (ATLAS-808) Not all properties of a business term are used when a term instance is associated to an entity

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-808:


Currently, only name and description are being handled in the UI. Hence, will 
punt this out of 0.7, but keep the bug on for enhancements to business catalog.

> Not all properties of a business term are used when a term instance is 
> associated to an entity
> --
>
> Key: ATLAS-808
> URL: https://issues.apache.org/jira/browse/ATLAS-808
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>Priority: Critical
>
> When a business term is defined, it is defined with a certain set of 
> properties. When the same term is associated to an entity, an instance is 
> created, but only the name and description attributes are copied over to the 
> instance. This will result in missing other attributes.



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

[jira] [Resolved] (ATLAS-838) hive table schema api is broken.

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-838.

Resolution: Fixed

This was due to unsynchronized changes in configuration. It is fixed now.

> hive table schema api is broken.
> 
>
> Key: ATLAS-838
> URL: https://issues.apache.org/jira/browse/ATLAS-838
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> Create a hive table and make schema call on that table.
> {noformat}
> curl -v 
> 'http://os-r7-wbucju-atlas-re-2.openstacklocal:21000/api/atlas/lineage/03f469a7-0eae-4247-a710-38529f767952/schema'
>  -H 'Cookie: JSESSIONID=v1drbnjb5y4847uj20vinoyh' -H 'Accept-Encoding: gzip, 
> deflate, sdch' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: 
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, 
> like Gecko) Chrome/50.0.2661.102 Safari/537.36' -H 'Accept: application/json, 
> text/javascript, */*; q=0.01' -H 'Referer: 
> http://os-r7-wbucju-atlas-re-2.openstacklocal:21000/index.html' -H 
> 'X-Requested-With: XMLHttpRequest' -H 'Connection: keep-alive' --compressed
> *   Trying 172.22.90.59...
> * Connected to os-r7-wbucju-atlas-re-2.openstacklocal (172.22.90.59) port 
> 21000 (#0)
> > GET /api/atlas/lineage/03f469a7-0eae-4247-a710-38529f767952/schema HTTP/1.1
> > Host: os-r7-wbucju-atlas-re-2.openstacklocal:21000
> > Cookie: JSESSIONID=v1drbnjb5y4847uj20vinoyh
> > Accept-Encoding: gzip, deflate, sdch
> > Accept-Language: en-US,en;q=0.8
> > User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) 
> > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
> > Accept: application/json, text/javascript, */*; q=0.01
> > Referer: http://os-r7-wbucju-atlas-re-2.openstacklocal:21000/index.html
> > X-Requested-With: XMLHttpRequest
> > Connection: keep-alive
> >
> < HTTP/1.1 500 Internal Server Error
> < Date: Sat, 28 May 2016 17:59:34 GMT
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> {"error":"Failed with 
> java.lang.NullPointerException","stackTrace":"java.lang.NullPointerException\n\tat
>  java.util.regex.Matcher.getTextLength(Matcher.java:1234)\n\tat 
> java.util.regex.Matcher.reset(Matcher.java:308)\n\tat 
> java.util.regex.Matcher.(Matcher.java:228)\n\tat 
> java.util.regex.Pattern.matcher(Pattern.java:1088)\n\tat 
> java.util.Formatter.parse(Formatter.java:2515)\n\tat 
> java.util.Formatter.format(Formatter.java:2469)\n\tat 
> java.util.Formatter.format(Formatter.java:2423)\n\tat 
> java.lang.String.format(String.java:2790)\n\tat 
> org.apache.atlas.discovery.DataSetLineageService.getSchemaForId(DataSetLineageService.java:171)\n\tat
>  
> org.apache.atlas.discovery.DataSetLineageService.getSchemaForEntity(DataSetLineageService.java:181)\n\tat
>  
> org.apache.atlas.web.resources.LineageResource.schema(LineageResource.java:135)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.

[jira] [Resolved] (ATLAS-505) Create Entity response from API should match the data in ATLAS_ENTITIES kafka topic when some attributes are set to null

[Shwetha G S (JIRA)]

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

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

> Create Entity response from API should match the data in ATLAS_ENTITIES kafka 
> topic when some attributes are set to null
> 
>
> Key: ATLAS-505
> URL: https://issues.apache.org/jira/browse/ATLAS-505
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Chethana
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: Type.txt, input_output.txt
>
>
> create a type in atlas 
> create an entity of type
> Make sure this entity is pushed to atlas topic
> The response from create entity API and data pushed to kafka queue should 
> match
> This could be possibly caused by different JSON libraries used between 
> Notification and API classes



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

[jira] [Commented] (ATLAS-505) Create Entity response from API should match the data in ATLAS_ENTITIES kafka topic when some attributes are set to null

[Shwetha G S (JIRA)]

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

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

If we release this out now, we will have to support it for a long time. Hence I 
wanted to take a look at it now to figure out the issue and scope of fix. 
Looking at input_output.txt, the entity definition json is same, but the topic 
message has more fields like message type, which I think is valid. So, will 
resolve this as not a problem

> Create Entity response from API should match the data in ATLAS_ENTITIES kafka 
> topic when some attributes are set to null
> 
>
> Key: ATLAS-505
> URL: https://issues.apache.org/jira/browse/ATLAS-505
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Chethana
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: Type.txt, input_output.txt
>
>
> create a type in atlas 
> create an entity of type
> Make sure this entity is pushed to atlas topic
> The response from create entity API and data pushed to kafka queue should 
> match
> This could be possibly caused by different JSON libraries used between 
> Notification and API classes



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

[jira] [Updated] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-435:
---
Fix Version/s: (was: 0.7-incubating)

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



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

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-435:


Since this is an enhancement, I am assuming this will not make 0.7. Also, it 
looks like this issue itself is fixed, but some sub-tasks are not. If we feel 
this issue is fixed and is independent - we could resolve it as such, and 
delink the sub-task. [~suma.shivaprasad]? [~guptaneeru]?

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



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

[jira] [Commented] (ATLAS-888) NPE in NotificationHookConsumer

[Shwetha G S (JIRA)]

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

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

{code}
UriBuilder builder = UriBuilder
156 .fromPath(AtlasConstants.DEFAULT_ATLAS_REST_ADDRESS)
157 .path(uriPath).path(guids.get(0));
158 
{code}
This will fail if guids is empty

What are the changes in log statements? 

> NPE in NotificationHookConsumer
> ---
>
> Key: ATLAS-888
> URL: https://issues.apache.org/jira/browse/ATLAS-888
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-888.patch
>
>
> 2016-06-08 15:54:22,375 ERROR - [NotificationHookConsumer thread-0:] ~ Unable 
> to persist entity instance (EntityResource:137)
> java.lang.NullPointerException
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:652)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:203)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:187)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2016-06-08 15:54:22,376 WARN  - [NotificationHookConsumer thread-0:] ~ Error 
> handling message 
> org.apache.atlas.notification.hook.HookNotification$EntityCreateRequest@6b8492f1
>  (NotificationHookConsumer:233)
> org.apache.atlas.AtlasServiceException: Metadata service API CREATE_ENTITY 
> failed with status 500(Internal Server Error) Response Body 
> (java.lang.NullPointerException
> at 
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:122)
> at 
> org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82)
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:652)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:203)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:187)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> )
> at 
> org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:122)
> at 
> org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85)
> at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:652)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:203)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:187)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)



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

[jira] [Commented] (ATLAS-891) UI changes to implement Update term

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-891:


Tested this once more on top of the committed ATLAS-794. Things are fine. Will 
commit the patch after running tests once.

> UI changes to implement Update term
> ---
>
> Key: ATLAS-891
> URL: https://issues.apache.org/jira/browse/ATLAS-891
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-891.1.patch
>
>
> Need to implement update term feature, once ATLAS-794 is committed. UI side 
> changes will be made available on this patch.



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

[jira] [Commented] (ATLAS-884) Process registration should call Entity update instead of create

[Shwetha G S (JIRA)]

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

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

In testUpdateProcess(), can you use new query for the update say,  "insert 
overwrite DIRECTORY '" + pFile1  + "' select id from " + tableName and verify 
that query string is updated? Looks good otherwise. You can fix and commit. 
Thanks

> Process registration should call Entity update instead of create
> 
>
> Key: ATLAS-884
> URL: https://issues.apache.org/jira/browse/ATLAS-884
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating, 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-884.1.patch, ATLAS-884.patch
>
>
> Process registration in hive hook currently calls Entity create . But should 
> call update entity instead 



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

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

[Apache Jenkins Server]

See 

Changes:

[hyamijala] ATLAS-794 Business Catalog Update (jspeidel via yhemanth)

--
[...truncated 5924 lines...]
[INFO] Using incremental compilation
[INFO] Compiling 56 Java sources to 

[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:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 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-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 41 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [1940 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-webapp ---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.
[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.web.service.ActiveInstanceElectorServiceTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.315 sec - in 
org.apache.atlas.web.service.ActiveInstanceElectorServiceTest
Running org.apache.atlas.web.service.CuratorFactoryTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0,