jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommaso Teofili (Jira)" <j...@apache.org>
Subject [jira] [Updated] (OAK-8616) Leverage oak-search utils in oak-search-elasticsearch where possible
Date Tue, 10 Sep 2019 14:54:00 GMT

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

Tommaso Teofili updated OAK-8616:
---------------------------------
    Description: 
_oak-search-elasticsearch_ should use _oak-search_ SPIs and utilities as much as possible
to reduce code complexity and duplication.
Even this means changing some methods from *protected* to *public* it should not cause any
back-compat concern because nothing is currently exported yet from within _oak-search_ (in
fact it's embedded in _oak-lucene_).

  was:
_oak-search-elasticsearch_ should use _oak-search_ SPIs and utilities as much as possible
to reduce code complexity and duplication.
Even this means changing some methods from *protected* to *public* it should not cause any
back-compat concern because nothing is currently exported yet from within _oak-search_.


> Leverage oak-search utils in oak-search-elasticsearch where possible
> --------------------------------------------------------------------
>
>                 Key: OAK-8616
>                 URL: https://issues.apache.org/jira/browse/OAK-8616
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: elastic-search
>            Reporter: Tommaso Teofili
>            Assignee: Tommaso Teofili
>            Priority: Major
>             Fix For: 1.18.0
>
>
> _oak-search-elasticsearch_ should use _oak-search_ SPIs and utilities as much as possible
to reduce code complexity and duplication.
> Even this means changing some methods from *protected* to *public* it should not cause
any back-compat concern because nothing is currently exported yet from within _oak-search_
(in fact it's embedded in _oak-lucene_).



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message