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

Posted to dev@unomi.apache.org by "Serge Huber (JIRA)" <ji...@apache.org> on 2019/05/15 17:53:00 UTC

[jira] [Updated] (UNOMI-122) Use bulk processing for indexation (Performance improvement)

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

Serge Huber updated UNOMI-122:
------------------------------
    Affects Version/s: 1.4.0
                       1.3.0-incubating

> Use bulk processing for indexation (Performance improvement)
> ------------------------------------------------------------
>
>                 Key: UNOMI-122
>                 URL: https://issues.apache.org/jira/browse/UNOMI-122
>             Project: Apache Unomi
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.2.0-incubating, 1.3.0-incubating, 1.4.0
>            Reporter: Serge Huber
>            Assignee: Serge Huber
>            Priority: Major
>             Fix For: 1.5.0
>
>         Attachments: UNOMI_122_Performance_Improvement___Use_bulk_processing_for_indexing.patch
>
>
> It would be great to also have ElasticSearch bulk processing for general indexation, it will boost performance. However this is a bit tricky to get right because we need a temporary cache to make sure that items are available between the time they were saved using the PersistenceService and the time that ES actually makes them available for load.
> A short-lived cache could work, but would require a lot of testing to make sure there are no negative side effects.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)