Table CSV export behaviour

Follow
Avatar
Johannes Boehm

Hello Omnisci'ers,

Not sure whether that's a bug or an (undocumented) feature: when I have a table on a dashboard, and I try to export the data to CSV, only the set of rows that have been loaded get exported. For a new table that's 50 rows (the INITIAL_SIZE in here).

I'm not sure that this is really what the user has in mind, given that there is no easy way of seeing the number of observations that have been cached (without scrolling to the "bottom" and maybe triggering a new query). Ex-ante, I would have expected a full export of the query result underlying the table, possibly with a limit on the number of rows similarly to the "ui/map_export_limit" config parameter.

Slightly related to this: sometimes it would be nice to see the SQL query underlying a chart, or the crossfilter. That would, for example, enable a workaround to the above problem: I could then simply export the data via an SQL query. As of right now, I can't think of another way to get this than to dig into the javascript.

Overall, Immerse is a joy to use. Many thanks again for all your work.

0

Comments

1 comment

Sort by Date Votes
  • Avatar
    Candido Dessanti

    Thanks for the kind words about immerse @jmboehm,

    We are aware of the problem, and we are thinking about how to solve that. I guess that right now, we are exporting the underlying data of each type of chart in the same way, so what is ok for most of the chart types doesn't fit the table chart.

    Your idea about exporting the query used to populate the chart is clever, but in my opinion, could be also a little dangerous and tricky in case you are. The query run to populate le latest rows would be something like that

    SELECT date_trunc(month, flights_sk_orig.dep_timestamp) AS key0,flights_sk_orig.airplanes_sk AS key1,flights_sk_orig.arr_airport_fk AS key2,AVG(arrdelay) AS col0 FROM flights_sk_orig GROUP BY key0, key1, key2 ORDER BY col0 DESC NULLS LAST LIMIT 100 OFFSET 0

    changing the limit to one the configuration parameter would work, but a user could remove and/or raise that limit in a significant way, getting watchdog exception or stalling the system with a long-running query.

    anyway very thanks for your suggestions, they are very appreciated, and we will reach you hen that annoying problem will be settled.

    Regards, Candido

    1
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post