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

["Suma Shivaprasad (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340273#comment-15340273 ] 

Suma Shivaprasad commented on ATLAS-844:
----------------------------------------

+1

> 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
>            Assignee: 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)