[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACJ3J9EZ6THF2WN64YQ9G9":3,"skill-same:01M6ACJ3J9EZ6THF2WN64YQ9G9":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6ACJ3J9EZ6THF2WN64YQ9G9","implement-comet-expression",null,"Use when implementing a new Spark expression in DataFusion Comet. Walks through cloning latest Spark master to study the canonical implementation, checking the upstream datafusion-spark crate before writing native code, building the Comet serde and Rust wire-up from the contributor guide, then running audit-comet-expression to drive a test-coverage iteration loop.","apache\u002Fdatafusion-comet","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACHX42TPNCR8TQJEAR8J5J",1322,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fimplement-comet-expression\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"implement","implement comet expression","expression","use","new","running","when","contributor","implementing","iteration","upstream","study","up","writing","coverage","loop","datafusion","code","spark","test","rust","2026-11-10 10:12:30",false,"---\nname: implement-comet-expression\ndescription: Use when implementing a new Spark expression in DataFusion Comet. Walks through cloning latest Spark master to study the canonical implementation, checking the upstream datafusion-spark crate before writing native code, building the Comet serde and Rust wire-up from the contributor guide, then running audit-comet-expression to drive a test-coverage iteration loop.\nargument-hint: \u003Cexpression-name>\n---\n\n\u003C!--\nLicensed to the Apache Software Foundation (ASF) under one\nor more contributor license agreements.  See the NOTICE file\ndistributed with this work for additional information\nregarding copyright ownership.  The ASF licenses this file\nto you under the Apache License, Version 2.0 (the\n\"License\"); you may not use this file except in compliance\nwith the License.  You may obtain a copy of the License at\n\n  http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\nUnless required by applicable law or agreed to in writing,\nsoftware distributed under the License is distributed on an\n\"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\nKIND, either express or implied.  See the License for the\nspecific language governing permissions and limitations\nunder the License.\n-->\n\nImplement Comet support for the `$ARGUMENTS` Spark expression.\n\n## Background reading\n\nThe contributor guide is the canonical reference. Read these before writing code:\n\n- `docs\u002Fsource\u002Fcontributor-guide\u002Fadding_a_new_expression.md` covers the Scala serde, protobuf, Rust scalar function flow, support levels, shims, and tests.\n- `docs\u002Fsource\u002Fcontributor-guide\u002Fsql-file-tests.md` describes the Comet SQL Tests format.\n- `docs\u002Fsource\u002Fuser-guide\u002Flatest\u002Fexpressions.md` lists the support status for every expression.\n\n## Workflow\n\n### 1. Study the Spark master implementation first\n\nAlways start from the latest Spark `master`. Shallow clone if not already present:\n\n```bash\nif [ ! -d \u002Ftmp\u002Fspark-master ]; then\n  git clone --depth 1 https:\u002F\u002Fgithub.com\u002Fapache\u002Fspark.git \u002Ftmp\u002Fspark-master\nfi\n```\n\nFind the expression class and tests:\n\n```bash\nfind \u002Ftmp\u002Fspark-master\u002Fsql -name \"*.scala\" | \\\n  xargs grep -l \"case class $ARGUMENTS\\b\\|object $ARGUMENTS\\b\" 2>\u002Fdev\u002Fnull\n\nfind \u002Ftmp\u002Fspark-master\u002Fsql -name \"*.scala\" -path \"*\u002Ftest\u002F*\" | \\\n  xargs grep -l \"$ARGUMENTS\" 2>\u002Fdev\u002Fnull\n```\n\nRead the source. Note `inputTypes`, `dataType`, `eval` \u002F `nullSafeEval`, ANSI mode branches, and any `require` guards. These define the contract Comet must match.\n\n### 2. Check for an upstream `datafusion-spark` implementation\n\nBefore writing a Comet-specific native function, check whether the expression is already available in the upstream `datafusion-spark` crate. It is a Spark-compatible function library maintained alongside DataFusion, so its semantics are usually a closer match to Spark than a generic `datafusion-functions` built-in.\n\n```bash\ngrep -rn \"fn name\\|SparkFunctionName\" ~\u002F.cargo\u002Fregistry\u002Fsrc\u002F*\u002Fdatafusion-spark-*\u002Fsrc\u002Ffunction\u002F 2>\u002Fdev\u002Fnull | grep -i \"$ARGUMENTS\"\n```\n\nFunctions are organized as `datafusion_spark::function::\u003Ccategory>::\u003Cname>::Spark\u003CName>`. Existing wire-ups can be found in `native\u002Fcore\u002Fsrc\u002Fexecution\u002Fplanner.rs` (e.g. `SparkDateAdd`, `SparkDateSub`, `SparkCollectSet`).\n\nWhen the upstream implementation matches Spark's semantics, prefer it: register the `ScalarUDF` from `datafusion-spark` rather than re-implementing. This keeps the maintenance burden upstream. If the upstream version is missing, incomplete, or diverges from Spark, fall through to step 3 and write the function locally.\n\n### 3. Implement the initial version\n\nFollow `adding_a_new_expression.md`:\n\n1. Add a `CometExpressionSerde[T]` in the appropriate file under `spark\u002Fsrc\u002Fmain\u002Fscala\u002Forg\u002Fapache\u002Fcomet\u002Fserde\u002F`.\n2. Register it in the matching map in `QueryPlanSerde.scala`.\n3. If the function name collides with a DataFusion built-in that has a different signature, use `scalarFunctionExprToProtoWithReturnType` (see \"When to set the return type explicitly\").\n4. For a new scalar function, add a match case in `native\u002Fspark-expr\u002Fsrc\u002Fcomet_scalar_funcs.rs::create_comet_physical_fun`. If step 2 found an upstream implementation, wire that in. Otherwise implement the function under `native\u002Fspark-expr\u002Fsrc\u002F`.\n5. If Spark's behavior differs between versions, resolve the version in the serde or a shim and pass native code a parameter named for the behavior (`wrap_second_millisecond_overflow`), not the version (`spark_420_plus`). See \"Name the behavior, not the Spark version\" in `adding_a_new_expression.md`.\n6. Add at least one Comet SQL Test at `spark\u002Fsrc\u002Ftest\u002Fresources\u002Fsql-tests\u002Fexpressions\u002F\u003Ccategory>\u002F$ARGUMENTS.sql` exercising column references, literals, and `NULL`.\n\nBuild and smoke-test:\n\n```bash\nmake\n.\u002Fmvnw test -Dsuites=\"org.apache.comet.CometSqlFileTestSuite $ARGUMENTS\" -Dtest=none\n```\n\n### 4. Run the audit skill\n\nOnce the initial implementation passes its smoke test, run the `audit-comet-expression` skill on `$ARGUMENTS`. It compares the implementation and tests against Spark 3.4.3, 3.5.8, and 4.0.1 and produces a prioritized list of gaps.\n\n### 5. Implement audit-recommended tests and iterate\n\nAdd the missing test cases the audit recommends, then re-run the targeted suite:\n\n```bash\n.\u002Fmvnw test -Dsuites=\"org.apache.comet.CometSqlFileTestSuite $ARGUMENTS\" -Dtest=none\n```\n\nSurface findings to the user and ask whether the coverage is sufficient. Continue iterating (adding tests, fixing bugs, refining `getSupportLevel` \u002F `getIncompatibleReasons` \u002F `getUnsupportedReasons`) until the user confirms they are happy.\n\n### 6. Final checks\n\nBefore opening a PR:\n\n```bash\nmake format\ncd native && cargo clippy --all-targets --workspace -- -D warnings\n```\n\n### 7. Open the PR\n\nUse the repo's PR template at `.github\u002Fpull_request_template.md` and fill in every section: \"Which issue does this PR close?\", \"Rationale for this change\", \"What changes are included in this PR?\", and \"How are these changes tested?\". Do not add a separate test plan section.\n\nIn the \"What changes are included in this PR?\" section, add a brief note that the `implement-comet-expression` skill was used to scaffold the implementation, so reviewers know which workflow produced the change.\n","\u003C!--\nLicensed to the Apache Software Foundation (ASF) under one\nor more contributor license agreements.  See the NOTICE file\ndistributed with this work for additional information\nregarding copyright ownership.  The ASF licenses this file\nto you under the Apache License, Version 2.0 (the\n\"License\"); you may not use this file except in compliance\nwith the License.  You may obtain a copy of the License at\n\n  http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\nUnless required by applicable law or agreed to in writing,\nsoftware distributed under the License is distributed on an\n\"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\nKIND, either express or implied.  See the License for the\nspecific language governing permissions and limitations\nunder the License.\n-->\n\nImplement Comet support for the `$ARGUMENTS` Spark expression.\n\n## Background reading\n\nThe contributor guide is the canonical reference. Read these before writing code:\n\n- `docs\u002Fsource\u002Fcontributor-guide\u002Fadding_a_new_expression.md` covers the Scala serde, protobuf, Rust scalar function flow, support levels, shims, and tests.\n- `docs\u002Fsource\u002Fcontributor-guide\u002Fsql-file-tests.md` describes the Comet SQL Tests format.\n- `docs\u002Fsource\u002Fuser-guide\u002Flatest\u002Fexpressions.md` lists the support status for every expression.\n\n## Workflow\n\n### 1. Study the Spark master implementation first\n\nAlways start from the latest Spark `master`. Shallow clone if not already present:\n\n```bash\nif [ ! -d \u002Ftmp\u002Fspark-master ]; then\n  git clone --depth 1 https:\u002F\u002Fgithub.com\u002Fapache\u002Fspark.git \u002Ftmp\u002Fspark-master\nfi\n```\n\nFind the expression class and tests:\n\n```bash\nfind \u002Ftmp\u002Fspark-master\u002Fsql -name \"*.scala\" | \\\n  xargs grep -l \"case class $ARGUMENTS\\b\\|object $ARGUMENTS\\b\" 2>\u002Fdev\u002Fnull\n\nfind \u002Ftmp\u002Fspark-master\u002Fsql -name \"*.scala\" -path \"*\u002Ftest\u002F*\" | \\\n  xargs grep -l \"$ARGUMENTS\" 2>\u002Fdev\u002Fnull\n```\n\nRead the source. Note `inputTypes`, `dataType`, `eval` \u002F `nullSafeEval`, ANSI mode branches, and any `require` guards. These define the contract Comet must match.\n\n### 2. Check for an upstream `datafusion-spark` implementation\n\nBefore writing a Comet-specific native function, check whether the expression is already available in the upstream `datafusion-spark` crate. It is a Spark-compatible function library maintained alongside DataFusion, so its semantics are usually a closer match to Spark than a generic `datafusion-functions` built-in.\n\n```bash\ngrep -rn \"fn name\\|SparkFunctionName\" ~\u002F.cargo\u002Fregistry\u002Fsrc\u002F*\u002Fdatafusion-spark-*\u002Fsrc\u002Ffunction\u002F 2>\u002Fdev\u002Fnull | grep -i \"$ARGUMENTS\"\n```\n\nFunctions are organized as `datafusion_spark::function::\u003Ccategory>::\u003Cname>::Spark\u003CName>`. Existing wire-ups can be found in `native\u002Fcore\u002Fsrc\u002Fexecution\u002Fplanner.rs` (e.g. `SparkDateAdd`, `SparkDateSub`, `SparkCollectSet`).\n\nWhen the upstream implementation matches Spark's semantics, prefer it: register the `ScalarUDF` from `datafusion-spark` rather than re-implementing. This keeps the maintenance burden upstream. If the upstream version is missing, incomplete, or diverges from Spark, fall through to step 3 and write the function locally.\n\n### 3. Implement the initial version\n\nFollow `adding_a_new_expression.md`:\n\n1. Add a `CometExpressionSerde[T]` in the appropriate file under `spark\u002Fsrc\u002Fmain\u002Fscala\u002Forg\u002Fapache\u002Fcomet\u002Fserde\u002F`.\n2. Register it in the matching map in `QueryPlanSerde.scala`.\n3. If the function name collides with a DataFusion built-in that has a different signature, use `scalarFunctionExprToProtoWithReturnType` (see \"When to set the return type explicitly\").\n4. For a new scalar function, add a match case in `native\u002Fspark-expr\u002Fsrc\u002Fcomet_scalar_funcs.rs::create_comet_physical_fun`. If step 2 found an upstream implementation, wire that in. Otherwise implement the function under `native\u002Fspark-expr\u002Fsrc\u002F`.\n5. If Spark's behavior differs between versions, resolve the version in the serde or a shim and pass native code a parameter named for the behavior (`wrap_second_millisecond_overflow`), not the version (`spark_420_plus`). See \"Name the behavior, not the Spark version\" in `adding_a_new_expression.md`.\n6. Add at least one Comet SQL Test at `spark\u002Fsrc\u002Ftest\u002Fresources\u002Fsql-tests\u002Fexpressions\u002F\u003Ccategory>\u002F$ARGUMENTS.sql` exercising column references, literals, and `NULL`.\n\nBuild and smoke-test:\n\n```bash\nmake\n.\u002Fmvnw test -Dsuites=\"org.apache.comet.CometSqlFileTestSuite $ARGUMENTS\" -Dtest=none\n```\n\n### 4. Run the audit skill\n\nOnce the initial implementation passes its smoke test, run the `audit-comet-expression` skill on `$ARGUMENTS`. It compares the implementation and tests against Spark 3.4.3, 3.5.8, and 4.0.1 and produces a prioritized list of gaps.\n\n### 5. Implement audit-recommended tests and iterate\n\nAdd the missing test cases the audit recommends, then re-run the targeted suite:\n\n```bash\n.\u002Fmvnw test -Dsuites=\"org.apache.comet.CometSqlFileTestSuite $ARGUMENTS\" -Dtest=none\n```\n\nSurface findings to the user and ask whether the coverage is sufficient. Continue iterating (adding tests, fixing bugs, refining `getSupportLevel` \u002F `getIncompatibleReasons` \u002F `getUnsupportedReasons`) until the user confirms they are happy.\n\n### 6. Final checks\n\nBefore opening a PR:\n\n```bash\nmake format\ncd native && cargo clippy --all-targets --workspace -- -D warnings\n```\n\n### 7. Open the PR\n\nUse the repo's PR template at `.github\u002Fpull_request_template.md` and fill in every section: \"Which issue does this PR close?\", \"Rationale for this change\", \"What changes are included in this PR?\", and \"How are these changes tested?\". Do not add a separate test plan section.\n\nIn the \"What changes are included in this PR?\" section, add a brief note that the `implement-comet-expression` skill was used to scaffold the implementation, so reviewers know which workflow produced the change.\n",{"name":5,"description":7,"argument-hint":45},"\u003Cexpression-name>","main","7deeba21a42e4a9cd34f43e7ed6e960e4e851b26",".ai\u002Fskills\u002Fimplement-comet-expression",418,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet","https:\u002F\u002Fdatafusion.apache.org\u002Fcomet","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-15 03:15:20",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add apache\u002Fdatafusion-comet --skill implement-comet-expression",{"tool":61,"command":62},"bunx","bunx skills add apache\u002Fdatafusion-comet --skill implement-comet-expression",{"tool":64,"command":65},"pnpm","pnpm dlx skills add apache\u002Fdatafusion-comet --skill implement-comet-expression","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fimplement-comet-expression\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"OWNERSHIP","OTHER","其他",13,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fintellij-community\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fkotlin-ui-swing-component-architecture\u002FOWNERSHIP",[76,102,127,148,165,176],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":87,"publishedAt":40},"01M6ACJR50ZS7F1QX58JEKCGVM","wire-datafusion-function","Use when wiring an existing DataFusion or datafusion-spark function into Comet for a Spark expression. Identifies the right wiring pattern (one-line passthrough, datafusion-spark UDF registration, or custom serde with input massaging \u002F restrictions), applies the Scala serde, registers the UDF in jni_api when needed, and adds SQL file tests. Assumes the function already exists upstream — if not, switch to `implement-comet-expression`.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fwire-datafusion-function\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[35,88,89,90,19,37,91,92,93,29,94,21,95,22,96,25,97,98,99,100,101],"wire datafusion function","sql","scala","registration","switch","for","custom","tests","Existing","file","api","wiring","with","name",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":40},"01M6ACJPDDPND6FHE2PC1CJ4D3","suggest-native-expression","Use when picking the next Spark expression to implement natively in Comet, or when asked whether a specific codegen-dispatched expression is worth a native Rust implementation. Scores the candidate on how likely a native path can be 100% Spark-compatible and how much throughput or allocation it would save versus the JVM codegen dispatcher, records the verdict in the per-expression audit log so disqualified candidates are not re-litigated, and files a GitHub issue for the recommendation.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fsuggest-native-expression\u002FSKILL.md",[],[109,21,110,111,112,39,19,37,113,114,25,115,116,117,118,119,120,121,122,123,124,125,126],"suggest native expression","native","dispatcher","github","re","files","candidate","log","jvm","next","how","audit","audit log","allocation","issue","throughput","path","save",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":40},"01M6ACJMHPEN7E76VPKC3P4X6C","review-comet-shuffle-pr","Use when reviewing a DataFusion Comet pull request that touches native or JVM columnar shuffle, the shuffle writers and readers, partitioning, the Arrow IPC block format, shuffle compression, or the Celeborn integration. Load alongside review-comet-pr.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Freview-comet-shuffle-pr\u002FSKILL.md",[],[134,135,136,137,138,35,139,22,140,25,141,142,117,110,143,144,145,146,147],"review comet shuffle pr","pr","review","pull","pull request","arrow","load","ipc","number","request","format","integration","block","compression",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":40},"01M6ACJHX8BES7ZNNRNVCQ4QWE","review-comet-pr","Use when reviewing a DataFusion Comet pull request. Covers the workflow that applies to every PR and routes to the area-specific review skills for expressions, FFI, memory management, shuffle, Iceberg writes, and documentation. Provides guidance to a human reviewer rather than posting comments.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Freview-comet-pr\u002FSKILL.md",[],[135,136,155,137,156,138,157,35,158,159,25,142,160,161,143,162,93,22,163,164],"review comet pr","iceberg","memory","workflow","documentation","reviewer","human","posting","review skills","comments",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":40},"01M6ACJFM0QS61Z1RW516HXN2M","review-comet-memory-pr","Use when reviewing a DataFusion Comet pull request that touches memory pools, memory reservations, spilling, the Spark TaskMemoryManager bridge, allocators, or memory-related configuration. Load alongside review-comet-pr.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Freview-comet-memory-pr\u002FSKILL.md",[],[135,157,172,136,137,138,35,37,173,174,22,140,25,142,143,175],"review comet memory pr","bridge","reservations","configuration",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":40},"01M6ACJCV64V0FZPMVXDE2K3DX","review-comet-iceberg-write-pr","Use when reviewing a DataFusion Comet pull request that touches Iceberg writes, the split-operator write plan (IcebergWriteStrategy, IcebergWriteExec, IcebergCommitExec), the native Iceberg writer (CometIcebergWriteExec, iceberg_write.rs, iceberg_partition_path.rs), its eligibility gate (CometIcebergNativeWrite), or the iceberg-rust pin. Load alongside review-comet-pr.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-comet\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Freview-comet-iceberg-write-pr\u002FSKILL.md",[],[135,156,183,136,184,137,138,35,39,185,186,187,22,140,188,25,142,189,190,110],"review comet iceberg write pr","write","writer","write plan","partition","pin","split","plan"]