[ 
https://issues.apache.org/jira/browse/SYNCOPE-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679817#comment-17679817
 ] 

ASF subversion and git services commented on SYNCOPE-1725:
----------------------------------------------------------

Commit 086617475c46a089043c763122d2e0b49fb72821 in syncope's branch 
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=086617475c ]

[SYNCOPE-1725] Accumulating OR and AND conditions before generating the final 
ES query


> Error when searching with high number of OR or AND conditions with 
> Elasticsearch
> --------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-1725
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1725
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.1
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>              Labels: elasticsearch
>             Fix For: 3.0.2, 4.0.0
>
>
> When the FIQL expression contains a high number of OR or AND clauses, the 
> transformed query to Elasticsearch returns HTTP 400 with an error payload 
> like as follows:
> {code}
> {
>   "error": {
>     "root_cause": [
>       {
>         "type": "parsing_exception",
>         "reason": "Failed to parse",
>         "line": 1,
>         "col": 2608
>       }
>     ],
>     "type": "parsing_exception",
>     "reason": "Failed to parse",
>     "line": 1,
>     "col": 2608,
>     "caused_by": {
>       "type": "x_content_parse_exception",
>       "reason": "[1:2608] [bool] failed to parse field [must]",
>       "caused_by": {
>         "type": "illegal_argument_exception",
>         "reason": "The nested depth of the query exceeds the maximum nested 
> depth for queries set in [indices.query.bool.max_nested_depth]"
>       }
>     }
>   },
>   "status": 400
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to