You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (JIRA)" <ji...@apache.org> on 2018/09/11 08:40:00 UTC

[jira] [Updated] (UNOMI-198) Segment evaluation can go into infinite recursion

     [ https://issues.apache.org/jira/browse/UNOMI-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Serge Huber updated UNOMI-198:
------------------------------
    Affects Version/s: 1.1.0-incubating
                       1.2.0-incubating
                       1.3.0-incubating
        Fix Version/s: 1.4.0-incubating

> Segment evaluation can go into infinite recursion
> -------------------------------------------------
>
>                 Key: UNOMI-198
>                 URL: https://issues.apache.org/jira/browse/UNOMI-198
>             Project: Apache Unomi
>          Issue Type: Bug
>    Affects Versions: 1.1.0-incubating, 1.2.0-incubating, 1.3.0-incubating
>            Reporter: Thomas Draier
>            Assignee: Thomas Draier
>            Priority: Major
>             Fix For: 1.4.0-incubating
>
>
> Every time a profile is update, an updatedProfile event is sent and triggers the segment evaluation rule. It's easy to create a segment of all users that are not in this segment, which  will produce an infinite recursion and go into StackOverflowError :
> {code:json}
> {
>   "itemId": "_3a71uuslk",
>   "itemType": "segment",
>   "version": 4,
>   "condition": {
>     "parameterValues": {
>       "segments": ["_3a71uuslk"],
>       "matchType": "none"
>     },
>     "type": "profileSegmentCondition"
>   },
>   "metadata": {
>     "id": "_3a71uuslk",
>     "name": "test",
>     "description": null,
>     "scope": "systemscope",
>     "tags": [],
>     "systemTags": [],
>     "enabled": false,
>     "missingPlugins": false,
>     "hidden": false,
>     "readOnly": false
>   }
> }
> {code}
>  
> Probably other kind of rules can also go into StackOverflowError. We should try to avoid going into this kind of recursion



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)