User story: Writing queries often works with data of not necessarily known exact types. For example, a string date could be YYYYMMDD, or YYYY-MM-DD. A long timestamp could be seconds, milliseconds, or nanoseconds since the epoch.
Generally I have to do a quick SELECT * on some recent data and keep that open in a new window when writing queries. This would reduce that burden.
It would be nice to have them be some recent data, but it's not clear to me that re:dash will always know how to find which data is recent and which is not. For the very least we can select a few rows from the most recent dates in all of the telemetry datasets partitioned by submission_date_s3.
User story: Writing queries often works with data of not necessarily known exact types. For example, a string date could be
YYYYMMDD, orYYYY-MM-DD. A long timestamp could be seconds, milliseconds, or nanoseconds since the epoch.Generally I have to do a quick
SELECT *on some recent data and keep that open in a new window when writing queries. This would reduce that burden.It would be nice to have them be some recent data, but it's not clear to me that re:dash will always know how to find which data is recent and which is not. For the very least we can select a few rows from the most recent dates in all of the telemetry datasets partitioned by
submission_date_s3.