jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7981) Implement elastic search support based off of oak-search
Date Tue, 16 Jul 2019 09:46:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885997#comment-16885997

Thomas Mueller commented on OAK-7981:

What about using "oak-search-elastic" instead? To be in line with "oak-segment-azure", "oak-store-document"
and so on. We already have "oak-search" so it would be sorted there. I know we have "oak-lucene"
and "oak-solr", and don't want to rename those, but for a new component it might be OK to
use this naming convention. I think using "elastic" instead of "elasticsearch" is fine as
we also have "azure" and not "azureblobstore". Really just change the module name, not package
names or class names.

> Implement elastic search support based off of oak-search
> --------------------------------------------------------
>                 Key: OAK-7981
>                 URL: https://issues.apache.org/jira/browse/OAK-7981
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: elastic-search, search
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Major

This message was sent by Atlassian JIRA

View raw message