[jira] [Updated] (ATLAS-77) REST API to access all functions in Atlas

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn updated ATLAS-77:

Description: 
Create REST API to access all functions in Atlas.   Specifically the 
capabilities should include:

1Create new types
2Modify existing types
3Create new relationships for all types (data and trait)
4Remove relationships -- disassociate
5Allow assignment of properties to all types
6Allow search for type, entity, properties
7Return search results - detail, lineage (relations)

These API's will be used for UI, HDP component and 3rd party interfaces.
Summary: REST API  to access all functions in Atlas  (was: REST API to 
create new connections to Atlas)

 REST API  to access all functions in Atlas
 --

 Key: ATLAS-77
 URL: https://issues.apache.org/jira/browse/ATLAS-77
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George

 Create REST API to access all functions in Atlas.   Specifically the 
 capabilities should include:
 1Create new types
 2Modify existing types
 3Create new relationships for all types (data and trait)
 4Remove relationships -- disassociate
 5Allow assignment of properties to all types
 6Allow search for type, entity, properties
 7Return search results - detail, lineage (relations)
 These API's will be used for UI, HDP component and 3rd party interfaces.



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


[jira] [Updated] (ATLAS-76) Atlas business classification

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn updated ATLAS-76:

Assignee: Venkatesh Seetharam

 Atlas business classification
 -

 Key: ATLAS-76
 URL: https://issues.apache.org/jira/browse/ATLAS-76
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George
Assignee: Venkatesh Seetharam

 Create an agile facility to model a business organizational taxonomy.   This 
 logical model would include the following capabilities:
 1   Allow the creation a hierarchical model 
 2   Allow the creation of properties to any object in the model
 3   Have inheritance so that child objects will get the same attributes 
 (association) as the parent object.
 4   Related to data object such as a Hive table, Kafka topic or Storm 
 topology.
 5   Be able to create (import) and report (export) on structures in bulk or 
 ad hoc.
  



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


[jira] [Updated] (ATLAS-75) Atlas Hive integration

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn updated ATLAS-75:

 Due Date: 17/Jul/15
Fix Version/s: 0.5.1-incubating

 Atlas Hive integration
 --

 Key: ATLAS-75
 URL: https://issues.apache.org/jira/browse/ATLAS-75
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George
Assignee: Venkatesh Seetharam
 Fix For: 0.5.1-incubating


 Native Atlas connector for Hive.
 This should be a jar file - or a simple install- to add to Hive to allow 
 complete capture for Hive metadata will Atlas.   
 1) Should require no configuration from either Hive or Altas
 2) Have bootstrapping capability to get an initial synch. Should be able to 
 re-run in the event of DR situations.
 3) Post - Execution Hive Hook to capture incremental changes.   This should 
 not impact Hive performance or reliability.



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


[jira] [Resolved] (ATLAS-77) REST API to access all functions in Atlas

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn resolved ATLAS-77.
-
Resolution: Fixed

 REST API  to access all functions in Atlas
 --

 Key: ATLAS-77
 URL: https://issues.apache.org/jira/browse/ATLAS-77
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George
Assignee: Venkatesh Seetharam
 Fix For: 0.5.1-incubating


 Create REST API to access all functions in Atlas.   Specifically the 
 capabilities should include:
 1Create new types
 2Modify existing types
 3Create new relationships for all types (data and trait)
 4Remove relationships -- disassociate
 5Allow assignment of properties to all types
 6Allow search for type, entity, properties
 7Return search results - detail, lineage (relations)
 These API's will be used for UI, HDP component and 3rd party interfaces.



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


[jira] [Updated] (ATLAS-77) REST API to access all functions in Atlas

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn updated ATLAS-77:

Assignee: Venkatesh Seetharam

 REST API  to access all functions in Atlas
 --

 Key: ATLAS-77
 URL: https://issues.apache.org/jira/browse/ATLAS-77
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George
Assignee: Venkatesh Seetharam

 Create REST API to access all functions in Atlas.   Specifically the 
 capabilities should include:
 1Create new types
 2Modify existing types
 3Create new relationships for all types (data and trait)
 4Remove relationships -- disassociate
 5Allow assignment of properties to all types
 6Allow search for type, entity, properties
 7Return search results - detail, lineage (relations)
 These API's will be used for UI, HDP component and 3rd party interfaces.



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


[jira] [Updated] (ATLAS-75) Atlas Hive integration

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn updated ATLAS-75:

Description: 
Native Atlas connector for Hive.

This should be a jar file - or a simple install- to add to Hive to allow 
complete capture for Hive metadata will Atlas.   

1) Should require no configuration from either Hive or Altas
2) Have bootstrapping capability to get an initial synch. Should be able to 
re-run in the event of DR situations.
3) Post - Execution Hive Hook to capture incremental changes.   This should not 
impact Hive performance or reliability.


 Atlas Hive integration
 --

 Key: ATLAS-75
 URL: https://issues.apache.org/jira/browse/ATLAS-75
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George

 Native Atlas connector for Hive.
 This should be a jar file - or a simple install- to add to Hive to allow 
 complete capture for Hive metadata will Atlas.   
 1) Should require no configuration from either Hive or Altas
 2) Have bootstrapping capability to get an initial synch. Should be able to 
 re-run in the event of DR situations.
 3) Post - Execution Hive Hook to capture incremental changes.   This should 
 not impact Hive performance or reliability.



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


[jira] [Resolved] (ATLAS-75) Atlas Hive integration

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn resolved ATLAS-75.
-
Resolution: Fixed

 Atlas Hive integration
 --

 Key: ATLAS-75
 URL: https://issues.apache.org/jira/browse/ATLAS-75
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George
Assignee: Venkatesh Seetharam
 Fix For: 0.5.1-incubating


 Native Atlas connector for Hive.
 This should be a jar file - or a simple install- to add to Hive to allow 
 complete capture for Hive metadata will Atlas.   
 1) Should require no configuration from either Hive or Altas
 2) Have bootstrapping capability to get an initial synch. Should be able to 
 re-run in the event of DR situations.
 3) Post - Execution Hive Hook to capture incremental changes.   This should 
 not impact Hive performance or reliability.



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


[jira] [Commented] (ATLAS-18) Build fails because of a missing artifact

2015-07-21 Thread Erik Bergenholtz (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635536#comment-14635536
 ] 

Erik Bergenholtz commented on ATLAS-18:
---

[~ajayyadava] - Let's close this as CNR if it can not be reproduced.

 Build fails because of a missing artifact
 -

 Key: ATLAS-18
 URL: https://issues.apache.org/jira/browse/ATLAS-18
 Project: Atlas
  Issue Type: Improvement
Reporter: Ajay Yadava
Assignee: Ajay Yadava
 Attachments: ATLAS-18.patch


 Current build fails with the following complaint.
 Failed to execute goal on project hive-bridge: Could not resolve dependencies 
 for project org.apache.atlas:hive-bridge:jar:0.1-incubating-SNAPSHOT: Could 
 not find artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
 It's not available in any of the repositories mentioned in the pom.xml.



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


[jira] [Updated] (ATLAS-77) REST API to access all functions in Atlas

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn updated ATLAS-77:

 Due Date: 17/Jul/15
Fix Version/s: 0.5.1-incubating

 REST API  to access all functions in Atlas
 --

 Key: ATLAS-77
 URL: https://issues.apache.org/jira/browse/ATLAS-77
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George
Assignee: Venkatesh Seetharam
 Fix For: 0.5.1-incubating


 Create REST API to access all functions in Atlas.   Specifically the 
 capabilities should include:
 1Create new types
 2Modify existing types
 3Create new relationships for all types (data and trait)
 4Remove relationships -- disassociate
 5Allow assignment of properties to all types
 6Allow search for type, entity, properties
 7Return search results - detail, lineage (relations)
 These API's will be used for UI, HDP component and 3rd party interfaces.



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


[jira] [Updated] (ATLAS-76) Atlas business classification

2015-07-21 Thread Andrew Ahn (JIRA)

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

Andrew Ahn updated ATLAS-76:

 Due Date: 17/Jul/15
Fix Version/s: 0.5.1-incubating

 Atlas business classification
 -

 Key: ATLAS-76
 URL: https://issues.apache.org/jira/browse/ATLAS-76
 Project: Atlas
  Issue Type: New Feature
Affects Versions: 0.5-incubating
Reporter: Linda George
Assignee: Venkatesh Seetharam
 Fix For: 0.5.1-incubating


 Create an agile facility to model a business organizational taxonomy.   This 
 logical model would include the following capabilities:
 1   Allow the creation a hierarchical model 
 2   Allow the creation of properties to any object in the model
 3   Have inheritance capabilites so that child objects will get the same 
 attributes (association) as the parent object.
 4   Allow relating business logical model to data objects such as a Hive 
 table, Kafka topic or Storm topology.
 5   Be able to create (import) and report (export) on structures in bulk or 
 ad hoc.
  



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


[jira] [Commented] (ATLAS-16) jersey jaxb exception

2015-07-21 Thread Erik Bergenholtz (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635533#comment-14635533
 ] 

Erik Bergenholtz commented on ATLAS-16:
---

Is this still an issue, if so, what are the steps to re-produce?

 jersey jaxb exception
 -

 Key: ATLAS-16
 URL: https://issues.apache.org/jira/browse/ATLAS-16
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S

 {noformat}
 Jun 16, 2015 1:37:42 PM 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator 
 attachTypes
 INFO: Couldn't find JAX-B element for class javax.ws.rs.core.Response
 Jun 16, 2015 1:37:42 PM 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8 
 resolve
 SEVERE: null
 java.lang.IllegalAccessException: Class 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8 can 
 not access a member of class javax.ws.rs.core.Response with modifiers 
 protected
   at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:109)
   at java.lang.Class.newInstance(Class.java:373)
   at 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8.resolve(WadlGeneratorJAXBGrammarGenerator.java:467)
   at 
 com.sun.jersey.server.wadl.WadlGenerator$ExternalGrammarDefinition.resolve(WadlGenerator.java:181)
   at 
 com.sun.jersey.server.wadl.ApplicationDescription.resolve(ApplicationDescription.java:81)
   at 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator.attachTypes(WadlGeneratorJAXBGrammarGenerator.java:518)
   at com.sun.jersey.server.wadl.WadlBuilder.generate(WadlBuilder.java:151)
   at 
 com.sun.jersey.server.impl.wadl.WadlApplicationContextImpl.getApplication(WadlApplicationContextImpl.java:125)
   at 
 com.sun.jersey.server.impl.wadl.WadlMethodFactory$WadlOptionsMethodDispatcher.dispatch(WadlMethodFactory.java:98)
   at 
 com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
   at 
 com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
   at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
   at 
 com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
   at 
 com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
   at 
 com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
   at 
 com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
   at 
 com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
   at 
 org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:67)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
   at 
 com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
   at 
 com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
   at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
   at 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 
 

[jira] [Updated] (ATLAS-16) jersey jaxb exception

2015-07-21 Thread Erik Bergenholtz (JIRA)

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

Erik Bergenholtz updated ATLAS-16:
--
Fix Version/s: 0.6-incubating

 jersey jaxb exception
 -

 Key: ATLAS-16
 URL: https://issues.apache.org/jira/browse/ATLAS-16
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
 Fix For: 0.6-incubating


 {noformat}
 Jun 16, 2015 1:37:42 PM 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator 
 attachTypes
 INFO: Couldn't find JAX-B element for class javax.ws.rs.core.Response
 Jun 16, 2015 1:37:42 PM 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8 
 resolve
 SEVERE: null
 java.lang.IllegalAccessException: Class 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8 can 
 not access a member of class javax.ws.rs.core.Response with modifiers 
 protected
   at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:109)
   at java.lang.Class.newInstance(Class.java:373)
   at 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8.resolve(WadlGeneratorJAXBGrammarGenerator.java:467)
   at 
 com.sun.jersey.server.wadl.WadlGenerator$ExternalGrammarDefinition.resolve(WadlGenerator.java:181)
   at 
 com.sun.jersey.server.wadl.ApplicationDescription.resolve(ApplicationDescription.java:81)
   at 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator.attachTypes(WadlGeneratorJAXBGrammarGenerator.java:518)
   at com.sun.jersey.server.wadl.WadlBuilder.generate(WadlBuilder.java:151)
   at 
 com.sun.jersey.server.impl.wadl.WadlApplicationContextImpl.getApplication(WadlApplicationContextImpl.java:125)
   at 
 com.sun.jersey.server.impl.wadl.WadlMethodFactory$WadlOptionsMethodDispatcher.dispatch(WadlMethodFactory.java:98)
   at 
 com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
   at 
 com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
   at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
   at 
 com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
   at 
 com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
   at 
 com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
   at 
 com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
   at 
 com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
   at 
 org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:67)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
   at 
 com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
   at 
 com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
   at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
   at 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 
 

[jira] [Commented] (ATLAS-16) jersey jaxb exception

2015-07-21 Thread Erik Bergenholtz (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635552#comment-14635552
 ] 

Erik Bergenholtz commented on ATLAS-16:
---

Targeting resolve by next release.

 jersey jaxb exception
 -

 Key: ATLAS-16
 URL: https://issues.apache.org/jira/browse/ATLAS-16
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
 Fix For: 0.6-incubating


 {noformat}
 Jun 16, 2015 1:37:42 PM 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator 
 attachTypes
 INFO: Couldn't find JAX-B element for class javax.ws.rs.core.Response
 Jun 16, 2015 1:37:42 PM 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8 
 resolve
 SEVERE: null
 java.lang.IllegalAccessException: Class 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8 can 
 not access a member of class javax.ws.rs.core.Response with modifiers 
 protected
   at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:109)
   at java.lang.Class.newInstance(Class.java:373)
   at 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator$8.resolve(WadlGeneratorJAXBGrammarGenerator.java:467)
   at 
 com.sun.jersey.server.wadl.WadlGenerator$ExternalGrammarDefinition.resolve(WadlGenerator.java:181)
   at 
 com.sun.jersey.server.wadl.ApplicationDescription.resolve(ApplicationDescription.java:81)
   at 
 com.sun.jersey.server.wadl.generators.WadlGeneratorJAXBGrammarGenerator.attachTypes(WadlGeneratorJAXBGrammarGenerator.java:518)
   at com.sun.jersey.server.wadl.WadlBuilder.generate(WadlBuilder.java:151)
   at 
 com.sun.jersey.server.impl.wadl.WadlApplicationContextImpl.getApplication(WadlApplicationContextImpl.java:125)
   at 
 com.sun.jersey.server.impl.wadl.WadlMethodFactory$WadlOptionsMethodDispatcher.dispatch(WadlMethodFactory.java:98)
   at 
 com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
   at 
 com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
   at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
   at 
 com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
   at 
 com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at 
 com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
   at 
 com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
   at 
 com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
   at 
 com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
   at 
 org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:67)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
   at 
 com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
   at 
 com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
   at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
   at 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
   at 
 org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
   at 

Re: Review Request 36611: ATLAS-74 Create notification framework

2015-07-21 Thread Shwetha GS


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  notification/src/main/java/org/apache/atlas/notification/NotificationModule.java,
   line 26
  https://reviews.apache.org/r/36611/diff/1/?file=1016160#file1016160line26
 
  Is there a way to externalize this? How do folks say wrap another 
  implementaiton - for future.
 
 Shwetha GS wrote:
 I didn't want to add to just config as we use Guice everywhere. Add to 
 config and use that in Guice? Makes sense, will change.

Can I add this once we merge client and application properties? Wil do it soon. 
Currently, Guice is the way to go


- Shwetha


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


On July 20, 2015, 6:14 a.m., Shwetha GS wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/36611/
 ---
 
 (Updated July 20, 2015, 6:14 a.m.)
 
 
 Review request for atlas.
 
 
 Bugs: ATLAS-74
 https://issues.apache.org/jira/browse/ATLAS-74
 
 
 Repository: atlas
 
 
 Description
 ---
 
 Add notification framework with kafka as default implementation
 
 
 Diffs
 -
 
   client/src/main/java/org/apache/atlas/PropertiesUtil.java bc56cbf 
   notification/pom.xml PRE-CREATION 
   notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 
 PRE-CREATION 
   notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
 PRE-CREATION 
   
 notification/src/main/java/org/apache/atlas/notification/ConsumerInterface.java
  PRE-CREATION 
   
 notification/src/main/java/org/apache/atlas/notification/NotificationException.java
  PRE-CREATION 
   
 notification/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
  PRE-CREATION 
   
 notification/src/main/java/org/apache/atlas/notification/NotificationInterface.java
  PRE-CREATION 
   
 notification/src/main/java/org/apache/atlas/notification/NotificationModule.java
  PRE-CREATION 
   
 notification/src/test/java/org/apache/atlas/kafka/kafkaNotificationTest.java 
 PRE-CREATION 
   pom.xml 6e7c10c 
   src/conf/application.properties 6c4c7d2 
   typesystem/src/main/resources/application.properties 29c933f 
   typesystem/src/main/resources/log4j.xml 742f674 
   webapp/src/main/java/org/apache/atlas/Main.java 1dd17b4 
   webapp/src/main/java/org/apache/atlas/web/service/EmbeddedServer.java 
 88200f0 
   webapp/src/main/resources/application.properties c9b8408 
 
 Diff: https://reviews.apache.org/r/36611/diff/
 
 
 Testing
 ---
 
 UTs
 
 
 Thanks,
 
 Shwetha GS
 




[jira] [Updated] (ATLAS-46) Different data directory with restart

2015-07-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-46:
-
Affects Version/s: 0.5-incubating

 Different data directory with restart
 -

 Key: ATLAS-46
 URL: https://issues.apache.org/jira/browse/ATLAS-46
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.5-incubating
Reporter: Shwetha G S
Assignee: Shwetha G S
Priority: Critical
 Fix For: trunk

 Attachments: ATLAS-46.patch, application.log


 Atlas start picks up different data directories - initially 
 ./server/webapp/atlas/data and after restart ./data. This must be because of 
 relative path in the configuration
 {noformat}
 apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep -i atlas
   504  6437 1   0 11:51AM ttys0000:07.66 
 /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
 -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
  -Datlas.log.file=application.log 
 -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
  
 -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
  -Xmx1024m -classpath 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
  org.apache.atlas.Main -app 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
 apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
 ./server/webapp/atlas/data
 ./server/webapp/atlas/data/es/data
 ./server/webapp/atlas/lib/jquery/src/data
 apache-atlas-0.6-incubating-SNAPSHOT$ ./bin/atlas_stop.py
 apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep atlas
   504  6457 1   0 11:54AM ttys0000:07.50 
 /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
 -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
  -Datlas.log.file=application.log 
 -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
  
 -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
  -Xmx1024m -classpath 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
  org.apache.atlas.Main -app 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
 apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
 ./data
 ./data/es/data
 ./server/webapp/atlas/data
 ./server/webapp/atlas/data/es/data
 ./server/webapp/atlas/lib/jquery/src/data
 {noformat}



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


[jira] [Commented] (ATLAS-46) Different data directory with restart

2015-07-21 Thread Shwetha G S (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634928#comment-14634928
 ] 

Shwetha G S commented on ATLAS-46:
--

Atlas package start is failing with relative path. However, after a restart it 
works fine. Checking

 Different data directory with restart
 -

 Key: ATLAS-46
 URL: https://issues.apache.org/jira/browse/ATLAS-46
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.5-incubating
Reporter: Shwetha G S
Assignee: Shwetha G S
Priority: Critical
 Fix For: trunk

 Attachments: ATLAS-46.patch, application.log


 Atlas start picks up different data directories - initially 
 ./server/webapp/atlas/data and after restart ./data. This must be because of 
 relative path in the configuration
 {noformat}
 apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep -i atlas
   504  6437 1   0 11:51AM ttys0000:07.66 
 /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
 -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
  -Datlas.log.file=application.log 
 -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
  
 -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
  -Xmx1024m -classpath 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
  org.apache.atlas.Main -app 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
 apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
 ./server/webapp/atlas/data
 ./server/webapp/atlas/data/es/data
 ./server/webapp/atlas/lib/jquery/src/data
 apache-atlas-0.6-incubating-SNAPSHOT$ ./bin/atlas_stop.py
 apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep atlas
   504  6457 1   0 11:54AM ttys0000:07.50 
 /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
 -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
  -Datlas.log.file=application.log 
 -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
  
 -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
  -Xmx1024m -classpath 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
  org.apache.atlas.Main -app 
 /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
 apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
 ./data
 ./data/es/data
 ./server/webapp/atlas/data
 ./server/webapp/atlas/data/es/data
 ./server/webapp/atlas/lib/jquery/src/data
 {noformat}



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


Re: Review Request 36611: ATLAS-74 Create notification framework

2015-07-21 Thread Shwetha GS


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  client/src/main/java/org/apache/atlas/PropertiesUtil.java, line 42
  https://reviews.apache.org/r/36611/diff/1/?file=1016152#file1016152line42
 
  Merge may have conflicts, no? Isnt this dangerous? Why cant we treat 
  this separate configs?

kafka related configs like endpoint etc need to be shared between client and 
server. Don't want to define twice(both in client.properties and 
application.properties) and handle discrepancy issues later. Want to get rid of 
client.properties once we have consensus. Re-using client configs till then 
this way


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  pom.xml, line 976
  https://reviews.apache.org/r/36611/diff/1/?file=1016162#file1016162line976
 
  Why is this necessary?

For embedded kafka


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  notification/src/main/java/org/apache/atlas/notification/ConsumerInterface.java,
   line 20
  https://reviews.apache.org/r/36611/diff/1/?file=1016156#file1016156line20
 
  Seriously, suffix with Interface? :-)
  
  How close is this to JMS?

Didn't have a better name, will rename

JMS has receive(timeout). But kafka doesn't expose this interface currently. 
The one added here is the only kafka consumer interface. The new 
receive(timeout) interface is still in the works, we can change once thats 
released


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  notification/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java,
   line 66
  https://reviews.apache.org/r/36611/diff/1/?file=1016158#file1016158line66
 
  There is an implicit assumption that we always create the entity json 
  and put it in the broker? 
  
  Should we verify the layload?

Still need work in this. Just added basic kafka messaging as part of this 
patch. Will finalise the hook message format in another patch


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  notification/src/main/java/org/apache/atlas/notification/NotificationInterface.java,
   line 26
  https://reviews.apache.org/r/36611/diff/1/?file=1016159#file1016159line26
 
  Seriously, suffix with Interface? :-)

I don't have any better name, please suggest:)


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  notification/src/main/java/org/apache/atlas/notification/NotificationInterface.java,
   line 33
  https://reviews.apache.org/r/36611/diff/1/?file=1016159#file1016159line33
 
  Should we also allow Traits as a specific notofication type? 
  
  Hook generalizes all components - do we need anything specific here? 
  Cant think of any ATM

Didn't want to expose topic name to clients and hence added notification type. 

Yes, we need traits. Will add as part of entity/type notification.

Don't want to add any component specific part in the hook message. Else, we 
need to depend on all components and their internals?


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  notification/src/main/java/org/apache/atlas/notification/NotificationModule.java,
   line 26
  https://reviews.apache.org/r/36611/diff/1/?file=1016160#file1016160line26
 
  Is there a way to externalize this? How do folks say wrap another 
  implementaiton - for future.

I didn't want to add to just config as we use Guice everywhere. Add to config 
and use that in Guice? Makes sense, will change.


 On July 20, 2015, 11:16 p.m., Seetharam Venkatesh wrote:
  src/conf/application.properties, line 32
  https://reviews.apache.org/r/36611/diff/1/?file=1016163#file1016163line32
 
  Dont we need the notification impl type here which can be used in Guice?

Will add


- Shwetha


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


On July 20, 2015, 6:14 a.m., Shwetha GS wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/36611/
 ---
 
 (Updated July 20, 2015, 6:14 a.m.)
 
 
 Review request for atlas.
 
 
 Bugs: ATLAS-74
 https://issues.apache.org/jira/browse/ATLAS-74
 
 
 Repository: atlas
 
 
 Description
 ---
 
 Add notification framework with kafka as default implementation
 
 
 Diffs
 -
 
   client/src/main/java/org/apache/atlas/PropertiesUtil.java bc56cbf 
   notification/pom.xml PRE-CREATION 
   notification/src/main/java/org/apache/atlas/kafka/KafkaConsumer.java 
 PRE-CREATION 
   notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
 PRE-CREATION 
   
 notification/src/main/java/org/apache/atlas/notification/ConsumerInterface.java
  PRE-CREATION 
   
 notification/src/main/java/org/apache/atlas/notification/NotificationException.java
  PRE-CREATION 
   
 

[jira] [Updated] (ATLAS-37) atlas repository, webapp, hive-bridge tests fails with Hbase and Solr as Titan storage backend

2015-07-21 Thread Suma Shivaprasad (JIRA)

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

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

 atlas repository, webapp, hive-bridge tests fails with Hbase and Solr as 
 Titan storage backend
 --

 Key: ATLAS-37
 URL: https://issues.apache.org/jira/browse/ATLAS-37
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.5.1-incubating
Reporter: Suma Shivaprasad
Assignee: Suma Shivaprasad
 Fix For: 0.5.1-incubating

 Attachments: ATLAS-37.patch


 {noformat}
 Running org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
 Tests run: 45, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 170.609 sec 
 - in org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
 Running org.apache.atlas.discovery.HiveLineageServiceTest
 Tests run: 45, Failures: 1, Errors: 0, Skipped: 44, Time elapsed: 533.15 sec 
  FAILURE! - in org.apache.atlas.discovery.HiveLineageServiceTest
 setUp(org.apache.atlas.discovery.HiveLineageServiceTest)  Time elapsed: 
 533.067 sec   FAILURE!
 java.lang.IllegalArgumentException: The type of given name is not a key: 
 View.inputTables
   at 
 com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.getOrCreatePropertyKey(StandardTitanTx.java:906)
   at 
 com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:239)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository.addProperty(GraphBackedMetadataRepository.java:870)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository.access$900(GraphBackedMetadataRepository.java:74)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository$TypedInstanceToGraphMapper.mapArrayCollectionToVertex(GraphBackedMetadataRepository.java:710)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository$TypedInstanceToGraphMapper.mapAttributesToVertex(GraphBackedMetadataRepository.java:660)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository$TypedInstanceToGraphMapper.mapInstanceToVertex(GraphBackedMetadataRepository.java:633)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository$TypedInstanceToGraphMapper.addDiscoveredInstances(GraphBackedMetadataRepository.java:607)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository$TypedInstanceToGraphMapper.mapTypedInstanceToGraph(GraphBackedMetadataRepository.java:446)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository$TypedInstanceToGraphMapper.access$100(GraphBackedMetadataRepository.java:432)
   at 
 org.apache.atlas.repository.graph.GraphBackedMetadataRepository.createEntity(GraphBackedMetadataRepository.java:148)
   at 
 org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:41)
   at 
 org.apache.atlas.services.DefaultMetadataService.createEntity(DefaultMetadataService.java:231)
   at 
 org.apache.atlas.discovery.HiveLineageServiceTest.createInstance(HiveLineageServiceTest.java:518)
   at 
 org.apache.atlas.discovery.HiveLineageServiceTest.view(HiveLineageServiceTest.java:509)
   at 
 org.apache.atlas.discovery.HiveLineageServiceTest.setupInstances(HiveLineageServiceTest.java:409)
   at 
 org.apache.atlas.discovery.HiveLineageServiceTest.setUp(HiveLineageServiceTest.java:75)
 Running org.apache.atlas.query.BaseGremlinTest
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.201 sec - 
 in org.apache.atlas.query.BaseGremlinTest
 Running org.apache.atlas.query.ExpressionTest
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.21 sec - in 
 org.apache.atlas.query.ExpressionTest
 Running org.apache.atlas.query.GremlinTest
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.235 sec - 
 in org.apache.atlas.query.GremlinTest
 Running org.apache.atlas.query.LexerTest
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.189 sec - 
 in org.apache.atlas.query.LexerTest
 Running org.apache.atlas.query.LineageQueryTest
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.216 sec - 
 in org.apache.atlas.query.LineageQueryTest
 Running org.apache.atlas.query.ParserTest
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.223 sec - 
 in org.apache.atlas.query.ParserTest
 Running org.apache.atlas.query.TestApp
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.207 sec - 
 in org.apache.atlas.query.TestApp
 Running org.apache.atlas.repository.BaseTest
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.194 sec - 
 in org.apache.atlas.repository.BaseTest
 Running org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryTest
 Tests 

[jira] [Commented] (ATLAS-45) Entity submit fails

2015-07-21 Thread Shwetha G S (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634648#comment-14634648
 ] 

Shwetha G S commented on ATLAS-45:
--

+1, will commit

 Entity submit fails
 ---

 Key: ATLAS-45
 URL: https://issues.apache.org/jira/browse/ATLAS-45
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.6-incubating
Reporter: Shwetha G S
Assignee: Suma Shivaprasad
 Fix For: 0.6-incubating

 Attachments: ATLAS-45.patch


 {noformat}
 2015-07-02 16:28:25,044 ERROR - [503025921@qtp-1044962984-8 - 
 e842c8ce-58ce-4b3f-a083-81dbbb9902b2:] ~ Unable to persist entity instance 
 due to a desrialization error  (EntityResource:109)
 org.apache.atlas.typesystem.types.ValueConversionException: Cannot convert 
 value 'org.apache.atlas.typesystem.Referenceable@7a50b790' to datatype 
 hive_storagedesc
   at 
 org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:143)
   at 
 org.apache.atlas.services.DefaultMetadataService.deserializeClassInstance(DefaultMetadataService.java:251)
   at 
 org.apache.atlas.services.DefaultMetadataService.createEntity(DefaultMetadataService.java:229)
   at 
 org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:96)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at 
 com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
   at 
 com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
   at 
 com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
   at 
 com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
   at 
 com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
   at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
   at 
 com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
   at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
   at 
 com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
   at 
 com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
   at 
 com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
   at 
 com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
   at 
 com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
   at 
 org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:67)
   at 
 com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
   at 
 com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
   at 
 com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
   at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
   at 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
   at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
   at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
   at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
   at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
   at 

[jira] [Updated] (ATLAS-74) Create notification framework

2015-07-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-74:
-
Attachment: ATLAS-74-v2.patch

 Create notification framework
 -

 Key: ATLAS-74
 URL: https://issues.apache.org/jira/browse/ATLAS-74
 Project: Atlas
  Issue Type: Sub-task
Reporter: Shwetha G S
Assignee: Shwetha G S
 Attachments: ATLAS-74-v2.patch, ATLAS-74.patch


 Add notification framework with kafka as default implementation



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