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

Jarek Lipski commented on UNOMI-152:
------------------------------------

 Due to low severity of the issue (misplaced events from one day) and potential 
risk of running the script too late, the fix of existing data should be done 
manually. Do not run these scripts after November 2018! Replace localhost:9200 
with you Elasticsearch index address.

In  order to copy the invalid data to the right index: 
curl http://localhost:9200/_reindex --data '\{"source": {"index": 
"context-2018-12"}, "dest": \{"index": "context-2017-12"}}

To delete the invalid index:
curl -X DELETE http://localhost:9200/context-2018-12

> Invalid monthly index name around New Year's Eve
> ------------------------------------------------
>
>                 Key: UNOMI-152
>                 URL: https://issues.apache.org/jira/browse/UNOMI-152
>             Project: Apache Unomi
>          Issue Type: Bug
>            Reporter: Jarek Lipski
>            Priority: Major
>
> On 31/12/2017 the montly index context-2018-12 is created and events are 
> stored there instead of context-2017-12.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to