[jira] [Updated] (ATLAS-844) Remove titan berkeley and elastic search jars if hbase/solr based profiles are chosen

["Hemanth Yamijala (JIRA)" <ji...@apache.org>]

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

Hemanth Yamijala updated ATLAS-844:
-----------------------------------
    Attachment: ATLAS-844.patch

The attached patch does the following:

* When the profile selected for packaging is anything other than {{berkeley-elasticsearch}}, it excludes the Berkeley DB Java edition jar, elastic search jar, and the corresponding titan adapters.
* When the profile selected is {{berkeley-elasticsearch}}, it excludes only the Berkeley DB Java edition jar. 
* I think the exclusion may be required because the BerkeleyDB java edition has the Sleepy Cat license (http://www.oracle.com/technetwork/database/berkeleydb/downloads/jeoslicense-086837.html, https://opensource.org/licenses/Sleepycat) which seems to be incompatible for distribution with the Apache Software license. Some reference to Titan mailing list documentation on this: https://groups.google.com/d/msg/aureliusgraphs/5zF6zzGRFEs/igecqgkAOqkJ
* Adds documentation steps for how to get the BerkeleyDB jar if required. (I used the documentation steps from Apache Falcon which has similar needs, I think).

Note the following:
* I have only removed the bundling of the jars in Atlas distribution. AFAIK, that's the only requirement. 
* The titan adapters are covered under Apache license, hence they can be redistributed.
* The involved jars were a part of the Atlas server war file, hence the changes to {{maven-war-plugin}}.

I tested this with
* {{mvn clean install}} - runs all tests and passes
* {{mvn clean package -Pdist}} - default profile (pointing to external hbase and solr, hence removes the other jars)
* {{mvn clean package -Pdist,berkeley-elasticsearch}} (includes the berkeley titan adapter, ES jar, and ES titan adapter). Copied the berkeley JE jar to ${atlas_home}/extlib and server starts up fine.



> Remove titan berkeley and elastic search jars if hbase/solr based profiles are chosen
> -------------------------------------------------------------------------------------
>
>                 Key: ATLAS-844
>                 URL: https://issues.apache.org/jira/browse/ATLAS-844
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.7-incubating
>            Reporter: Hemanth Yamijala
>             Fix For: 0.7-incubating
>
>         Attachments: ATLAS-844.patch
>
>
> With ATLAS-833, users of Atlas now have the option of using an external HBase/Solr installation, an self-contained HBase/Solr installation (embedded mode) or BerkeleyDB/Elastic Search installation.
> When choosing either of the first two modes, we can potentially remove the Titan berkeley DB or elastic search jars. This helps distributions which have restrictions on using these jars from a contractual perspective.



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