-
Bug
-
Resolution: Timed out
-
Low
-
Severity 3 - Minor
Issue Summary
Using the GET method to this specific API request, we get below exception:
https://<instance>/wiki/rest/api/search?limit=1000&cql=parent=xxxxxxxx
com.atlassian.confluence.api.service.exceptions.ServiceException: Exception executing cql as async search: parent=xxxxxxxxx
Environment
- Confluence Cloud
Expected Results
No error on the page, and the page details should be displayed.
Actual Results
Splunk shows below error:
Caused by: org.elasticsearch.ElasticsearchException: too_many_clauses:too_many_clauses: maxClauseCount is set to 1024 com.atlassian.confluence.impl.search.elasticsearch.rest.ResponseErrorParser.handleOtherException(ResponseErrorParser.java:113) com.atlassian.confluence.impl.search.elasticsearch.rest.ResponseErrorParser.parseErrorResponse(ResponseErrorParser.java:61) com.atlassian.confluence.impl.search.elasticsearch.rest.ResponseErrorParser.handleShardSearchFailure(ResponseErrorParser.java:93) com.atlassian.confluence.impl.search.elasticsearch.rest.ResponseErrorParser.lambda$handleShardSearchFailures$0(ResponseErrorParser.java:88) java.lang.Iterable.forEach(Iterable.java:75) com.atlassian.confluence.impl.search.elasticsearch.rest.ResponseErrorParser.handleShardSearchFailures(ResponseErrorParser.java:88) ... 42 more } ext: { [+] } hostname: dde06fed3820 level: WARN logger: com.atlassian.confluence.rest.api.model.ExceptionConverter m: { [+] } message: Could not map exception type com.atlassian.confluence.api.service.exceptions.ServiceException to a specific REST status. Defaulting to InternalServerError micros_container: confluence product: confluence thread: http-bio-8081-exec-60 [tenantId:xxxxxxxxxxxxxxxx] [traceId:00cf48a5c560cd7f] time: 2019-08-20T12:10:59Z timestamp: 2019-08-20T12:10:59.410
Workaround
Currently there is no known workaround for this behaviour. A workaround will be added here when available
- is cloned from
-
-
- Closed
-
- blocks
-
JST-503320 Loading...
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!