[
https://issues.apache.org/jira/browse/UNOMI-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095508#comment-18095508
]
Serge Huber commented on UNOMI-396:
-----------------------------------
h2. Re-targeted to unomi-3.2.0
Moved fixVersion from {{unomi-3.1.0}} to {{unomi-3.2.0}}.
Plugin-driven monthly (or rolling) index aliases for events is an
extension/plugin API task. Core persistence on {{master}} handles aliases
internally for rollover, but there is no drop-in plugin hook matching the
attached patch workflow.
Defining a stable SPI, documentation, and sample plugin belongs on the 3.2
roadmap, not 3.1.0 GA.
h2. Workaround for 3.1
Use built-in rollover/ILM/ISM behaviour, external cron/index templates, or a
custom Karaf plugin maintained outside the 3.1 release gate.
> Add plugin support for index aliases
> ------------------------------------
>
> Key: UNOMI-396
> URL: https://issues.apache.org/jira/browse/UNOMI-396
> Project: Apache Unomi
> Issue Type: Improvement
> Components: unomi(-core)
> Reporter: Yakub Ilyasov
> Priority: Minor
> Fix For: unomi-3.2.0
>
> Attachments: elasticsearchAlias.patch
>
>
> Currently, you have to either change some things in the source code or create
> cronjobs to automatically create an alias for an index on monthly basis if
> you want your event indexes to have a certain alias every month.
>
> It would be nice if there was a way to make a plugin that can be added to the
> unomi deploy folder, instead of having to patch unomi.
>
> The current way to patch this can be found as an attachment.
> [^elasticsearchAlias.patch]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
