(Analytics) Return conflict on too many records

Registered by Lars Helge Øverland on 2016-10-07

The analytics API has an configurable max limit for the number of records to return through the system setting ANALYTICS_MAX_LIMIT. Currently, the response is simply cut off at this limit when exceeded. This is confusing as it can silently give a wrong impression.

Instead, the analytics API should return HTTP 409 Conflict with the explanation "Max number of records limit exceeded, adjust the system setting or change the query".

This applies to both aggregate and event analytics.

Blueprint information

Status:
Not started
Approver:
Lars Helge Øverland
Priority:
Medium
Drafter:
Lars Helge Øverland
Direction:
Approved
Assignee:
Stian Sandvold
Definition:
New
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None

Related branches

Sprints

Whiteboard

Verify that error is logged if a query exceeds max limit of rows

defaultEventAnalyticsService
jdbcEventAnalyticsService

This is currently implemented, but no indication is given in the event report app that the request failed.

{
"httpStatus": "Conflict",
"httpStatusCode": 409,
"status": "ERROR",
"message": "Number of rows produced by query is larger than the max limit: 1000"
}

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.