santosh-d3vpl3x opened a new pull request, #37761:
URL: https://github.com/apache/spark/pull/37761

   <!--
   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
        'core/src/main/resources/error/README.md'.
   -->
   
   ### What changes were proposed in this pull request?
   This change adds an ability for code to rename multiple columns in a single 
call. 
   ```scala
   withColumnsRenamed(colsMap: Map[String, String]): DataFrame
   ```
   
   ### Why are the changes needed?
   We have seen that catalyst optimiser struggles with bigger plans. The larger 
contribution to these plans in our setup comes from `withColumnRenamed`, `drop` 
and `withColumn` being called in for loop by unknowing users. `master` branch 
of spark already has a version for handling `withColumns` and `drop` for 
multiple columns. The missing bit of the puzzle is `withColumnRenamed`.
   
   ### Does this PR introduce _any_ user-facing change?
   Yes, adds a method to efficiently rename columns in a single batch.
   
   ### How was this patch tested?
   Added unit tests
   


-- 
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: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to