Abhishek-Mohan opened a new pull request, #7152:
URL: https://github.com/apache/datafusion-comet/pull/7152

   > [!NOTE]
   > **Draft / placeholder.** This branch has only an empty commit for now. The 
content will follow after the style guide PR merges.
   
   ## Which issue does this PR close?
   
   Closes #4419.
   
   ## Rationale for this change
   
   #4419 proposes a shared vocabulary for Comet's docs, mainly replacing the 
vague use of "native" with specific terms. The README and three user guides 
already use it (#4428, #4650, #4651, #4652), and the style guide PR writes the 
rules down. Several contributor-guide and about pages still use the old, 
ambiguous wording, such as "runs natively" and "the native path".
   
   ## What changes are included in this PR?
   
   Planned: apply the #4419 vocabulary to the remaining pages, following the 
same approach as #4650 to #4652:
   
   - `docs/source/contributor-guide/plugin_overview.md`
   - `docs/source/contributor-guide/native_shuffle.md`
   - `docs/source/contributor-guide/jvm_shuffle.md`
   - `docs/source/about/gluten_comparison.md`
   - leftover wording in 
`docs/source/user-guide/latest/understanding-comet-plans.md`
   
   If the diff grows large, I will split it into one PR per page, as was done 
for the earlier pages.
   
   Not included: operator renames such as `CometExchange`. They change plan 
output and test files, and need agreement on #4419 first.
   
   ## How are these changes tested?
   
   Docs only. I will build the docs locally and check that the changed pages 
render and their links still work.
   
   AI assistance: OpenCode is being used to help draft this 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.

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