[
https://issues.apache.org/jira/browse/UNOMI-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Gauthier updated UNOMI-816:
----------------------------------
Description:
In unomi 1, it was possible to have login events with a scope that either is:
* null
* empty ""
* non existing
In Unomi 2, it's not possible anymore. I know there is already a migration
script, but are these 3 cases taken into account?
https://github.com/apache/unomi/blob/98e4d87c827b05e817e0538793a8a34e5434a00a/tools/shell-commands/src/main/resources/requestBody/2.0.0/event_migrate.painless#L4
If no, is it possible to assign a default value?
If yes, is it possible to add integration tests?
was:
In unomi 1, it was possible to have login events with a scope that either is:
* null
* empty ""
* non existing
In Unomi 2, it's not possible anymore. I know there is already a migration
script, but are these 3 cases taken into account?
If no, is it possible to assign a default value?
If yes, is it possible to add integration tests?
> Data consistency for login events in migration to jcustomer 2
> -------------------------------------------------------------
>
> Key: UNOMI-816
> URL: https://issues.apache.org/jira/browse/UNOMI-816
> Project: Apache Unomi
> Issue Type: Improvement
> Reporter: Romain Gauthier
> Priority: Major
>
> In unomi 1, it was possible to have login events with a scope that either is:
> * null
> * empty ""
> * non existing
> In Unomi 2, it's not possible anymore. I know there is already a migration
> script, but are these 3 cases taken into account?
> https://github.com/apache/unomi/blob/98e4d87c827b05e817e0538793a8a34e5434a00a/tools/shell-commands/src/main/resources/requestBody/2.0.0/event_migrate.painless#L4
> If no, is it possible to assign a default value?
> If yes, is it possible to add integration tests?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
