[jira] [Updated] (ATLAS-247) hive_column leve lineage

2016-02-23 Thread Shwetha G S (JIRA) 

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

Shwetha G S updated ATLAS-247:
--
Assignee: Harish Butani

> hive_column leve lineage
> 
>
> Key: ATLAS-247
> URL: https://issues.apache.org/jira/browse/ATLAS-247
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.5-incubating
>Reporter: Herman Yu
>Assignee: Harish Butani
>
> hive_column is not inherited from DataSet, thus can't be using hive_process 
> to track column level lineages
> Is there specific reason that hive_column is not inheriting from Data Set? 



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

[jira] [Commented] (ATLAS-476) Update type attribute with Reserved characters updated the original type as unknown

2016-02-23 Thread Hemanth Yamijala (JIRA) 

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

Hemanth Yamijala commented on ATLAS-476:


I have attached a patch on review board requesting review.

[~shwethags], I followed the first approach. However, I did not use the 
TransientTypeSystem as you have suggested. There are calls that already rely on 
the returned Map of newly added types from {{TypeSystem.defineTypes}} and 
{{TypeSystem.updateTypes}}. Rather than change those methods, I instead 
extended the same logic to {{TypeStore.store}}.

Since I was added overloaded methods, I tried to cleanup ones that were being 
used only in tests etc, particularly in {{TypeStore.store}}.

Let's take the review on the review board and continue discussion there. Thanks.

> Update type attribute with Reserved characters updated the original type as 
> unknown
> ---
>
> Key: ATLAS-476
> URL: https://issues.apache.org/jira/browse/ATLAS-476
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: sandbox
>Reporter: Chethana
>Assignee: Hemanth Yamijala
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: 1.log
>
>
> create a type with required attribute
> try to get this type created - the type data is returned
> try update this type by adding attribute with attribute name consisting of a 
> reserved character eg:test$
> this throws exception.
> Now use to get call to get the previously created type
> Expected:
> The type should not be updated.
> Actual:
> "error": "Unknown datatype: className_update_vsvrbzqaqg",
> "stackTrace": "org.apache.atlas.typesystem.exception.TypeNotFoundException: 
> Unknown datatype: className_update_vsvrbzqaqg\n\tat 



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

[jira] [Commented] (ATLAS-508) Apache nightly build failure - UnsupportedOperationException: Not a single key: __traitNames

2016-02-23 Thread Shwetha G S (JIRA) 

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

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

I haven't made any changes to fix the issue. Even originally, the build always 
worked on our dev environment. It was failing only in the jenkins job, so must 
be some environment issue. I  haven't looked at it further

> Apache nightly build failure - UnsupportedOperationException: Not a single 
> key: __traitNames
> 
>
> Key: ATLAS-508
> URL: https://issues.apache.org/jira/browse/ATLAS-508
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: David Kantor
>Priority: Critical
>
> https://builds.apache.org/job/apache-atlas-nightly/184/console
> {noformat}
> Failed tests: 
>   GremlinTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang.Unsu...
>   LineageQueryTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang...
> Tests run: 200, Failures: 2, Errors: 0, Skipped: 28
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] apache-atlas .. SUCCESS [ 21.262 s]
> [INFO] Apache Atlas Common ... SUCCESS [ 58.381 s]
> [INFO] Apache Atlas Typesystem ... SUCCESS [04:51 min]
> [INFO] Apache Atlas Server API ... SUCCESS [ 37.922 s]
> [INFO] Apache Atlas Client ... SUCCESS [01:12 min]
> [INFO] Apache Atlas Notification . SUCCESS [01:25 min]
> [INFO] Apache Atlas Titan  SUCCESS [01:56 min]
> [INFO] Apache Atlas Repository ... FAILURE [10:51 min]
> [INFO] Apache Atlas UI ... SKIPPED
> [INFO] Apache Atlas Web Application .. SKIPPED
> [INFO] Apache Atlas Documentation  SKIPPED
> [INFO] Apache Atlas Hive Bridge .. SKIPPED
> [INFO] Apache Atlas Falcon Bridge  SKIPPED
> [INFO] Apache Atlas Sqoop Bridge . SKIPPED
> [INFO] Apache Atlas Storm Bridge . SKIPPED
> [INFO] Apache Atlas Distribution . SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> Running org.apache.atlas.query.LineageQueryTest
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 16.236 sec 
> <<< FAILURE! - in org.apache.atlas.query.LineageQueryTest
> beforeAll(org.apache.atlas.query.LineageQueryTest)  Time elapsed: 16.159 sec  
> <<< FAILURE!
> javax.script.ScriptException: javax.script.ScriptException: 
> java.lang.UnsupportedOperationException: Not a single key: __traitNames. Use 
> addProperty instead
>   at 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.setProperty(StandardTitanTx.java:755)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:244)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:239)
>   at 
> com.tinkerpop.blueprints.util.wrappers.batch.BatchGraph$BatchVertex.setProperty(BatchGraph.java:492)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONUtility.vertexFromJson(GraphSONUtility.java:136)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:158)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:104)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:88)
>   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 
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
>   at

[jira] [Commented] (ATLAS-508) Apache nightly build failure - UnsupportedOperationException: Not a single key: __traitNames

2016-02-23 Thread Naima Djouhri (JIRA) 

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

Naima Djouhri commented on ATLAS-508:
-

[~shwethags] I am having this issue with Atlas release 06 that I downloaded 
from  http://www.apache.org/dyn/closer.cgi/incubator/atlas/0.6.0-incubating/
and installed on a Hadoop cluster
is there any setting that you turned on to make the build pass after the issue? 
or anything else that resolved the issue?
Thanks

> Apache nightly build failure - UnsupportedOperationException: Not a single 
> key: __traitNames
> 
>
> Key: ATLAS-508
> URL: https://issues.apache.org/jira/browse/ATLAS-508
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: David Kantor
>Priority: Critical
>
> https://builds.apache.org/job/apache-atlas-nightly/184/console
> {noformat}
> Failed tests: 
>   GremlinTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang.Unsu...
>   LineageQueryTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang...
> Tests run: 200, Failures: 2, Errors: 0, Skipped: 28
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] apache-atlas .. SUCCESS [ 21.262 s]
> [INFO] Apache Atlas Common ... SUCCESS [ 58.381 s]
> [INFO] Apache Atlas Typesystem ... SUCCESS [04:51 min]
> [INFO] Apache Atlas Server API ... SUCCESS [ 37.922 s]
> [INFO] Apache Atlas Client ... SUCCESS [01:12 min]
> [INFO] Apache Atlas Notification . SUCCESS [01:25 min]
> [INFO] Apache Atlas Titan  SUCCESS [01:56 min]
> [INFO] Apache Atlas Repository ... FAILURE [10:51 min]
> [INFO] Apache Atlas UI ... SKIPPED
> [INFO] Apache Atlas Web Application .. SKIPPED
> [INFO] Apache Atlas Documentation  SKIPPED
> [INFO] Apache Atlas Hive Bridge .. SKIPPED
> [INFO] Apache Atlas Falcon Bridge  SKIPPED
> [INFO] Apache Atlas Sqoop Bridge . SKIPPED
> [INFO] Apache Atlas Storm Bridge . SKIPPED
> [INFO] Apache Atlas Distribution . SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> Running org.apache.atlas.query.LineageQueryTest
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 16.236 sec 
> <<< FAILURE! - in org.apache.atlas.query.LineageQueryTest
> beforeAll(org.apache.atlas.query.LineageQueryTest)  Time elapsed: 16.159 sec  
> <<< FAILURE!
> javax.script.ScriptException: javax.script.ScriptException: 
> java.lang.UnsupportedOperationException: Not a single key: __traitNames. Use 
> addProperty instead
>   at 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.setProperty(StandardTitanTx.java:755)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:244)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:239)
>   at 
> com.tinkerpop.blueprints.util.wrappers.batch.BatchGraph$BatchVertex.setProperty(BatchGraph.java:492)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONUtility.vertexFromJson(GraphSONUtility.java:136)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:158)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:104)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:88)
>   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 
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>

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

2016-02-23 Thread Apache Jenkins Server 
See 

--
Started by user sneethir
[EnvInject] - Loading node environment variables.
Building remotely on H3 (Mapreduce Hadoop Zookeeper Hdfs yahoo-not-h2) in 
workspace 
Cloning the remote Git repository
Cloning repository http://git-wip-us.apache.org/repos/asf/incubator-atlas.git
 > git init  # 
 > timeout=10
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:655)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
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 ..remote call to H3(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:778)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor533.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy83.execute(Unknown Source)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1013)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1053)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1274)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:381)
Caused by: hudson.plugins.git.GitException: Error performing command: git init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1700)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1669)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1665)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1307)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:653)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
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)
Caused by: java.io.IOException: Cannot run program "git" (in directory 
": error=11, Resource 
temporarily unavailable
at java.lang.ProcessBuilder.start

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

2016-02-23 Thread Apache Jenkins Server 
See 

--
Started by user sneethir
[EnvInject] - Loading node environment variables.
Building remotely on H3 (Mapreduce Hadoop Zookeeper Hdfs yahoo-not-h2) in 
workspace 
Cloning the remote Git repository
Cloning repository http://git-wip-us.apache.org/repos/asf/incubator-atlas.git
 > git init  # 
 > timeout=10
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:655)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
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 ..remote call to H3(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:778)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor533.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy83.execute(Unknown Source)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1013)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1053)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1274)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:381)
Caused by: hudson.plugins.git.GitException: Error performing command: git init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1700)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1669)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1665)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1307)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:653)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
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)
Caused by: java.io.IOException: Cannot run program "git" (in directory 
": error=11, Resource 
temporarily unavailable
at java.lang.ProcessBuilder.start

[jira] [Resolved] (ATLAS-508) Apache nightly build failure - UnsupportedOperationException: Not a single key: __traitNames

2016-02-23 Thread David Kantor (JIRA) 

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

David Kantor resolved ATLAS-508.

Resolution: Cannot Reproduce

This test has passed in the last two nightly builds and I cannot reproduce the 
failure.

> Apache nightly build failure - UnsupportedOperationException: Not a single 
> key: __traitNames
> 
>
> Key: ATLAS-508
> URL: https://issues.apache.org/jira/browse/ATLAS-508
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: David Kantor
>Priority: Critical
>
> https://builds.apache.org/job/apache-atlas-nightly/184/console
> {noformat}
> Failed tests: 
>   GremlinTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang.Unsu...
>   LineageQueryTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang...
> Tests run: 200, Failures: 2, Errors: 0, Skipped: 28
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] apache-atlas .. SUCCESS [ 21.262 s]
> [INFO] Apache Atlas Common ... SUCCESS [ 58.381 s]
> [INFO] Apache Atlas Typesystem ... SUCCESS [04:51 min]
> [INFO] Apache Atlas Server API ... SUCCESS [ 37.922 s]
> [INFO] Apache Atlas Client ... SUCCESS [01:12 min]
> [INFO] Apache Atlas Notification . SUCCESS [01:25 min]
> [INFO] Apache Atlas Titan  SUCCESS [01:56 min]
> [INFO] Apache Atlas Repository ... FAILURE [10:51 min]
> [INFO] Apache Atlas UI ... SKIPPED
> [INFO] Apache Atlas Web Application .. SKIPPED
> [INFO] Apache Atlas Documentation  SKIPPED
> [INFO] Apache Atlas Hive Bridge .. SKIPPED
> [INFO] Apache Atlas Falcon Bridge  SKIPPED
> [INFO] Apache Atlas Sqoop Bridge . SKIPPED
> [INFO] Apache Atlas Storm Bridge . SKIPPED
> [INFO] Apache Atlas Distribution . SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> Running org.apache.atlas.query.LineageQueryTest
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 16.236 sec 
> <<< FAILURE! - in org.apache.atlas.query.LineageQueryTest
> beforeAll(org.apache.atlas.query.LineageQueryTest)  Time elapsed: 16.159 sec  
> <<< FAILURE!
> javax.script.ScriptException: javax.script.ScriptException: 
> java.lang.UnsupportedOperationException: Not a single key: __traitNames. Use 
> addProperty instead
>   at 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.setProperty(StandardTitanTx.java:755)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:244)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:239)
>   at 
> com.tinkerpop.blueprints.util.wrappers.batch.BatchGraph$BatchVertex.setProperty(BatchGraph.java:492)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONUtility.vertexFromJson(GraphSONUtility.java:136)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:158)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:104)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:88)
>   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 
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
>   at 
> com.tinkerpop.gremlin.groovy.loaders.GraphLoad

Re: Integration tests failing for Atlas release 06 on a Hadoop cluster

2016-02-23 Thread Dave Kantor 

Hi Naima,

I've assigned ATLAS-508 to myself and started debugging it, I will keep you
posted.

-Dave.

David Kantor
IBM Software Group
Phone: 978-899-2072 (T/L: 276-2072)
Email: dkan...@us.ibm.com



From:   Naima Djouhri/Boston/IBM@IBMUS
To: dev@atlas.incubator.apache.org
Date:   02/23/2016 03:51 PM
Subject:Integration tests failing for Atlas release 06 on a Hadoop
cluster



Hi,
I downloaded Atlas release 06 from the Apache site
http://www.apache.org/dyn/closer.cgi/incubator/atlas/0.6.0-incubating/
and tried to build and deploy on a Hadoop cluster.
It did install and deploy Atlas on each node of the cluster with no issue
but got the following errors when running the integration tests

Tests run: 23, Failures: 1, Errors: 0, Skipped: 22, Time elapsed: 7.474
sec <<< FAILURE! - in org.apache.atlas.query.GremlinTest
beforeAll(org.apache.atlas.query.GremlinTest)  Time elapsed: 7.395 sec <<<
FAILURE!
javax.script.ScriptException: javax.script.ScriptException:
java.lang.UnsupportedOperationException: Not a single key: __traitNames.
Use addProperty instead
at
com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.setProperty
(StandardTitanTx.java:755)
at
com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty
(AbstractVertex.java:244)
at
com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty
(AbstractVertex.java:239)
at
com.tinkerpop.blueprints.util.wrappers.batch.BatchGraph
$BatchVertex.setProperty(BatchGraph.java:492)
at
com.tinkerpop.blueprints.util.io.graphson.GraphSONUtility.vertexFromJson
(GraphSONUtility.java:136)
at
com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph
(GraphSONReader.java:158)
at
com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph
(GraphSONReader.java:104)
at
com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph
(GraphSONReader.java:88)
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
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)

which is an UnsupportedOperationException that was reported on
https://issues.apache.org/jira/browse/ATLAS-508

Does anyone have an idea what is causing this error?

Thanks
Naima Djouhri

[jira] [Assigned] (ATLAS-508) Apache nightly build failure - UnsupportedOperationException: Not a single key: __traitNames

2016-02-23 Thread David Kantor (JIRA) 

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

David Kantor reassigned ATLAS-508:
--

Assignee: David Kantor

> Apache nightly build failure - UnsupportedOperationException: Not a single 
> key: __traitNames
> 
>
> Key: ATLAS-508
> URL: https://issues.apache.org/jira/browse/ATLAS-508
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: David Kantor
>Priority: Critical
>
> https://builds.apache.org/job/apache-atlas-nightly/184/console
> {noformat}
> Failed tests: 
>   GremlinTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang.Unsu...
>   LineageQueryTest.beforeAll:41 » Script javax.script.ScriptException: 
> java.lang...
> Tests run: 200, Failures: 2, Errors: 0, Skipped: 28
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] apache-atlas .. SUCCESS [ 21.262 s]
> [INFO] Apache Atlas Common ... SUCCESS [ 58.381 s]
> [INFO] Apache Atlas Typesystem ... SUCCESS [04:51 min]
> [INFO] Apache Atlas Server API ... SUCCESS [ 37.922 s]
> [INFO] Apache Atlas Client ... SUCCESS [01:12 min]
> [INFO] Apache Atlas Notification . SUCCESS [01:25 min]
> [INFO] Apache Atlas Titan  SUCCESS [01:56 min]
> [INFO] Apache Atlas Repository ... FAILURE [10:51 min]
> [INFO] Apache Atlas UI ... SKIPPED
> [INFO] Apache Atlas Web Application .. SKIPPED
> [INFO] Apache Atlas Documentation  SKIPPED
> [INFO] Apache Atlas Hive Bridge .. SKIPPED
> [INFO] Apache Atlas Falcon Bridge  SKIPPED
> [INFO] Apache Atlas Sqoop Bridge . SKIPPED
> [INFO] Apache Atlas Storm Bridge . SKIPPED
> [INFO] Apache Atlas Distribution . SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> Running org.apache.atlas.query.LineageQueryTest
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 16.236 sec 
> <<< FAILURE! - in org.apache.atlas.query.LineageQueryTest
> beforeAll(org.apache.atlas.query.LineageQueryTest)  Time elapsed: 16.159 sec  
> <<< FAILURE!
> javax.script.ScriptException: javax.script.ScriptException: 
> java.lang.UnsupportedOperationException: Not a single key: __traitNames. Use 
> addProperty instead
>   at 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.setProperty(StandardTitanTx.java:755)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:244)
>   at 
> com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:239)
>   at 
> com.tinkerpop.blueprints.util.wrappers.batch.BatchGraph$BatchVertex.setProperty(BatchGraph.java:492)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONUtility.vertexFromJson(GraphSONUtility.java:136)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:158)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:104)
>   at 
> com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:88)
>   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 
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)
>   at 
> org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
>   at 
> com.tinkerpop.gremlin.groovy.loaders.GraphLoader$_load_closure14.doCall(GraphLoader.groovy:126)
>   at sun.reflect.NativeMethodAccess

Integration tests failing for Atlas release 06 on a Hadoop cluster

2016-02-23 Thread Naima Djouhri 
Hi,
I downloaded Atlas release 06 from the Apache site 
http://www.apache.org/dyn/closer.cgi/incubator/atlas/0.6.0-incubating/ 
and tried to build and deploy on a Hadoop cluster.
It did install and deploy Atlas on each node of the cluster with no issue 
but got the following errors when running the integration tests

Tests run: 23, Failures: 1, Errors: 0, Skipped: 22, Time elapsed: 7.474 
sec <<< FAILURE! - in org.apache.atlas.query.GremlinTest
beforeAll(org.apache.atlas.query.GremlinTest)  Time elapsed: 7.395 sec <<< 
FAILURE!
javax.script.ScriptException: javax.script.ScriptException: 
java.lang.UnsupportedOperationException: Not a single key: __traitNames. 
Use addProperty instead
at 
com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.setProperty(StandardTitanTx.java:755)
at 
com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:244)
at 
com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.setProperty(AbstractVertex.java:239)
at 
com.tinkerpop.blueprints.util.wrappers.batch.BatchGraph$BatchVertex.setProperty(BatchGraph.java:492)
at 
com.tinkerpop.blueprints.util.io.graphson.GraphSONUtility.vertexFromJson(GraphSONUtility.java:136)
at 
com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:158)
at 
com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:104)
at 
com.tinkerpop.blueprints.util.io.graphson.GraphSONReader.inputGraph(GraphSONReader.java:88)
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 
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)

which is an UnsupportedOperationException that was reported on 
https://issues.apache.org/jira/browse/ATLAS-508

Does anyone have an idea what is causing this error?

Thanks 
Naima Djouhri

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

2016-02-23 Thread Apache Jenkins Server 
See 

Changes:

[sshivalingamurthy] ATLAS-483 Remove client.properties (tbeerbower via 
shwethags)

--
[...truncated 6450 lines...]
[INFO] Class 
org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1 
defines non-transient non-serializable instance field aInfo$1 
[org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1]
 In GraphPersistenceStrategies.scala
[INFO] Class 
org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1 
defines non-transient non-serializable instance field arrayType$1 
[org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1]
 In GraphPersistenceStrategies.scala
[INFO] Class 
org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1 
defines non-transient non-serializable instance field i$1 
[org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1]
 In GraphPersistenceStrategies.scala
[INFO] Class 
org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1 
defines non-transient non-serializable instance field v$3 
[org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadArrayAttribute$1]
 In GraphPersistenceStrategies.scala
[INFO] Class 
org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadStructInstance$1 
defines non-transient non-serializable instance field dataType$1 
[org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadStructInstance$1]
 In GraphPersistenceStrategies.scala
[INFO] Class 
org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadStructInstance$1 
defines non-transient non-serializable instance field typInstance$1 
[org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadStructInstance$1]
 In GraphPersistenceStrategies.scala
[INFO] Class 
org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadStructInstance$1 
defines non-transient non-serializable instance field v$1 
[org.apache.atlas.query.GraphPersistenceStrategy1$$anonfun$loadStructInstance$1]
 In GraphPersistenceStrategies.scala
[INFO] Class org.apache.atlas.query.GremlinEvaluator$$anonfun$1 defines 
non-transient non-serializable instance field $outer 
[org.apache.atlas.query.GremlinEvaluator$$anonfun$1] In GremlinEvaluator.scala
[INFO] Class org.apache.atlas.query.GremlinEvaluator$$anonfun$2 defines 
non-transient non-serializable instance field $outer 
[org.apache.atlas.query.GremlinEvaluator$$anonfun$2] In GremlinEvaluator.scala
[INFO] Class org.apache.atlas.query.GremlinEvaluator$$anonfun$2 defines 
non-transient non-serializable instance field oType$1 
[org.apache.atlas.query.GremlinEvaluator$$anonfun$2] In GremlinEvaluator.scala
[INFO] Class org.apache.atlas.query.GremlinEvaluator$$anonfun$3 defines 
non-transient non-serializable instance field $outer 
[org.apache.atlas.query.GremlinEvaluator$$anonfun$3] In GremlinEvaluator.scala
[INFO] Class org.apache.atlas.query.GremlinEvaluator$$anonfun$3 defines 
non-transient non-serializable instance field sType$1 
[org.apache.atlas.query.GremlinEvaluator$$anonfun$3] In GremlinEvaluator.scala
[INFO] Class 
org.apache.atlas.query.GremlinEvaluator$$anonfun$3$$anonfun$apply$1 defines 
non-transient non-serializable instance field sInstance$1 
[org.apache.atlas.query.GremlinEvaluator$$anonfun$3$$anonfun$apply$1] In 
GremlinEvaluator.scala
[INFO] Class 
org.apache.atlas.query.GremlinTranslator$$anonfun$addAliasToLoopInput$1 defines 
non-transient non-serializable instance field c$1 
[org.apache.atlas.query.GremlinTranslator$$anonfun$addAliasToLoopInput$1] In 
GremlinQuery.scala
[INFO] Class 
org.apache.atlas.query.GremlinTranslator$$anonfun$org$apache$atlas$query$GremlinTranslator$$genQuery$1
 defines non-transient non-serializable instance field $outer 
[org.apache.atlas.query.GremlinTranslator$$anonfun$org$apache$atlas$query$GremlinTranslator$$genQuery$1]
 In GremlinQuery.scala
[INFO] Class 
org.apache.atlas.query.GremlinTranslator$$anonfun$org$apache$atlas$query$GremlinTranslator$$genQuery$2
 defines non-transient non-serializable instance field $outer 
[org.apache.atlas.query.GremlinTranslator$$anonfun$org$apache$atlas$query$GremlinTranslator$$genQuery$2]
 In GremlinQuery.scala
[INFO] The method name org.apache.atlas.query.HiveLineageQuery.Relation() 
doesn't start with a lower case letter 
[org.apache.atlas.query.HiveLineageQuery] At ClosureQuery.scala:[line 259]
[INFO] The method name 
org.apache.atlas.query.HiveLineageQuery.ReverseRelation() doesn't start with a 
lower case letter [org.apache.atlas.query.HiveLineageQuery] At 
ClosureQuery.scala:[line 259]
[INFO] Class org.apache.atlas.query.HiveLineageQuery defines non-transient 
non-serializable instance field attributeTyp 
[org.apache.atlas.query.HiveLineageQuery] In ClosureQuery.scala
[INFO] The method name org.apache.atlas.query.HiveWhereUsedQuery.Relation() 
doesn't start with a lower case letter 
[org.apa

[jira] [Commented] (ATLAS-479) Add description for different types during create time

2016-02-23 Thread Neeru Gupta (JIRA) 

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

Neeru Gupta commented on ATLAS-479:
---

TestSerialization tests run successfully on my environment. Is there any 
specific way to reproduce the test failures?

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531.patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



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

Re: Atlas dev environment setup

2016-02-23 Thread Hemanth Yamijala 
Venkat,

Would be nice to document these on the Atlas wiki I think? Would get
indexed better probably.

Thanks
Hemanth
On 23-Feb-2016 18:37, "Venkata R Madugundu" 
wrote:

> Thanks Neeru.
>
> Here is what I did. (May be it is useful to others)
>
> 1. Pulled atlas source from Git.
>
> 2. Installed Scala IDE 4.3.0 from http://scala-ide.org/download/sdk.html
>
> 3. Imported atlas projects as Maven projects in Eclipse
>
> 4. Added the scala folders in 'typesystem' and 'repository' projects as
> 'Source folders'
> Right click the scala folder -> Build Path -> Use as Source Folder
>
> 5. Changed the Scala Compiler Settings for 'typesystem' and 'repository'
> projects to use Scala 2.10
> Right click project -> Scala Compiler -> Use Project Settings ... select
> 'Fixed Scala installation 2.10.5'
>
> 6. Pretty much every project is green except for 'atlas-webapp' where
> there is an error flagged in pom.
> "Plugin execution not covered by lifecycle configuration:
> org.codehaus.mojo:keytool-maven-plugin:1.5:clean (execution: clean, phase:
> generate-resources) pom.xml"
> I think that keytool plugin probably needs some kind of integration with
> m2eclipse.
> I am OK to live with this red flag.
>
> NOTE:
> - I have excluded projects in atlas/addons to begin with.
> - Used Java8 and Maven 3.3.3
>
> Thanks
> Venkat
>
>
> [image: Inactive hide details for "Fnu Neerju" ---22/02/2016 09:06:18
> PM---Hi Venkat, I had the same issue. I had to select scala folde]"Fnu
> Neerju" ---22/02/2016 09:06:18 PM---Hi Venkat, I had the same issue. I had
> to select scala folders and add those on
>
> From: "Fnu Neerju" 
> To: dev@atlas.incubator.apache.org
> Date: 22/02/16 09:06 PM
> Subject: Re: Atlas dev environment setup
> --
>
>
>
> Hi Venkat,
>
> I had the same issue. I had to select scala folders and add those on
> classpath manually. I did it for typesystem and repository projects for
> atlas. Please choose scala for both main code and test code. PFA the SS.
>
> -Neeru*(See attached file: ScalainPath.png)*
>
> [image: Inactive hide details for "Venkata R Madugundu" ---02/22/2016
> 10:01:22 AM---Is there an Atlas page for the people who want to c]"Venkata
> R Madugundu" ---02/22/2016 10:01:22 AM---Is there an Atlas page for the
> people who want to contribute, to setup a development environment wit
>
> From: "Venkata R Madugundu" 
> To: dev@atlas.incubator.apache.org
> Date: 02/22/2016 10:01 AM
> Subject: Atlas dev environment setup
> --
>
>
>
>
>
> Is there an Atlas page for the people who want to contribute, to setup a
> development environment with Eclipse as IDE ?
> I am trying to set it up, but one specific issue which keeps me bothering
> is "the Scala sources do not get recognized inside Eclipse as source
> folders.
> I searched a bit on the web and found out that the scala-maven-plugin needs
> to be configured specifically to let maven eclipse plugin add the Scala
> source folders as Eclipse source folders. Something like described in
>
> *http://stackoverflow.com/questions/23794398/eclipse-doesnt-recognize-scala-source-directory*
> 
>
> But I would prefer to get some advice from already contributing folks on
> what is your routine procedure to setup Atlas dev env with Eclipse IDE.
>
> Thanks
> Venkat
>
>
>
>

Re: Atlas dev environment setup

2016-02-23 Thread Venkata R Madugundu 

Thanks Neeru.

Here is what I did. (May be it is useful to others)

1. Pulled atlas source from Git.

2. Installed Scala IDE 4.3.0 from http://scala-ide.org/download/sdk.html

3. Imported atlas projects as Maven projects in Eclipse

4. Added the scala folders in 'typesystem' and 'repository' projects as
'Source folders'
Right click the scala folder -> Build Path -> Use as Source Folder

5. Changed the Scala Compiler Settings for 'typesystem' and 'repository'
projects to use Scala 2.10
Right click project -> Scala Compiler -> Use Project Settings ... select
'Fixed Scala installation 2.10.5'

6. Pretty much every project is green except for 'atlas-webapp' where there
is an error flagged in pom.
"Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:keytool-maven-plugin:1.5:clean (execution: clean, phase:
generate-resources) pom.xml"
I think that keytool plugin probably needs some kind of integration with
m2eclipse.
I am OK to live with this red flag.

NOTE:
- I have excluded projects in atlas/addons to begin with.
- Used Java8 and Maven 3.3.3

Thanks
Venkat




From:   "Fnu Neerju" 
To: dev@atlas.incubator.apache.org
Date:   22/02/16 09:06 PM
Subject:Re: Atlas dev environment setup



Hi Venkat,

I had the same issue. I had to select scala folders and add those on
classpath manually. I did it for typesystem and repository projects for
atlas. Please choose scala for both main code and test code. PFA the SS.

-Neeru(See attached file: ScalainPath.png)

Inactive hide details for "Venkata R Madugundu" ---02/22/2016 10:01:22
AM---Is there an Atlas page for the people who want to c"Venkata R
Madugundu" ---02/22/2016 10:01:22 AM---Is there an Atlas page for the
people who want to contribute, to setup a development environment wit

From: "Venkata R Madugundu" 
To: dev@atlas.incubator.apache.org
Date: 02/22/2016 10:01 AM
Subject: Atlas dev environment setup





Is there an Atlas page for the people who want to contribute, to setup a
development environment with Eclipse as IDE ?
I am trying to set it up, but one specific issue which keeps me bothering
is "the Scala sources do not get recognized inside Eclipse as source
folders.
I searched a bit on the web and found out that the scala-maven-plugin needs
to be configured specifically to let maven eclipse plugin add the Scala
source folders as Eclipse source folders. Something like described in
http://stackoverflow.com/questions/23794398/eclipse-doesnt-recognize-scala-source-directory


But I would prefer to get some advice from already contributing folks on
what is your routine procedure to setup Atlas dev env with Eclipse IDE.

Thanks
Venkat

[jira] [Created] (ATLAS-512) Decouple currently integrating components from availability of Atlas service for raising metadata events

2016-02-23 Thread Hemanth Yamijala (JIRA) 
Hemanth Yamijala created ATLAS-512:
--

 Summary: Decouple currently integrating components  from 
availability of Atlas service for raising metadata events
 Key: ATLAS-512
 URL: https://issues.apache.org/jira/browse/ATLAS-512
 Project: Atlas
  Issue Type: Sub-task
Reporter: Hemanth Yamijala


The components that currently integrate with Atlas (Hive, Sqoop, Falcon, Storm) 
all communicate their metadata events using Kafka as a messaging layer. This 
effectively decouples these components from the Atlas server. 

However, all of these components have some initialization that checks if their 
respective models are registered with Atlas. For components that integrate on 
the server, like HiveServer2 and Falcon, this initialization is a one time 
check and hence, is manageable. Others like Sqoop, Storm and the Hive CLI are 
client side components and hence the initialization happens for every run or 
session of these components. Invoking the initialization (and the one time 
check) every time like this effectively means that the Atlas server should be 
always available.

This JIRA is to try and remove this dependency and thus truly decouple these 
components.



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

[jira] [Created] (ATLAS-511) Ability to run multiple instances of Atlas Server with automatic failover to one active server

2016-02-23 Thread Hemanth Yamijala (JIRA) 
Hemanth Yamijala created ATLAS-511:
--

 Summary: Ability to run multiple instances of Atlas Server with 
automatic failover to one active server
 Key: ATLAS-511
 URL: https://issues.apache.org/jira/browse/ATLAS-511
 Project: Atlas
  Issue Type: Sub-task
Reporter: Hemanth Yamijala


One of the most important components that only supports active-standby mode 
currently is the Atlas server which hosts the API / UI for Atlas. As described 
in the [HA 
Documentation|http://atlas.incubator.apache.org/0.6.0-incubating/HighAvailability.html],
 we currently are limited to running only one instance of the Atlas server 
behind a proxy service. If the running instance goes down, a manual process is 
required to bring up another instance.

In this JIRA, we propose to have an ability to run multiple Atlas server 
instances. However, as a first step, only one of them will be actively 
processing requests. To have a consistent terminology, let us call that server 
the *master*. Any requests sent to the other servers will be redirected to the 
master.

When the master suffers a partition, one of the other servers must 
automatically become the master and start processing requests. What this mode 
brings us over the current system is the ability to automatically failover the 
Atlas server instance without any  manual intervention. Note that this can be 
arguably called an [active/active 
setup|https://en.wikipedia.org/wiki/High-availability_cluster]

ATLAS-488 raised to support multiple active Atlas server instances. While that 
would be ideal, we have to learn more about the underlying system behavior 
before we can get there, and hopefully we can take smaller steps to improve the 
system systematically. The method proposed here is similar to what is adopted 
in many other Hadoop components including HDFS NameNode, HBase HMaster etc.



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

[jira] [Commented] (ATLAS-328) UI: Swagger API Documentation support

2016-02-23 Thread venkata madugundu (JIRA) 

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

venkata madugundu commented on ATLAS-328:
-

The Atlas REST API documentation is outdated and does not reflect the current 
state of Atlas REST interface. It is quite misleading to adopters of Atlas, as 
they would need to dig into the Atlas source code to figure out the correct 
REST interface.

Swagger can generate the Atlas REST API documentation as they are compliant 
with JAX-RS specification. As a side effect, Swagger can also generate client 
code for the REST API in multiple languages, which is useful for error free 
invocation of Atlas REST API (but that is a different topic).

Sample Swagger doc for a PetStore REST service is here - 
http://petstore.swagger.io/

> UI: Swagger API Documentation support
> -
>
> Key: ATLAS-328
> URL: https://issues.apache.org/jira/browse/ATLAS-328
> Project: Atlas
>  Issue Type: Task
>Reporter: roshni gadiyar
>Priority: Minor
>  Labels: Atlas-UI
>
> Swagger API Documentation support.
> https://github.com/swagger-api/swagger-samples/tree/master/java/java-jersey2-guice



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