[
https://issues.apache.org/jira/browse/UNOMI-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761004#comment-17761004
]
Serge Huber commented on UNOMI-797:
-----------------------------------
Here's the PR to review: https://github.com/apache/unomi/pull/647
> glitches and minor bugs in unomi 2 migration documentation
> ----------------------------------------------------------
>
> Key: UNOMI-797
> URL: https://issues.apache.org/jira/browse/UNOMI-797
> Project: Apache Unomi
> Issue Type: Task
> Reporter: Romain Gauthier
> Assignee: Serge Huber
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hello,
> I did a review of
> https://unomi.apache.org/manual/latest/index.html#_from_version_1_6_to_2_0
> There are couple of glitches and things that can be improved:
> _Enable debug mode
> => link not working
> _what_s_new_
> => link not working
> _with all of the necessary JSON Schemas for its own operation_
> => + as well as all operations generated from the unomi web tracker
> _When creating your new schemas, reviewing debug messages in the logs (using:
> `log:set DEBUG org.apache.unomi.schema.impl.SchemaServiceImpl` in Karaf
> console), will point to errors in your schemas or will help you diagnose why
> the events are not being accepted._
> => since https://jira.jahia.org/browse/UNOMI-796 , we should mention the
> following (or something close): "Set UNOMI_LOGS_JSONSCHEMA_LEVEL env variable
> to DEBUG then restart jCustomer. It is also possible to test if your events
> are valid with the API /cxs/jsonSchema/validateEvent"
> _This requires making sure that you don’t allow open properties by using JSON
> schema keywords such as [unevaluated
> properties](https://json-schema.org/understanding-json-schema/reference/object.html#unevaluated-properties)_
> => Is it grammatically correct?
> _Your Elasticsearch cluster has enough capacity to handle the migration_
> => How are users supposed to know if their infrastructure can handle the
> migration?
> _Start an Apache Unomi 2.0 migration node_
> => Does the migration start automatically? Is anything specific required to
> start a "migration node" or does it work with any unomi 2 instance?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
