dongjoon-hyun opened a new pull request, #53361:
URL: https://github.com/apache/spark/pull/53361

   ### What changes were proposed in this pull request?
   
   This PR aims to promote `RequiresDistributionAndOrdering` and its required 
interfaces to `Evolving` from `Experimental`.
   
   ### Why are the changes needed?
   
   Since Apache Spark 3.2.0, `RequiresDistributionAndOrdering` and its required 
interfaces have been served stably over 4 years like the following.
   - #30706
   
   | Interface | Description |
   | - | - |
   | org.apache.spark.sql.connector.distributions.ClusteredDistribution | 
Unchange |
   | org.apache.spark.sql.connector.distributions.Distribution | Unchange |
   | org.apache.spark.sql.connector.distributions.Distributions | Unchange |
   | org.apache.spark.sql.connector.distributions.OrderedDistribution | 
Unchange |
   | org.apache.spark.sql.connector.distributions.UnspecifiedDistribution | 
Unchange |
   | org.apache.spark.sql.connector.expressions.NullOrdering | No Functional 
Change |
   | org.apache.spark.sql.connector.expressions.SortDirection | No Functional 
Change |
   | org.apache.spark.sql.connector.expressions.SortOrder | No Functional 
Change |
   | org.apache.spark.sql.connector.write.RequiresDistributionAndOrdering | 
Stably Evolving |
   
   In Apache Spark 4.2.0, we had better promote this as `Evolving` because 
these are no longer `Experimental`.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   Pass the CIs and manual review.
   
   ### 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