Actions
Feature #6309
closedFix ending timestamp after query submission
Start date:
04/09/2020
Due date:
% Done:
100%
Estimated time:
To be discussed:
No
Description
Currently if user does not provide ending timestamp, the field stays "open", and submitting the query again might result in different results (new incoming data). That's bad for repeatability and determinism - and consequently caching, for instance.
Let's make timestamp fixed at the time of query submission, so query form of result page will not bring empty ending timestamp, but the fixed one. If the user needs to get new data, he can rewrite or empty the ending timestamp contents again.
Related issues
Updated by Pavel Kácha over 4 years ago
- Blocks Feature #6310: Implement result caching added
Updated by Jan Mach over 4 years ago
- Status changed from New to Closed
- Target version changed from 2.8 to 2.7
- % Done changed from 0 to 100
Actions