Skip to content

Commit e8b8000

Browse files
docs: limit the N2 scan compounds to Rust-implemented scans
A dry run read native cache scan as allowed by N2, but the in-memory cache scan runs on the JVM. N2 now says the scan and writer compounds apply only to Rust-implemented ones. Generated-by: OpenCode
1 parent ad78e9b commit e8b8000

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎docs/source/contributor-guide/style_guide.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,8 +90,9 @@ is meant. Name the meaning instead.
9090
- **N2.** These compounds are allowed everywhere, because the second part fixes the meaning:
9191
_native Rust_; _native shuffle_ and _the native shuffle path_ (the counterpart of _JVM shuffle_,
9292
which need not appear beside it); "native", optionally followed by a format, followed by _scan_,
93-
_reader_, _write_, or _writer_, for Comet's Rust scans and writers (_native scan_, _native Parquet
94-
reader_, _native Iceberg write_); _native memory_ and _native library_ (the terms Comet's own log
93+
_reader_, _write_, or _writer_, only for Comet's Rust-implemented scans and writers (_native scan_,
94+
_native Parquet reader_, _native Iceberg write_), not for a JVM-side scan such as
95+
`CometInMemoryTableScanExec`; _native memory_ and _native library_ (the terms Comet's own log
9596
lines use); _Arrow-native_ (T7); _Native_ as the expression kind (T6); and _native implementation_
9697
of an expression, meaning its Rust implementation.
9798
- **N3.** In the contributor guide, "native" before a code noun is also allowed when it means the

0 commit comments

Comments
 (0)