[NXP-26578] LogEntryJsonWriter doesn't handle complex in ExtendedInfo - Nuxeo Issue Tracker

XML

Word

Printable

Tags:
Backlog priority:
700
Impact type:

Data Persistence Change
Upgrade notes:
Hide

Complex types in ExtendedInfo in LogEntry are now serialized correctly.

This is a breaking change because we used to serialize them as their String representation and we now serialize them as JSON object.

For instance, we changed:

{ "extended": { "array": "[123,456]", "map": "{key1=value1,key2=value2}" } }

to:

{ "extended": { "array": [123, 456], "map": { "key1": "value1", "key2": "value2" } } }
Show
Complex types in ExtendedInfo in LogEntry are now serialized correctly. This is a breaking change because we used to serialize them as their String representation and we now serialize them as JSON object. For instance, we changed: { "extended" : { "array" : "[123,456]" , "map" : "{key1=value1,key2=value2}" } } to: { "extended" : { "array" : [123, 456], "map" : { "key1" : "value1" , "key2" : "value2" } } }
Sprint:
nxcore 10.10.5, nxcore 11.1.1
Story Points:
1

Improve LogEntryJsonWriter in order to handle complex types (array, list, map) in ExtendedInfo.

This is a bug because audit with stream uses this serialization which leads to the loss of this kind of data.

Such data could be page provider params.

is related to

NXP-26360 Deprecate AuditBulker implementation

Estimated:

Remaining:

Logged:

1d 4h