[
https://issues.apache.org/jira/browse/SPARK-58270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Neumann resolved SPARK-58270.
-------------------------------------
Fix Version/s: 4.3.0
Resolution: Done
It was initially suggested as a follow-up, but then implemented already in
SPARK-58261
> Improve lexing/parsing for SCD TYPE
> ------------------------------------
>
> Key: SPARK-58270
> URL: https://issues.apache.org/jira/browse/SPARK-58270
> Project: Spark
> Issue Type: Sub-task
> Components: Declarative Pipelines
> Affects Versions: 4.3.0
> Reporter: Andreas Neumann
> Priority: Major
> Fix For: 4.3.0
>
>
> Currently, the SCD Type s represented by a single Lexer token SCD_TYPE_1 =
> "SCD TYPE 1", and the same same for type2. This is not great because any
> double whitespace or newline between one of the three words will result in
> failure to parse. A better way to do this is to parse SCD and TYPE as
> separate tokens and have the grammar expect the sequnece of them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
