AnishMahto opened a new pull request, #51080:
URL: https://github.com/apache/spark/pull/51080

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: 
https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a 
faster review.
     7. If you want to add a new configuration, please read the guideline first 
for naming configurations in
        
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
     8. If you want to add or modify an error type or message, please read the 
guideline first in
        'common/utils/src/main/resources/error/README.md'.
   -->
   
   ### What changes were proposed in this pull request?
   Add functionality to register graph elements (tables, views, flows) in a 
declarative pipeline's DataflowGraph object, from the SQL files sent on 
`DefineSqlDataset` requests to the spark connect backend.
   
   This involves parsing the SQL text, interpreting the extracted logical 
plans, and constructing appropriate graph element objects (Table, View, Flow).
   
   The consequence is when a pipeline is eventually run, the registered graph 
elements from SQL files will actually materialize and produce the correct 
streaming table/materialized view/temporary view during execution.
   
   
   ### Why are the changes needed?
   To support the creation of Spark Declarative Pipeline objects from SQL files.
   
   
   ### Does this PR introduce _any_ user-facing change?
   No. The Spark Declarative Pipelines module is not yet released in any spark 
version. This PR implements logic to actually service the currently unhandled 
`DefineSqlDataset` spark connect request.
   
   
   ### How was this patch tested?
   `org.apache.spark.sql.pipelines.graph.SqlPipelineSuite` contains the core 
unit tests for SQL graph element registration.
   `org.apache.spark.sql.pipelines.graph.SqlQueryOriginSuite` contains unit 
tests to verify the query origin is correctly constructed for graph elements 
registered from SQL source files.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   No
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to