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 2018/04/29 07:11:00 UTC

[jira] [Resolved] (UNOMI-164) Optimize profile save by avoiding a refresh

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

Serge Huber resolved UNOMI-164.
-------------------------------
    Resolution: Fixed

> Optimize profile save by avoiding a refresh
> -------------------------------------------
>
>                 Key: UNOMI-164
>                 URL: https://issues.apache.org/jira/browse/UNOMI-164
>             Project: Apache Unomi
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.3.0-incubating
>            Reporter: Serge Huber
>            Assignee: Serge Huber
>            Priority: Major
>             Fix For: 1.3.0-incubating
>
>
> Currently when we save a profile, we reload it directly after, forcing a refresh in ElasticSearch. This leads to an in-place index refresh that is not a good idea and kills ElasticSearch performance.
> This change will make it possible to configure whether this refresh should happen, and will be deactivated by default.



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