[jira] [Commented] (ATLAS-117) Build fails on the latest commit 48343db999...
[
https://issues.apache.org/jira/browse/ATLAS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730422#comment-14730422
]
David Kaspar commented on ATLAS-117:
I have verified the ATLAS-117-2.patch on my machine and it fixes the issue.
> Build fails on the latest commit 48343db999...
> --
>
> Key: ATLAS-117
> URL: https://issues.apache.org/jira/browse/ATLAS-117
> Project: Atlas
> Issue Type: Bug
>Reporter: David Kaspar
>Assignee: Tom Beerbower
> Attachments: ATLAS-117-2.patch, ATLAS-117.patch
>
>
> Build fails when building the latest commit
> 48343db999b495458409644c8b9d2fd0bd9fa99d:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.atlas:atlas-webapp:war:0.6-incubating-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for
> org.codehaus.mojo:keytool-maven-plugin is missing. @
> org.apache.atlas:atlas-webapp:[unknown-version],
> /Users/MYSELF/Projects/External/incubator-atlas/webapp/pom.xml, line 309,
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] apache-atlas
> [INFO] Apache Atlas Typesystem
> [INFO] Apache Atlas Client
> [INFO] Apache Atlas Notification
> [INFO] Apache Atlas Repository
> [INFO] Apache Atlas Web Application
> [INFO] Apache Atlas Documentation
> [INFO] Apache Atlas Hive Bridge
> [INFO]
>
> [INFO]
>
> [INFO] Building apache-atlas 0.6-incubating-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ apache-atlas ---
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas/target
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas (includes =
> [**/*.pyc], excludes = [])
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.0:create (default) @ apache-atlas ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [WARNING] Cannot get the revision information from the scm repository,
> proceeding with revision of release :
> No such provider: 'https'.
> [INFO] Storing buildNumber: release at timestamp: 1440071695692
> [WARNING] Cannot get the branch information from the scm repository,
> proceeding with UNKNOWN_BRANCH :
> No such provider: 'https'.
> [INFO] Storing buildScmBranch: UNKNOWN_BRANCH
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ apache-atlas
> ---
> [INFO]
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> apache-atlas ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @
> apache-atlas ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- exec-maven-plugin:1.2.1:exec (python-test) @ apache-atlas ---
> test_jar_java_lookups_fail (TestMetadata.TestMetadata) ... ok
> test_jar_java_lookups_succeed_from_path (TestMetadata.TestMetadata) ... ok
> test_main (TestMetadata.TestMetadata) ... Apache Atlas Server started!!!
> ok
> --
> Ran 3 tests in 0.003s
> OK
> [INFO]
> [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @
> apache-atlas ---
> [INFO]
> [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ apache-atlas ---
> [INFO] Reading assembly descriptor: src/main/assemblies/standalone-package.xml
> [INFO] Reading assembly descriptor: src/main/assemblies/src-package.xml
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] apache-atlas ... FAILURE [ 1.773
> s]
> [INFO] Apache Atlas Typesystem SKIPPED
> [INFO] Apache Atlas Client SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] Apache Atlas Repository SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [
[jira] [Commented] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[
https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730530#comment-14730530
]
Suma Shivaprasad commented on ATLAS-136:
[~vantonevich] Can you pls upload the patch to reviewboard for review -
https://reviews.apache.org/dashboard/?group=atlas
> Add trait API to org.apache.atlas.AtlasClient
> -
>
> Key: ATLAS-136
> URL: https://issues.apache.org/jira/browse/ATLAS-136
> Project: Atlas
> Issue Type: Improvement
>Reporter: Vladimir Antonevich`
> Attachments: atlas.client.patch
>
>
> API to manipulate entity traits must be added to
> org.apache.atlas.AtlasClient. These should include methods to add/remove a
> trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as
> supported by exposed entities resource
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Titan: configuration in atlas
Hi Nigel, You should be able to point to the graph created in ATLAS through Rexster by following the steps at http://s3.thinkaurelius.com/docs/titan/current/server.html#_downloading_rexster_and_titan_separately. I was able to get the Rexster instance up this way but got some issue while loading the vertices though the edges are seen. Need to dig into this further. Thanks Suma On Thu, Sep 3, 2015 at 8:47 PM, Nigel Jones wrote: > > > I'm trying to understand more about the setup/configuration - for example > I'd like to improve my understanding of atlas by: > - Use the titan rexster api to view/understand the underlying graph > - using titans doghouse UI to poke around > - use the gremlin shell > > In the Atlas Configuration documentation i can see reference to modifying > the underlying titan storage backend & a few other aspects of config. > > Atlas comes with the 0.5.4 titan jars, but not the full distribution > > Before I start trying to add in rexster etc I was wondering if anyone else > has done this & what the appropriate approach might be > > Thanks > Nigel. > > > > >
Re: Titan: configuration in atlas
I think I figured out the reason why the vertices were not getting loaded. The atlas jars also need to be copied into REXHOME/ext/titan to make it work. ATLAS as you might be ware is using berkeley DB and ES as the default storage and index backends . You need to configure that in the rextser.xml conf pointed out in the above link and point to the directory where the data for them resides. Connecting through the gremlin shell also requires a .properties file with all these properties set to load the graph stored by ATLAS. Thanks Suma On Fri, Sep 4, 2015 at 5:47 PM, Suma Shivaprasad < sumasai.shivapra...@gmail.com> wrote: > Hi Nigel, > > You should be able to point to the graph created in ATLAS through Rexster > by following the steps at > http://s3.thinkaurelius.com/docs/titan/current/server.html#_downloading_rexster_and_titan_separately. > I was able to get the Rexster instance up this way but got some issue while > loading the vertices though the edges are seen. Need to dig into this > further. > > Thanks > Suma > > > On Thu, Sep 3, 2015 at 8:47 PM, Nigel Jones wrote: > >> >> >> I'm trying to understand more about the setup/configuration - for example >> I'd like to improve my understanding of atlas by: >> - Use the titan rexster api to view/understand the underlying graph >> - using titans doghouse UI to poke around >> - use the gremlin shell >> >> In the Atlas Configuration documentation i can see reference to modifying >> the underlying titan storage backend & a few other aspects of config. >> >> Atlas comes with the 0.5.4 titan jars, but not the full distribution >> >> Before I start trying to add in rexster etc I was wondering if anyone >> else has done this & what the appropriate approach might be >> >> Thanks >> Nigel. >> >> >> >> >> >
Re: Titan: configuration in atlas
Nigel, Atlas has sufficient abstraction over the repository and does not want to expose it to the users. Given that we have a type-specific DSL, we would like users to interact with the system using that or full-text search. Rester read-only API was added for testing and I purposefully left out the server part since it allows mutations. Given that you want to poke around a graph db, I'd suggest you download titan server with rexster and just point it to the atlas db dir. Makes sense? On Fri, Sep 4, 2015 at 5:23 AM Suma Shivaprasad < sumasai.shivapra...@gmail.com> wrote: > I think I figured out the reason why the vertices were not getting loaded. > The atlas jars also need to be copied into REXHOME/ext/titan to make it > work. > > ATLAS as you might be ware is using berkeley DB and ES as the default > storage and index backends . You need to configure that in the rextser.xml > conf pointed out in the above link and point to the directory where the > data for them resides. > > Connecting through the gremlin shell also requires a .properties file with > all these properties set to load the graph stored by ATLAS. > > Thanks > Suma > > On Fri, Sep 4, 2015 at 5:47 PM, Suma Shivaprasad < > sumasai.shivapra...@gmail.com> wrote: > > > Hi Nigel, > > > > You should be able to point to the graph created in ATLAS through Rexster > > by following the steps at > > > http://s3.thinkaurelius.com/docs/titan/current/server.html#_downloading_rexster_and_titan_separately > . > > I was able to get the Rexster instance up this way but got some issue > while > > loading the vertices though the edges are seen. Need to dig into this > > further. > > > > Thanks > > Suma > > > > > > On Thu, Sep 3, 2015 at 8:47 PM, Nigel Jones wrote: > > > >> > >> > >> I'm trying to understand more about the setup/configuration - for > example > >> I'd like to improve my understanding of atlas by: > >> - Use the titan rexster api to view/understand the underlying graph > >> - using titans doghouse UI to poke around > >> - use the gremlin shell > >> > >> In the Atlas Configuration documentation i can see reference to > modifying > >> the underlying titan storage backend & a few other aspects of config. > >> > >> Atlas comes with the 0.5.4 titan jars, but not the full distribution > >> > >> Before I start trying to add in rexster etc I was wondering if anyone > >> else has done this & what the appropriate approach might be > >> > >> Thanks > >> Nigel. > >> > >> > >> > >> > >> > > >
