[
https://issues.apache.org/jira/browse/UNOMI-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095507#comment-18095507
]
Serge Huber commented on UNOMI-698:
-----------------------------------
h2. Re-targeted to unomi-3.2.0
Moved fixVersion from {{unomi-3.1.0}} to {{unomi-3.2.0}}.
Allowlisting or blocklisting which profile properties are copied into the
session object is a storage/behaviour change. Many rules and actions assume the
current full copy. A safe change needs config design, runtime behaviour change,
integration tests, and session migration — too large for the 3.1.0 GA window.
Note: {{requiredProfileProperties}} on {{/context.json}} only filters
*response* profile properties to the client; it does not change internal
session storage.
h2. Workaround for 3.1
Use {{requiredProfileProperties}} / concealed property tags to limit what
clients receive; accept full session copy in persistence until 3.2 delivers
allowlist support.
> Do not copy all profile properties in the session object
> --------------------------------------------------------
>
> Key: UNOMI-698
> URL: https://issues.apache.org/jira/browse/UNOMI-698
> Project: Apache Unomi
> Issue Type: New Feature
> Reporter: romain.gauthier
> Priority: Major
> Fix For: unomi-3.2.0
>
>
> Currently, the profile is entirely copied to the session. This is needed as
> many rules and actions assume the presence of this copy. However, it would be
> nice to have a logic to avoid copying all properties and instead have a
> forbidden list or even better: an "allowlist" that would only copy some
> properties.
> This would reduce Unomi size and make things less complex.
> Migration of existing sessions should be taken into account
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
