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 2021/05/04 16:29:00 UTC
[jira] [Created] (UNOMI-480) Default configuration for
monthlyIndexOverride is wrong, could cause major data integrity issues when
upgrading
Serge Huber created UNOMI-480:
---------------------------------
Summary: Default configuration for monthlyIndexOverride is wrong, could cause major data integrity issues when upgrading
Key: UNOMI-480
URL: https://issues.apache.org/jira/browse/UNOMI-480
Project: Apache Unomi
Issue Type: Bug
Components: core
Affects Versions: 1.5.5
Reporter: Serge Huber
Assignee: Serge Huber
Fix For: 1.5.6
The default value for the following setting:
{code}
<property name="itemsMonthlyIndexedOverride" value="${es.monthlyIndex.itemsMonthlyIndexedOverride}" />
{code}
does not work properly because since the referenced value doesn't exist Blueprint uses the marker as a value instead of an empty string (was expected).
The consequence is that the event and session item types are not monthly indexes anymore, which has the following consequences:
- existing data sets will create a new context-event and context-session index
- all old context-event-date-* and context-session-date-* indices will no longer be used and queries for the data will not work
- external tools such as Kibana will not work either
As this is a major data model bug, it is being flagged critical and a special release will be prepared for it. It is recommended that all users avoid using 1.5.5 and wait for 1.5.6 instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)