[
https://issues.apache.org/jira/browse/UNOMI-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Sinovassin-Naïk updated UNOMI-611:
-------------------------------------------
Description:
Contrary to the version 1.6.0 when restarting UNOMI, the following objects
*ConditionType, ActionType, Goal, Profile, PropertyType, Rule, Segment,
Scoring* are deployed in elasticsearch and if these objects are already stored
and modified in Elasticsearch, they are overridden.
If there is patches which are applied to these objects, the modifications done
by them are lost because the patches are not applied when restarting unomi.
We should apply the patches each time we are starting UNOMI to keep the
consistency before and after the starting.
was:
Contrary to the version 1.6.0 when restarting UNOMI, the following objects are
deployed in elasticsearch and if these objects are already stored and modified
in Elasticsearch, they are overridden.
If there is patches which are applied to these objects, the modifications done
by them are lost because the patches are not applied when restarting unomi.
We should apply the patches each time we are starting UNOMI to keep the
consistency before and after the starting.
> Inconsistency when restarting unomi
> -----------------------------------
>
> Key: UNOMI-611
> URL: https://issues.apache.org/jira/browse/UNOMI-611
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Jonathan Sinovassin-Naïk
> Priority: Major
>
> Contrary to the version 1.6.0 when restarting UNOMI, the following objects
> *ConditionType, ActionType, Goal, Profile, PropertyType, Rule, Segment,
> Scoring* are deployed in elasticsearch and if these objects are already
> stored and modified in Elasticsearch, they are overridden.
> If there is patches which are applied to these objects, the modifications
> done by them are lost because the patches are not applied when restarting
> unomi.
>
> We should apply the patches each time we are starting UNOMI to keep the
> consistency before and after the starting.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)