[OPT-1848] Give warning of too large reports Created: 21/Jan/19  Updated: 03/May/19  Resolved: 15/Apr/19

Status: Done
Project: Camunda Optimize
Component/s: backend, frontend
Affects Version/s: None
Fix Version/s: 2.5.0, 2.5.0-alpha1

Type: Feature Request Priority: L3 - Default
Reporter: Sebastian Stamm Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
OPT-2126 The evaluation of a report indicates ... Sub-task Done  
OPT-2127 Display warning to the user if the re... Feature Part Done  
OPT-2132 Restructure Report Evaluation Response Sub-task Done  
OPT-2134 Use new result structure in front-end Sub-task Done  
OPT-2140 Limit date histogram reports (group b... Sub-task Done  
PM Priority: 40

 Description   

AT:

  • the number of datapoints that a report can evaluate is restricted to 1000
  • if a report evaluation would contains more than the maximum allowed databpoints, then only the first 1000 entries are shown and a warning is displayed to the user similar to the one that already exists in the raw data report
  • changes in the rest api are adjusted in the documentation
  • there is documentation in the user guide about this behavior

Context:
When the user creates a report, he usually selects a view, groupby and visualize as and the report is displayed. However, there are scenarios where there are a lot of datapoints to display, e.g. if you grouped by StartDate: Hour with data from several years or grouped by a variable with a lot of distinct values.

Depending on the visualization and browser, this might create problems where the page appears to become unresponsive while the huge dataload is transferred and processed.

Also there is a back-end dimension to this: if there are too many datapoints, Elasticsearch will reject to evaluate a query in the future. Also it can crash Optimize/Elasticsearch if the queries evaluate too many datapoints.


Generated at Fri Sep 20 01:11:12 CEST 2019 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.