You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Tommaso Teofili (Jira)" <ji...@apache.org> on 2019/09/11 08:18:00 UTC

[jira] [Comment Edited] (OAK-8616) Leverage oak-search utils in oak-search-elastic where possible

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

Tommaso Teofili edited comment on OAK-8616 at 9/11/19 8:17 AM:
---------------------------------------------------------------

first round of improvements in r1866781, 1866782.


was (Author: teofili):
first round of improvements in r1866781.

> Leverage oak-search utils in oak-search-elastic 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)