[
https://issues.apache.org/jira/browse/ATLAS-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
<lines removed>
# 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)
