Closed Bug 1369085 Opened 8 years ago Closed 8 years ago

Show running Presto version in re:dash

Categories

(Data Platform and Tools :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gfritzsche, Unassigned)

Details

Feedback that came in is that currently it's hard to find out what Presto version (and thus features) are available through our re:dash instance. Can we show the version somewhere? Or have a link to a page that is documenting the current versions etc.?
To show how my current workflow falls down: I have https://prestodb.io/docs/current/functions.html bookmarked as my reference for presto SQL functions, which is a really nice reference. But there are a set of things that are documented here which don't work on STMO: VALUES clause lambda functions e.g. transform() reduce() etc various kinds of subqueries including scalar subqueries It would be nice to browse the presto reference that matches the currently available version of presto. Aside, are we at the mercy of EMR releases for presto updates? If so I'm guessing STMO is still using EMR 5.2.1 and not EMR 5.5.0. Is there a bug I can follow about upgrading STMO to use EMR 5.5.0?
Got it. Opened https://github.com/mozilla/redash/issues/89 for triage and tracking.
Rob, I see the github issue has been closed, but this is still not working for Presto/Athena in general - are there plans to work on this further, or should we close this out?
Flags: needinfo?(rmiller)
Hrm... yeah, I see the literal string "'version'", but not anything useful. I'll dig in and see what's going on.
Okay, we fixed this regression, the Presto version is now showing up in the STMO UI, as is the version for most of the PostGreSQL data sources. Athena isn't yet showing up, but as this bug was originally opened for Presto, I'm closing it. I'll open a github issue to track getting the Athena version to show up.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(rmiller)
Resolution: --- → FIXED
Component: Redash (STMO) → General
You need to log in before you can comment on or make changes to this bug.