[
https://issues.apache.org/jira/browse/SPARK-57421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sotirios Kougiouris updated SPARK-57421:
----------------------------------------
Parent: SPARK-58010
Issue Type: Sub-task (was: Task)
> Support @-syntax version time travel on table name
> --------------------------------------------------
>
> Key: SPARK-57421
> URL: https://issues.apache.org/jira/browse/SPARK-57421
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 4.3.0
> Reporter: Sotirios Kougiouris
> Assignee: Sotirios Kougiouris
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.3.0
>
>
> h2. What
> Add the {{@}} version time travel shorthand on table names so that
> {code:sql}
> SELECT * FROM name@vN
> {code}
> and
> {code:java}
> spark.read.format("format").table("name@vN")
> {code}
> parse into the same plan as the existing {{VERSION AS OF}} and
> {{option("versionAsOf")}} syntaxes. Support for SQL, the classic DataFrame
> reader, and Spark Connect.
> h2. Why
> Spark already supports {{VERSION AS OF}} and the {{{}versionAsOf{}}} reader
> options, but not the compact {{@v}} suffix. Resolving it at parse time also
> simplifies the time travel entry points pipeline.
> h2. Proposed change
> * Lexer/grammar: add {{@v}}-suffix on table identifiers.
> * AstBuilder converts the suffix into {{RelationTimeTravel}}.
> * New flag {{spark.sql.timeTravel.atSyntax.enabled}} (default {{true}}) to
> allow or disallow.
> h2. Notes
> * Backquoted identifiers like {{`name@v1`}} remain literal table names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
