FYI, there have been changes made to the default Atlas distribution build, as 
follows ...

Three new build profiles have been added to distro to control the default 
configuration and packaging of the graph storage and indexing for Atlas.


1. To build a distribution that configures Atlas for external HBase and Solr, 
build with the external-hbase-solr profile.  This is the default.

    mvn clean package -Pdist,external-hbase-solr


Note that when the external-hbase-solr profile is used the following steps need 
to be completed to make Atlas functional.
   - Configure atlas.graph.storage.hostname.
   - Configure atlas.graph.index.search.solr.zookeeper-url.
   - Set HBASE_CONF_DIR to point to a valid HBase config directory.
   - Create the SOLR indices.

(see "Graph persistence engine - HBase" and "Graph Search Index - Solr" in the 
Configuration section of the Atlas documentation)


2. To build a distribution that packages HBase and Solr, build with the 
embedded-hbase-solr profile.


    mvn clean package -Pdist,embedded-hbase-solr


Using the embedded-hbase-solr profile will configure Atlas so that an HBase 
instance and a Solr instance will be started
and stopped along with the Atlas server by default.

Note that this profile adds the following environment variables to atlas-env.sh 
...


    # indicates whether or not a local instance of HBase should be started for 
Atlas
    export MANAGE_LOCAL_HBASE=true

    # indicates whether or not a local instance of Solr should be started for 
Atlas
    export MANAGE_LOCAL_SOLR=true


To start the Atlas server along with the local HBase and Solr instances ...

    source ./conf/atlas-env.sh;bin/atlas_start.py



3.  To build a distribution that configures Atlas for Berkeley and 
ElasticSearch, build with the berkeley-elasticsearch profile.

    mvn clean package -DskipTests -Pdist,berkeley-elasticsearch




Reply via email to