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

Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2023/01/03 14:17:00 UTC

[jira] [Commented] (UNOMI-723) Backport optimization on non persisted events on 1.7.x

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

Kevan Jahanshahi commented on UNOMI-723:
----------------------------------------

PR: [https://github.com/apache/unomi/pull/564]

 

> Backport optimization on non persisted events on 1.7.x
> ------------------------------------------------------
>
>                 Key: UNOMI-723
>                 URL: https://issues.apache.org/jira/browse/UNOMI-723
>             Project: Apache Unomi
>          Issue Type: Bug
>    Affects Versions: unomi-1.7.1
>            Reporter: Kevan Jahanshahi
>            Assignee: Kevan Jahanshahi
>            Priority: Major
>             Fix For: unomi-1.8.0
>
>
> We need to backport: [https://jira.jahia.org/browse/UNOMI-597]
> in Unomi 1.7.x.
> It is require to avoid poluting the event index with the profile as target stored in ElasticSearch. In case of profile containing a lot of properties it can drastically increase the number of potential field for the event indices.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)