[
https://issues.apache.org/jira/browse/UNOMI-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Sinovassin-Naïk updated UNOMI-885:
-------------------------------------------
Fix Version/s: unomi-2.7.0
> Error during migration
> ----------------------
>
> Key: UNOMI-885
> URL: https://issues.apache.org/jira/browse/UNOMI-885
> Project: Apache Unomi
> Issue Type: Bug
> Reporter: Jonathan Sinovassin-Naïk
> Assignee: Jonathan Sinovassin-Naïk
> Priority: Major
> Fix For: unomi-2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h2. Current behaviour:
> During a migration using the Elasticsearch _reindex API, the task fails if
> the destination index is associated with an alias where is_write_index:
> false. This prevents documents from being indexed and blocks the migration
> process.
> It's happening in the migrate-2.5.0-10-loginEventScope for example.
> https://github.com/apache/unomi/blob/3b2da028d6ac50b2b276c1150491bf0fc9cd689a/tools/shell-commands/src/main/resources/META-INF/cxs/migration/migrate-2.5.0-10-loginEventScope.groovy#L30
> when there is more than one index created for the events.
> In that case the settings for the event alias for event will be
> {code:java}
> {
> "prefix-event-000002": {
> "aliases": {
> "prefix-jc-event": {
> "is_write_index": true
> }
> }
> },
> "prefix-event-000001": {
> "aliases": {
> "prefix-event": {
> "is_write_index": false
> }
> }
> }
> }
> {code}
> but the script tries to reindex prefix-event-000001 and it results to a
> failure.
> h2. Expected behaviour:
> The reindex operation should be executed successfully.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
