Closed Bug 1332395 Opened 8 years ago Closed 5 years ago

Make notebook experimenting with date/datetime/timestamp types

Categories

(Data Platform and Tools :: General, defect, P3)

defect
Points:
1

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: frank, Unassigned)

References

Details

There are a few time types in Presto and Parquet. We should have a notebook experimenting with all of them, casting from string, importing to Presto, etc. This should be reproduceable and readable so we can know which types to use moving forward.
Points: --- → 1
Priority: -- → P3
Component: Metrics: Pipeline → Redash (STMO)
Product: Cloud Services → Data Platform and Tools
This is currently in the "Redash (STMO)" component, but AFAICT it doesn't seem to have anything to do with redash, so it's either misfiled or I'm not understanding the issue. Frank, can you help me understand which of these is the case?
Flags: needinfo?(fbertsch)
(In reply to Rob Miller [:RaFromBRC :rmiller] from comment #1) > This is currently in the "Redash (STMO)" component, but AFAICT it doesn't > seem to have anything to do with redash, so it's either misfiled or I'm not > understanding the issue. Frank, can you help me understand which of these is > the case? The reason this is filed under STMO is largely because that's where a lot of the confusion happens w.r.t. dates, especially because re:dash does it's own casting of dates, and some strings. I am no sure if we can test that in any sort of reproducible way though. Moving to Presto.
Component: Redash (STMO) → Presto
Flags: needinfo?(fbertsch)
Ah, gotcha. I just saw that you wanted to create a notebook, and wasn't quite sure how STMO fit into this at all. Thanks for clarifying.
This main_summary time reference sheet might be useful for making the notebook. https://docs.google.com/spreadsheets/d/1DQk0YQx2PLaY2ZMTdhF2TA-ueZ6g5PWwUqbPWL90AHM

Moving to General.

Component: Presto → General

Presto is deprecated.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.