lidavidm opened a new pull request #31738:
URL: https://github.com/apache/spark/pull/31738


   <!--
   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'.
   -->
   
   ### What changes were proposed in this pull request?
   
   As a followup for #29818, document caveats of using the Arrow selfDestruct 
option in toPandas, which include:
   - toPandas() may be slower;
   - the resulting dataframe may not support some Pandas operations due to 
immutable backing arrays.
   
   ### Why are the changes needed?
   
   This will hopefully reduce user confusion as with SPARK-34463.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes - documentation is updated and a config setting description is updated 
to clearly indicate the config is experimental.
   
   ### How was this patch tested?
   This is a documentation-only change.
   


----------------------------------------------------------------
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.

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