[jira] [Commented] (ATLAS-2261) Atlas cannot be built with Titan0 on master with BerkeleyDB
[ https://issues.apache.org/jira/browse/ATLAS-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257216#comment-16257216 ] Madhan Neethiraj commented on ATLAS-2261: - bq. I think we should remove all the configuration from the atals-application.properties file that the user should not change. Given an Atlas build can support only one Graph provider (Titan0/Titan1/Janus), it will be cleaner to not have a configuration to specify the provider. If @Service annotation can be used and have Spring Framework instantiate the available instance, there won't be a need for a configuration like "atlas.graphdb.backend". We need to investigate this. > Atlas cannot be built with Titan0 on master with BerkeleyDB > --- > > Key: ATLAS-2261 > URL: https://issues.apache.org/jira/browse/ATLAS-2261 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2261) Atlas cannot be built with Titan0 on master with BerkeleyDB
[ https://issues.apache.org/jira/browse/ATLAS-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256847#comment-16256847 ] Graham Wallis commented on ATLAS-2261: -- Whoops - apologies - I omitted to mention that I had also inserted the line: atlas.graphdb.backend=org.apache.atlas.repository.graphdb.titan0.Titan0GraphDatabase Didn't quite copy and paste enough of the properties file. :-( > Atlas cannot be built with Titan0 on master with BerkeleyDB > --- > > Key: ATLAS-2261 > URL: https://issues.apache.org/jira/browse/ATLAS-2261 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2261) Atlas cannot be built with Titan0 on master with BerkeleyDB
[ https://issues.apache.org/jira/browse/ATLAS-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256841#comment-16256841 ] David Radley commented on ATLAS-2261: - [~grahamwallis] That did not work for me . It seems I need to add in this line or Atlas does not know to generate titan0: atlas.graphdb.backend=org.apache.atlas.repository.graphdb.titan0.Titan0GraphDatabase [~madhan.neethiraj] I think we should remove all the configuration from the atals-application.properties file that the user should not change. In the case where we build with Titan0 - it is not possible to run Janus- so the code should just work using titan0. In the case where we build with Berkeleyje -we should not put this in the configuration file - as no other value could work with the code we build. We should leave in properties that the user can customize. What do you think? > Atlas cannot be built with Titan0 on master with BerkeleyDB > --- > > Key: ATLAS-2261 > URL: https://issues.apache.org/jira/browse/ATLAS-2261 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2261) Atlas cannot be built with Titan0 on master with BerkeleyDB
[ https://issues.apache.org/jira/browse/ATLAS-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255828#comment-16255828 ] David Radley commented on ATLAS-2261: - Thanks [~grahamwallis] - I will give this circumvention a go. > Atlas cannot be built with Titan0 on master with BerkeleyDB > --- > > Key: ATLAS-2261 > URL: https://issues.apache.org/jira/browse/ATLAS-2261 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2261) Atlas cannot be built with Titan0 on master with BerkeleyDB
[ https://issues.apache.org/jira/browse/ATLAS-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255579#comment-16255579 ] Graham Wallis commented on ATLAS-2261: -- Hi David - I had a play with the current master and like you I found it was not easy to start - but I did the following build and configuration and can get the server to start: mvn clean mvn package -Pdist,berkeley-elasticsearch -DGRAPH-PROVIDER=titan0 -DskipTests cd ...dstro/target/apache-atlas-1.0.0-SNAPSHOT-bin/apache-atlas-1.0.0-SNAPSHOT cd conf Update the atlas-application.properties files as follows (these are just the lines I changed/added, be sure to comment out the conflicting hbase and solr lines): # Graph Storage #atlas.graph.storage.backend=hbase atlas.graph.storage.backend=berkeley atlas.graph.storage.directory=data/berkeley #atlas.graph.storage.hbase.table=apache_atlas_titan # Graph Search Index #atlas.graph.index.search.backend=solr atlas.graph.index.search.backend=elasticsearch Then, cd ../bin atlas_start.py C:\dev\atlas\atlas\distro\target\apache-atlas-1.0.0-SNAPSHOT-bin\apache-atlas-1.0.0-SNAPSHOT\bin>atlas_start.py starting atlas on host localhost starting atlas on port 21000 .. Apache Atlas Server started!!! This is not ideal, as I would have expected berkeley and elasticsearch to have been configured given that's how I built, but I think the default configuration changed, so maybe we now have to manually make the above configuration changes. Hope this helps. Cheers Graham > Atlas cannot be built with Titan0 on master with BerkeleyDB > --- > > Key: ATLAS-2261 > URL: https://issues.apache.org/jira/browse/ATLAS-2261 > Project: Atlas > Issue Type: Bug >Reporter: David Radley > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
