[
https://issues.apache.org/jira/browse/UNOMI-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895229#comment-17895229
]
Francois Gerthoffert commented on UNOMI-862:
--------------------------------------------
This ticket was tested by performing a real migration in a clone of a prod
environment.
> Error in scope existing check during the migration
> --------------------------------------------------
>
> Key: UNOMI-862
> URL: https://issues.apache.org/jira/browse/UNOMI-862
> Project: Apache Unomi
> Issue Type: Bug
> Reporter: Jonathan Sinovassin-Naïk
> Assignee: Jonathan Sinovassin-Naïk
> Priority: Major
> Fix For: unomi-2.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During the migration the step 2.0.0-create-scopes-from-existing-events cheks
> if the scope exists before creating it.
> If there is special characters in the scope name, the migration fails due to
> java.lang.IllegalArgumentException
> {code:java}
> Error executing: {version=2.0.0, name='scopes',
> bundle=org.apache.unomi.shell-commands}
> java.lang.IllegalArgumentException: Illegal character in path at index 113:
> https://localhost:9200/context-scope/_doc/scope with space
> at java.net.URI.create(URI.java:883) ~[?:?]
> at org.apache.http.client.methods.HttpGet.<init>(HttpGet.java:66)
> ~[!/:4.5.14]
> at
> org.apache.unomi.shell.migration.utils.HttpUtils.executeGetRequest(HttpUtils.java:102)
> ~[!/:?]
> [...]
> {code}
> The migration should not fail if there is some special characters in the scope
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
