You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Andreas Neumann (Jira)" <ji...@apache.org> on 2026/07/22 21:52:00 UTC

[jira] [Created] (SPARK-58270) Improve lexing/parsing for SCD TYPE

Andreas Neumann created SPARK-58270:
---------------------------------------

             Summary: 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


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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org