You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@datafusion.apache.org by "Abhishek-Mohan (via GitHub)" <gi...@apache.org> on 2026/10/22 00:14:27 UTC

[PR] docs: add a terminology style guide for contributor docs [datafusion-comet]

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

   > [!NOTE]
   > **Draft / placeholder.** This branch has only an empty commit for now. The content will follow.
   
   ## Which issue does this PR close?
   
   Part of #4419.
   
   ## Rationale for this change
   
   #4419 proposes a shared vocabulary for Comet's docs, mainly replacing the vague use of "native" with specific terms such as *Rust-implemented*, *Arrow-native* and *Comet pipeline*. Several user guides already use this vocabulary (#4428, #4650, #4651, #4652), but the rules are not written down anywhere in the docs. Contributors have to read the issue to find them, and the docs-review skill proposed in #4420 has no document to check against.
   
   ## What changes are included in this PR?
   
   Planned:
   
   - A new contributor-guide page, `docs/source/contributor-guide/style_guide.md`, that writes down the vocabulary from #4419: pipeline membership, implementation language and data format, the rule for "native" with the allowed compound forms, and the reserved meaning of "vectorized".
   - A link to the page from the contributor guide index.
   
   Not included: rewording other pages (follow-up PR), operator renames (need separate discussion on #4419), and the docs-review skill (#4420).
   
   ## How are these changes tested?
   
   Docs only. I will build the docs locally and check that the new page renders and is linked from the contributor guide index.
   
   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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "Abhishek-Mohan (via GitHub)" <gi...@apache.org>.
Abhishek-Mohan commented on code in PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#discussion_r4409626859


##########
docs/source/about/gluten_comparison.md:
##########
@@ -139,33 +141,33 @@ Comet relies on the full Spark SQL test suite (consisting of more than 24,000 te
 integration tests to ensure compatibility with Spark. Features that are known to have compatibility differences with
 Spark are disabled by default, but users can opt in. See the [Comet Compatibility Guide] for more information.
 
-[Comet Compatibility Guide]: https://datafusion.apache.org/comet/user-guide/latest/compatibility/index.html
+[Comet Compatibility Guide]: /user-guide/latest/compatibility/index.md

Review Comment:
   > [!NOTE]
   > πŸ€– **Claude Opus 5.5 responding on behalf of @Abhishek-Mohan**
   
   No effect on publishing. Sphinx resolves `/user-guide/latest/compatibility/index.md` to the relative link `../user-guide/latest/compatibility/index.html` in the built page, the same form `main` already uses for four other links on this page. A base-vs-head docs build shows no new warnings, and the build now warns if the target page moves.



-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "Abhishek-Mohan (via GitHub)" <gi...@apache.org>.
Abhishek-Mohan commented on code in PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#discussion_r4385080429


##########
docs/source/contributor-guide/plugin_overview.md:
##########
@@ -127,10 +140,26 @@ In the native code there is a `PhysicalPlanner` struct (in `planner.rs`) which c
 Apache DataFusion `ExecutionPlan`. In some cases, Comet provides specialized physical operators and expressions to
 override the DataFusion versions to ensure compatibility with Apache Spark.
 
-The leaf nodes in the physical plan are always `ScanExec`. Each JVM-sourced input is exported once as an
+Not every expression in a Rust plan runs in Rust. When an expression has no Rust implementation, or its Rust
+implementation does not match Spark for the given input, its serde can route it through the JVM codegen dispatcher
+instead of falling back to Spark (see the
+[Implementation legend](../user-guide/latest/expressions.md#implementation-legend)). The Rust plan then evaluates the
+expression with `JvmScalarUdfExpr`, which passes each batch's input columns through JNI and the Arrow C Data Interface
+to `CometUdfBridge`, which hands them to `CometScalaUDFCodegen` on the JVM. There, Spark's own generated code for the expression, compiled into a batch
+kernel by `CometBatchKernelCodegen`, runs over the Arrow vectors and returns an Arrow column. Scala and Java UDFs take
+the same path. The operator around the expression stays Rust-implemented, so this JVM code runs inside the Comet
+pipeline. `spark.comet.exec.scalaUDF.codegen.enabled`, which is on by default, turns the dispatcher on. When it is off,
+these expressions fall back to Spark.
+
+A leaf node in the physical plan that takes Arrow batches from the JVM is a `ScanExec`. Each such input is exported once as an
 [Arrow C Stream](https://arrow.apache.org/docs/format/CStreamInterface.html) (`org.apache.arrow.c.ArrowArrayStream`),
 and `ScanExec` pulls each input batch through a single C callback rather than making a JNI call per batch. The
-input could be a Comet native Parquet scan, a Spark exchange, or another native plan.
+input could be a broadcast, a shuffle read decoded through JNI and imported into the JVM, the output of
+`CometSparkToColumnarExec`, or the output of an earlier Comet block. When direct shuffle read is enabled and the input
+is a Comet shuffle whose output types Comet supports, the input is instead a `ShuffleScanExec`, which pulls compressed

Review Comment:
   Fixed in 3c982c8cf.



##########
docs/source/user-guide/latest/understanding-comet-plans.md:
##########
@@ -94,6 +94,8 @@ They serve different purposes and produce output in different places.
 | `spark.comet.explain.codegen.enabled`      | `ExtendedExplainInfo` / SQL UI     | A single `[COMET-INFO: JVM codegen dispatcher: <name1>, <name2>, ...]` segment naming each expression on the operator that was routed through the JVM codegen dispatcher. |
 | `spark.comet.explain.format`               | Spark SQL UI (Spark 4.0 and newer) | Annotated plan or fallback-reason list, depending on `verbose` (default) or `fallback` value.                                                                             |
 | `spark.comet.explain.native.enabled`       | Executor logs, per task            | The DataFusion plan with metrics, useful for inspecting Rust execution.                                                                                                   |
+| `spark.comet.explain.planOnly.enabled`     | Driver log                         | The Comet plan and coverage summary, prefixed `[Comet plan-only]`, while Spark runs the original plan.                                                                    |
+| `spark.comet.explain.rules`                | Driver log                         | Each plan transformation that Comet's planner rules make.                                                                                                                 |

Review Comment:
   Fixed in 3c982c8cf.



##########
docs/source/contributor-guide/jvm_shuffle.md:
##########
@@ -65,7 +65,7 @@ returns an `RDD[InternalRow]`. The rows flow directly to the JVM shuffle writers
 
 ### Comet Columnar Input
 
-When the child plan is a Comet native operator (e.g., `CometHashAggregate`) but JVM shuffle is selected
+When the child plan is a Comet operator (e.g., `CometHashAggregate`) but JVM shuffle is selected

Review Comment:
   Fixed in 3c982c8cf.



##########
docs/source/contributor-guide/native_shuffle.md:
##########
@@ -25,33 +25,35 @@ see [JVM Shuffle](jvm_shuffle.md).
 
 ## Overview
 
-Native shuffle takes columnar input directly from Comet native operators and performs partitioning,
+Native shuffle takes Arrow batches directly from Comet operators and performs partitioning,
 encoding, and writing in native Rust code. This avoids the columnar-to-row-to-columnar conversion
 overhead that JVM shuffle incurs.
 
 ```
-Comet Native (columnar) β†’ Native Shuffle β†’ Arrow IPC β†’ columnar
+Comet operator (Arrow batches) β†’ Native Shuffle β†’ Arrow IPC β†’ columnar
 ```
 
 Compare this to JVM shuffle's data path:
 
 ```
-Comet Native (columnar) β†’ ColumnarToRowExec β†’ rows β†’ JVM Shuffle β†’ Arrow IPC β†’ columnar
+Comet operator (Arrow batches) β†’ ColumnarToRowExec β†’ rows β†’ JVM Shuffle β†’ Arrow IPC β†’ columnar
 ```
 
 When `RevertNativeForTransitionHeavyStages` restores the map stage to Spark execution, the
-native exchange stays in place. Its input still needs Arrow-backed Comet vectors, even if the
-restored Spark operator supports columnar output. The rule adds `CometSparkToColumnarExec` to
-convert either Spark rows or Spark columnar batches to Arrow before the native shuffle consumes
-them. Spark's `RowToColumnarExec` alone does not satisfy this input contract.
+native shuffle exchange usually stays in place. Its input still needs Arrow-backed Comet vectors,
+even if the restored Spark operator supports columnar output. The rule adds `CometSparkToColumnarExec`
+to convert either Spark rows or Spark columnar batches to Arrow before the native shuffle consumes
+them. Spark's `RowToColumnarExec` alone does not satisfy this input contract. The exception is a
+native shuffle whose input was converted by `spark.comet.convert.shuffleInput.enabled`: the rule
+switches it back to JVM columnar shuffle, which reads the restored stage's rows.
 
 ## When Native Shuffle is Used
 
 Native shuffle (`CometExchange`) is selected when all of the following conditions are met:
 
-1. **Shuffle mode allows native**: `spark.comet.shuffle.mode` is `native` or `auto`.
+1. **Shuffle mode allows native shuffle**: `spark.comet.shuffle.mode` is `native` or `auto`.
 
-2. **Child plan is a Comet native operator**: The child must be a `CometPlan` that produces
+2. **Child plan is a Comet operator**: The child must be a `CometPlan` that produces

Review Comment:
   Fixed in 3c982c8cf.



-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "sunchao (via GitHub)" <gi...@apache.org>.
sunchao commented on code in PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#discussion_r4366956694


##########
docs/source/contributor-guide/jvm_shuffle.md:
##########
@@ -65,7 +65,7 @@ returns an `RDD[InternalRow]`. The rows flow directly to the JVM shuffle writers
 
 ### Comet Columnar Input
 
-When the child plan is a Comet native operator (e.g., `CometHashAggregate`) but JVM shuffle is selected
+When the child plan is a Comet operator (e.g., `CometHashAggregate`) but JVM shuffle is selected

Review Comment:
   [P2] Broadening this paragraph to any Comet operator makes the conversion diagram incorrect for `CometSparkToColumnarExec` over Spark rows. In JVM shuffle mode, `child.execute()` forwards the underlying rows directly. The diagram assigns an Arrow-to-row conversion cost to a path that produces no input Arrow batch. Scope the diagram to children using `CometExec.doExecute()` and describe the row-forwarding bridge separately.
   
   Evidence: A Spark 4.1.3 probe requested `SinglePartition` over `CometSparkToColumnarExec(RDDScanExec)` with `spark.comet.shuffle.mode=jvm`. The planner selected `CometColumnarExchange`. Consuming its `inputRDD` returned both rows while the bridge’s `numOutputBatches` remained zero. [Bridge implementation](https://github.com/apache/datafusion-comet/blob/56396e38e2dd066e01256201b6b3dc4772dec970/spark/src/main/scala/org/apache/spark/sql/comet/CometSparkToColumnarExec.scala#L43-L61)



##########
docs/source/user-guide/latest/understanding-comet-plans.md:
##########
@@ -94,6 +94,8 @@ They serve different purposes and produce output in different places.
 | `spark.comet.explain.codegen.enabled`      | `ExtendedExplainInfo` / SQL UI     | A single `[COMET-INFO: JVM codegen dispatcher: <name1>, <name2>, ...]` segment naming each expression on the operator that was routed through the JVM codegen dispatcher. |
 | `spark.comet.explain.format`               | Spark SQL UI (Spark 4.0 and newer) | Annotated plan or fallback-reason list, depending on `verbose` (default) or `fallback` value.                                                                             |
 | `spark.comet.explain.native.enabled`       | Executor logs, per task            | The DataFusion plan with metrics, useful for inspecting Rust execution.                                                                                                   |
+| `spark.comet.explain.planOnly.enabled`     | Driver log                         | The Comet plan and coverage summary, prefixed `[Comet plan-only]`, while Spark runs the original plan.                                                                    |
+| `spark.comet.explain.rules`                | Driver log                         | Each plan transformation that Comet's planner rules make.                                                                                                                 |

Review Comment:
   [P2] The new row promises a driver-log entry for every planner transformation. `RevertNativeForTransitionHeavyStages` can remove Comet operators without emitting a rule diff, so the log omits the rewrite someone investigating that fallback needs. Describe the before/after output from `CometScanRule`, `CometExecRule`, and `EliminateRedundantTransitions`, and point readers to `spark.comet.explain.fallback.log.enabled` for the reversion reason.
   
   Evidence: On Spark 4.1.3 with INFO logging, `spark.comet.explain.rules=true`, transition reversion enabled, and `maxTransitions=0`, the rule rewrote `ColumnarToRow(CometLocalTableScan)` to `LocalTableScan` with zero `Applying Rule` entries. An `EliminateRedundantTransitions` control emitted its rule diff. Enabling fallback-reason logging produced `Stage reverted: 1 C2R transitions exceed threshold 0`. [Reversion rule](https://github.com/apache/datafusion-comet/blob/56396e38e2dd066e01256201b6b3dc4772dec970/spark/src/main/scala/org/apache/comet/rules/RevertNativeForTransitionHeavyStages.scala#L122-L152)



##########
docs/source/contributor-guide/native_shuffle.md:
##########
@@ -25,33 +25,35 @@ see [JVM Shuffle](jvm_shuffle.md).
 
 ## Overview
 
-Native shuffle takes columnar input directly from Comet native operators and performs partitioning,
+Native shuffle takes Arrow batches directly from Comet operators and performs partitioning,
 encoding, and writing in native Rust code. This avoids the columnar-to-row-to-columnar conversion
 overhead that JVM shuffle incurs.
 
 ```
-Comet Native (columnar) β†’ Native Shuffle β†’ Arrow IPC β†’ columnar
+Comet operator (Arrow batches) β†’ Native Shuffle β†’ Arrow IPC β†’ columnar
 ```
 
 Compare this to JVM shuffle's data path:
 
 ```
-Comet Native (columnar) β†’ ColumnarToRowExec β†’ rows β†’ JVM Shuffle β†’ Arrow IPC β†’ columnar
+Comet operator (Arrow batches) β†’ ColumnarToRowExec β†’ rows β†’ JVM Shuffle β†’ Arrow IPC β†’ columnar
 ```
 
 When `RevertNativeForTransitionHeavyStages` restores the map stage to Spark execution, the
-native exchange stays in place. Its input still needs Arrow-backed Comet vectors, even if the
-restored Spark operator supports columnar output. The rule adds `CometSparkToColumnarExec` to
-convert either Spark rows or Spark columnar batches to Arrow before the native shuffle consumes
-them. Spark's `RowToColumnarExec` alone does not satisfy this input contract.
+native shuffle exchange usually stays in place. Its input still needs Arrow-backed Comet vectors,
+even if the restored Spark operator supports columnar output. The rule adds `CometSparkToColumnarExec`
+to convert either Spark rows or Spark columnar batches to Arrow before the native shuffle consumes
+them. Spark's `RowToColumnarExec` alone does not satisfy this input contract. The exception is a
+native shuffle whose input was converted by `spark.comet.convert.shuffleInput.enabled`: the rule
+switches it back to JVM columnar shuffle, which reads the restored stage's rows.
 
 ## When Native Shuffle is Used
 
 Native shuffle (`CometExchange`) is selected when all of the following conditions are met:
 
-1. **Shuffle mode allows native**: `spark.comet.shuffle.mode` is `native` or `auto`.
+1. **Shuffle mode allows native shuffle**: `spark.comet.shuffle.mode` is `native` or `auto`.
 
-2. **Child plan is a Comet native operator**: The child must be a `CometPlan` that produces
+2. **Child plan is a Comet operator**: The child must be a `CometPlan` that produces

Review Comment:
   [P2] The broader child criterion predicts `CometExchange` when Celeborn sees a `SinglePartition` exchange over an already-unwrapped `CometSparkToColumnarExec`. Even in explicit `native` mode with a supported integer schema, Celeborn declines that child and retains Spark’s exchange. Distinguish the local manager’s `CometPlan` check from Celeborn’s requirement for a `CometNativeExec` at selection time.
   
   Evidence: A Spark 4.1.3 Celeborn planning probe returned `None` for the columnar bridge with reason `Celeborn native shuffle requires a CometNativeExec child`. With the same schema and partitioning, a `CometNativeExec` control returned `Some(CometNativeShuffle)`. The repository test also asserts that the unwrapped case retains `ShuffleExchangeExec`. [Planner gate](https://github.com/apache/datafusion-comet/blob/56396e38e2dd066e01256201b6b3dc4772dec970/spark/src/main/scala/org/apache/spark/sql/comet/execution/shuffle/CometShuffleExchangeExec.scala#L512-L536) Β· [Planning regression](https://github.com/apache/datafusion-comet/blob/56396e38e2dd066e01256201b6b3dc4772dec970/spark/src/test/scala/org/apache/spark/sql/comet/execution/shuffle/CometCelebornShufflePlanningSuite.scala#L251-L265)



##########
docs/source/contributor-guide/plugin_overview.md:
##########
@@ -127,10 +140,26 @@ In the native code there is a `PhysicalPlanner` struct (in `planner.rs`) which c
 Apache DataFusion `ExecutionPlan`. In some cases, Comet provides specialized physical operators and expressions to
 override the DataFusion versions to ensure compatibility with Apache Spark.
 
-The leaf nodes in the physical plan are always `ScanExec`. Each JVM-sourced input is exported once as an
+Not every expression in a Rust plan runs in Rust. When an expression has no Rust implementation, or its Rust
+implementation does not match Spark for the given input, its serde can route it through the JVM codegen dispatcher
+instead of falling back to Spark (see the
+[Implementation legend](../user-guide/latest/expressions.md#implementation-legend)). The Rust plan then evaluates the
+expression with `JvmScalarUdfExpr`, which passes each batch's input columns through JNI and the Arrow C Data Interface
+to `CometUdfBridge`, which hands them to `CometScalaUDFCodegen` on the JVM. There, Spark's own generated code for the expression, compiled into a batch
+kernel by `CometBatchKernelCodegen`, runs over the Arrow vectors and returns an Arrow column. Scala and Java UDFs take
+the same path. The operator around the expression stays Rust-implemented, so this JVM code runs inside the Comet
+pipeline. `spark.comet.exec.scalaUDF.codegen.enabled`, which is on by default, turns the dispatcher on. When it is off,
+these expressions fall back to Spark.
+
+A leaf node in the physical plan that takes Arrow batches from the JVM is a `ScanExec`. Each such input is exported once as an
 [Arrow C Stream](https://arrow.apache.org/docs/format/CStreamInterface.html) (`org.apache.arrow.c.ArrowArrayStream`),
 and `ScanExec` pulls each input batch through a single C callback rather than making a JNI call per batch. The
-input could be a Comet native Parquet scan, a Spark exchange, or another native plan.
+input could be a broadcast, a shuffle read decoded through JNI and imported into the JVM, the output of
+`CometSparkToColumnarExec`, or the output of an earlier Comet block. When direct shuffle read is enabled and the input
+is a Comet shuffle whose output types Comet supports, the input is instead a `ShuffleScanExec`, which pulls compressed

Review Comment:
   [P2] With `spark.sql.adaptive.enabled=false` and `spark.comet.shuffle.directRead.enabled=true`, a final aggregate over a Comet hash shuffle with `BIGINT` output still reads through `ScanExec`. The paragraph predicts `ShuffleScanExec`, leading someone profiling the aggregate to expect the Arrow FFI crossing to disappear. Describe direct read as applying when the serialized input is a `ShuffleScan` leaf, and include the bare non-AQE exchange as a `ScanExec` case.
   
   Evidence: A Spark 4.1.3 serializer probe returned `SCAN` for the bare exchange and `SHUFFLE_SCAN` for its AQE stage with the same schema and direct-read setting. The checked-in regression groups a 50-partition range by `id % 997` and asserts those leaf kinds in the final aggregate. [Grouped-aggregate regression](https://github.com/apache/datafusion-comet/blob/56396e38e2dd066e01256201b6b3dc4772dec970/spark/src/test/scala/org/apache/comet/exec/CometNativeShuffleSuite.scala#L1791-L1821)



-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "andygrove (via GitHub) via github" <gi...@datafusion.apache.org>.
andygrove merged PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151


-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "andygrove (via GitHub)" <gi...@apache.org>.
andygrove commented on PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#issuecomment-6483678334

   This looks great @Abhishek-Mohan. I've been reviewing the changes manually. Will finish reviewing tomorrow!


-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "Abhishek-Mohan (via GitHub)" <gi...@apache.org>.
Abhishek-Mohan commented on PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#issuecomment-6476086579

   > [!NOTE]
   > πŸ€– **Claude Opus 5.5 responding on behalf of @Abhishek-Mohan**
   
   @sunchao all four findings are fixed in 3c982c8cf, and `main` is merged in (459c6fe55). Ready for another look.


-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "andygrove (via GitHub)" <gi...@apache.org>.
andygrove commented on code in PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#discussion_r4407238457


##########
docs/source/about/gluten_comparison.md:
##########
@@ -139,33 +141,33 @@ Comet relies on the full Spark SQL test suite (consisting of more than 24,000 te
 integration tests to ensure compatibility with Spark. Features that are known to have compatibility differences with
 Spark are disabled by default, but users can opt in. See the [Comet Compatibility Guide] for more information.
 
-[Comet Compatibility Guide]: https://datafusion.apache.org/comet/user-guide/latest/compatibility/index.html
+[Comet Compatibility Guide]: /user-guide/latest/compatibility/index.md

Review Comment:
   Changing this link format may affect how the site gets published?



-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "Abhishek-Mohan (via GitHub)" <gi...@apache.org>.
Abhishek-Mohan commented on PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#issuecomment-6490460457

   > [!NOTE]
   > πŸ€– **Claude Opus 5.5 responding on behalf of @Abhishek-Mohan**
   
   @comphead all three fixed in 60af6cbc4: the Shuffle Reads paragraph uses the `ShuffleScan` condition, `comet-overview.svg` and `index.md` no longer say native or seamlessly. bc3ffc26c corrects two of the figure labels.


-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org

Re: [PR] docs: add a documentation style guide and apply it to the remaining pages [datafusion-comet]

Posted by "Abhishek-Mohan (via GitHub) via github" <gi...@datafusion.apache.org>.
Abhishek-Mohan commented on PR #7151:
URL: https://github.com/apache/datafusion-comet/pull/7151#issuecomment-6535912881

   > [!NOTE]
   > πŸ€– **Claude Opus 5.5 responding on behalf of @Abhishek-Mohan**
   
   Both done. The scope paragraph now says the rules apply to new and changed text, and that existing pages move over as they are edited. The same change is on #7153. `gluten_comparison.md` says "vectorized query engine" again. #7358 tracks the remaining pages and is linked from #4419.
   
   On CI: since #7311 the pull request checks run on my fork, and they passed on the latest push, including prettier in Preflight ([run](https://github.com/Abhishek-Mohan/datafusion-comet/actions/runs/41145447879)).


-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org