Skip to content

[SPARK-29275][SQL][DOC] Describe special date/timestamp values in the SQL migration guide #25948

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MaxGekk wants to merge 2 commits into from
Closed

[SPARK-29275][SQL][DOC] Describe special date/timestamp values in the SQL migration guide #25948

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5d8e57b
Update the SQL migration guide
MaxGekk Sep 27, 2019
c2c6d0c
Remove dots
MaxGekk Sep 27, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/sql-migration-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,20 @@ license: |
</tr>
</table>

- Since Spark 3.0, special values are supported in conversion from strings to dates and timestamps. Those values are simply notational shorthands that will be converted to ordinary date or timestamp values when read. The following string values are supported for dates:
- `epoch [zoneId]` - 1970-01-01
- `today [zoneId]` - the current date in the time zone specified by `spark.sql.session.timeZone`.
- `yesterday [zoneId]` - the current date - 1
- `tomorrow [zoneId]` - the current date + 1
- `now` - the date of running the current query. It has the same notion as today.
For example `SELECT date 'tomorrow' - date 'yesterday';` should output `2`. Here are special timestamp values:
- `epoch [zoneId]` - 1970-01-01 00:00:00+00 (Unix system time zero)
- `today [zoneId]` - midnight today.
Copy link
Member

@dongjoon-hyun dongjoon-hyun Sep 27, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we remove the . at the end? For line 206 and 209, it might be natural. This line might be better be consistent with the following lines (213/214).

Copy link
Member Author

@MaxGekk MaxGekk Sep 27, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed all dots because some items don't form complete sentences, and others must not as well for consistency .

- `yesterday [zoneId]` - midnight yesterday
- `tomorrow [zoneId]` - midnight tomorrow
- `now` - current query start time.
For example `SELECT timestamp 'tomorrow';`.

## Upgrading from Spark SQL 2.4 to 2.4.1

- The value of `spark.executor.heartbeatInterval`, when specified without units like "30" rather than "30s", was
Expand Down