Arik Fraimovich

@bboe how open? very much :) this is low priority for me, but I definitely want to better handle this. It's hard to give an estimate without looking into this...

@jezdez this issue is about large query results and not a long list of queries :)

@changchichung unfortunately not yet. Although if you don't have much more than 50K, maybe just giving more memory to Redash will resolve your issue.

@ismailsimsek try using a larger instance (depends on the dataset size you're trying to download).

@ismailsimsek pagination/server side cursors won't help without changing how we store the data, because we can't stream the data into Postgres (where we currently store results cache). Also it won't...

> Can we set up a config for enforcing limit clause automatically? Yes.. just need to find a way to do it in a "scalable" way for all the data...

@kravets-levko not sure 🤔 The simplest solution? Give up on dynamic values there and keep adding different maps to our build. We should just make it very simple and documented...

> @arikfr How about adding [`connect-src *;`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/connect-src) to [default CSP rules](https://github.com/getredash/redash/blob/master/redash/settings/__init__.py#L115-L125)? According to docs, it will allow only requests triggered by JS code (and it fixes the issue mentioned in...

> The complex part is to make this endpoint secure by checking that this URL is indeed in the visualization definition. But this actually doesn't have to be that hard:...

Thinking of it; making only GET requests should be fine.