atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-823) Atlas should use external HBase and SOLR
Date Thu, 26 May 2016 06:38:13 GMT

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

Shwetha G S commented on ATLAS-823:
-----------------------------------

There is InMemoryEntityAuditRepository, we can enable it for now, which is of course limited
functionality. But for 0.7, we should add either derby/graph based one by default (for non-hbase
usecases)

> Atlas should use external HBase and SOLR
> ----------------------------------------
>
>                 Key: ATLAS-823
>                 URL: https://issues.apache.org/jira/browse/ATLAS-823
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, including:
> # lack of support by Ambari makes it difficult to handle kerberization, upgrade/migration,
start/stop
> # not suitable for production use - no HA, local-storage
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should be updated
to use external HBase and SOLR. 



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

Mime
View raw message