Timeouts (#698)
We've revamped timeouts in Turnilo. In general, Turnilo tries to honour Druid timeouts and does not impose any additional timeouts.
Clusters timeout is sent with Druid query. You can of course override it on data source basis using druidContext on DataCube. Additionally, Turnilo instance have two settings: serverTimeout and clientTimeout and both default to 0 which means no timeout at all.
serverTimeout is maximum time of handling request from browser. clientTimeout is time after which browser would terminate request to server.
Retries (#699)
Turnilo now support retry policy. All queries to Druid can be retried after failure or timeout.
Property retry on Cluster should be an object with two fields: maxAttempts is count of attempts Turnilo would make and delay is time in ms between each attempt.
Fixes
- Turnilo now respects user timezone when exporting view to cvs. Thanks to @metapraveen for the fix (#707)!