[
https://issues.apache.org/jira/browse/UNOMI-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136002#comment-18136002
]
Serge Huber commented on UNOMI-1026:
------------------------------------
Pull request: https://github.com/apache/unomi/pull/938
> Built-in JSON schemas can lose their createdBy audit data after migration
> (flaky Migrate16xToCurrentVersionIT)
> --------------------------------------------------------------------------------------------------------------
>
> Key: UNOMI-1026
> URL: https://issues.apache.org/jira/browse/UNOMI-1026
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: unomi-4.0.0
> Reporter: Serge Huber
> Priority: Major
> Fix For: unomi-4.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. In short
> After an upgrade, some built-in event schemas can lose the record of who
> created them and when. It also makes an integration test fail at random,
> which blocks unrelated changes.
> h3. Details
> * {{Migrate16xToCurrentVersionIT.checkMigratedData}} intermittently fails
> with "Created by should be set for system_..._jsonschema" (seen on PR 916 and
> PR 927, both unrelated).
> * {{SchemaServiceImpl}} saves bundle schemas with {{persistenceService.save}}
> directly, bypassing the {{createdBy}}/{{creationDate}} carry-over that
> {{AbstractMultiTypeCachingService}} applies (UNOMI-997). If the bundle
> re-saves its schemas after migration, the migrated audit data is overwritten.
> h3. Fix and test
> Save bundle schemas through the audit-preserving path. The migration IT must
> pass reliably, and a re-saved predefined schema must keep its original
> {{createdBy}}.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
