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

   
   ### What changes were proposed in this pull request?
   This PR fixes the DROP operator in pipe syntax (|>) to support qualified 
column names.
   
   
   
   ### Why are the changes needed?
   Previously, the DROP operator in pipe syntax only accepted simple 
identifiers due to the use of identifierSeq in the grammar. This prevented 
users from dropping struct fields using qualified names
   
   
   ### Does this PR introduce _any_ user-facing change?
   Yes. Users can now use qualified column names with the DROP pipe operator.
   
   Before changes:
   <img width="1028" height="646" alt="Screenshot 2026-01-06 at 4 19 51 PM" 
src="https://github.com/user-attachments/assets/cb0e7c12-e44a-435c-a002-97b0019c9a4b";
 />
   
   After changes:
   <img width="1028" height="462" alt="Screenshot 2026-01-06 at 4 18 15 PM" 
src="https://github.com/user-attachments/assets/f0d48598-be4a-4672-bb7f-3647270eac99";
 />
   
   
   
   ### How was this patch tested?
   
   Test 1:
   Updated SQL test cases in pipe-operators.sql with positive test for dropping 
struct fields using qualified names
   Updated expected results in pipe-operators.sql.out and 
analyzer-results/pipe-operators.sql.out
   
   Test 2:
   
   spark.sql("""
        |   SELECT 2 AS lhs_a, 1 AS lhs_b
        |   |> AS lhs
        |   |> JOIN (VALUES (2, 1)) AS rhs(a, b)
        |        ON lhs.lhs_a = rhs.a
        |   |> Drop lhs.lhs_a
        | """).show()
   
   ### 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