[
https://issues.apache.org/jira/browse/SPARK-53573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun updated SPARK-53573:
----------------------------------
Parent: SPARK-51166
Issue Type: Sub-task (was: Improvement)
> Expand usage of parameter markers by means of a pre-processing parser
> ---------------------------------------------------------------------
>
> Key: SPARK-53573
> URL: https://issues.apache.org/jira/browse/SPARK-53573
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 4.1.0
> Reporter: Serge Rielau
> Assignee: Serge Rielau
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> The current implementation of parameter markers (:Parm and ?) is limited to
> two scenarios which must both be true:
> 1. An expression, such as a WHERE clause or a SELECT list
> 2. A query, a DML statement, or SET VARIABLE.
> There is a lot of value in expanding their use to:
> 1. DDL and utility statements (such as CREATE VIEW, or SHOW)
> 2. Any place a literal can go (such as TBLPROPERTIES, or DECIMAL(?, ?).
> Unfortunately the current implementation is very hard to expand in that
> direction.
> For DDL we must persist the effective text, or remember the parameter marker
> values
> And literals in general do NOT go through the analyzer. They are often
> handled straight in te visit methods.
> This proposed solution is to add a pre-parser which's sole job is replace any
> parameter markers it finds with literals without the regular parser having to
> be aware.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
