[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACCS7K3VNRNBFY6PJ7Y2KY":3,"skill-same:01M6ACCS7K3VNRNBFY6PJ7Y2KY":90},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6ACCS7K3VNRNBFY6PJ7Y2KY","hudi-mdt-health",null,"Checks whether an Apache Hudi table's metadata table is healthy -- caught up with the data table, consistent with the files on storage, compacting on schedule, and with a record-level index sized for the table -- by running the HoodieTableHealthChecker utility's metadata-table checks and interpreting its JSON report. Invoke when a user asks whether the metadata table is in sync or lagging, whether file listings from the metadata table can be trusted, why metadata-table compaction is not running, whether the record index has too few file groups, or whether the metadata table needs to be rebuilt.","apache\u002Fhudi","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACCEYWKJPXXQEKM83N9C89",6381,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-mdt-health\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,9,38,39],"hudi","hudi mdt health","health","table","running","when","invoke","for","compaction","utility","listings","files","up","schedule","storage","why","data","file","index","report","sync","2026-11-10 10:12:30",false,"---\nname: hudi-mdt-health\ndescription: Checks whether an Apache Hudi table's metadata table is healthy -- caught up with the data table, consistent with the files on storage, compacting on schedule, and with a record-level index sized for the table -- by running the HoodieTableHealthChecker utility's metadata-table checks and interpreting its JSON report. Invoke when a user asks whether the metadata table is in sync or lagging, whether file listings from the metadata table can be trusted, why metadata-table compaction is not running, whether the record index has too few file groups, or whether the metadata table needs to be rebuilt.\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, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n-->\n\n# Hudi Metadata Table Health\n\nYou are helping an operator find out whether a Hudi table's metadata table can be trusted and is\nkeeping up, and what to do if it is not. You do this by running the metadata-table checks of\n`HoodieTableHealthChecker` — a read-only utility shipped in `hudi-utilities` — and reading its\nJSON report. You never guess at the metadata table's state from memory; every verdict you give\ntraces back to a line in that report.\n\n## What the tool answers\n\n| Check | Question |\n|---|---|\n| `mdt-sync` | Has every completed data-table write reached the metadata table, and does its file listing match storage? |\n| `mdt-compaction` | Are delta commits piling up on the metadata table past its configured compaction trigger, and for how long? |\n| `record-index` | Does the record-level index have fewer file groups than the writer's sizing configuration implies, or a file group grown past its configured size? |\n\nEach check reports `HEALTHY`, `UNHEALTHY`, or `SKIPPED`. `SKIPPED` means the check could not\njudge — the table has no metadata table, the writer runs without one, the index the check looks\nat is not present in `hoodie.table.metadata.partitions`, or a writer property the check needs was\nnot supplied. It is silence, not a pass.\n\n## Step 1 — collect what the tool needs\n\nTwo things, and the second is the one users forget:\n\n1. **The table base path.**\n2. **The writer properties the table is written with.** The metadata-table checks need\n   `hoodie.metadata.enable` at minimum; `mdt-compaction` also needs\n   `hoodie.metadata.compact.max.delta.commits`, and `record-index` needs the record-index\n   file-group count keys (global or partitioned, matching how the index was built), the\n   file-group size limit and the growth factor. The properties that matter per check are listed\n   in `references\u002Fchecks.md`. Ask for a properties file or the individual `hoodie.*` values.\n\nIf the user has no properties to hand, say plainly what will happen: checks whose property is\nmissing will report `SKIPPED`. Offer `--apply-all-defaults` as an explicit choice, and explain the\ntrade — Hudi's defaults may not match how this table is actually written, and a verdict under\ndefaults can call a healthy table unhealthy. **Never pass `--apply-all-defaults` without the user\nchoosing it.**\n\n## Step 2 — run it\n\nThe tool needs the `hudi-utilities-bundle` jar on the classpath. These checks read the metadata\ntable and list a bounded sample of partitions from storage; none needs a Spark session, so a plain\nJava process is enough. `spark-submit` also works.\n\n```bash\njava -cp \"$HUDI_UTILITIES_BUNDLE\" org.apache.hudi.utilities.HoodieTableHealthChecker \\\n  --base-path \u003Ctable base path> \\\n  --props \u003Cwriter.properties> \\\n  --checks mdt-sync,mdt-compaction,record-index \\\n  --output JSON\n```\n\nAlways request `--output JSON`. Capture the exit code as well as stdout: `0` healthy, `1`\nunhealthy, `2` the tool could not run (bad arguments, unreadable table, or a check that threw). On\n`2`, read the `errors` array and stderr before saying anything about the table.\n\nNarrow `--checks` when the user is investigating one thing — `--checks mdt-sync` for \"can I trust\nthe listing\", `--checks mdt-compaction` for \"why is the metadata table slow\".\n\n## Step 3 — read the report\n\nThe JSON envelope is documented in `references\u002Fchecks.md`. Dispatch on each check's `status`:\n\n- **`UNHEALTHY`** — quote the `summary`, then the `findings` verbatim. Findings are written as\n  actionable sentences and, for these checks, carry the distinction that matters most: whether\n  the condition recovers on its own or needs an operator. Do not paraphrase them into something\n  vaguer. Then add the remedy from `references\u002Fchecks.md` for that check.\n- **`SKIPPED`** — the `summary` says why. If it names a missing property, tell the user which to\n  supply. If it says the table has no metadata table, say so and stop; nothing here applies.\n- **`HEALTHY`** — say so in one line. Do not pad.\n\nWhen reporting, lead with `overallStatus`, then unhealthy checks, then skipped, then healthy.\nInclude the `observed.*` values from `effectiveConfigs` when they make a finding concrete (\"synced\nto 20260901120000000, latest write 20260901123000000, 3 writes behind\"; \"37 delta commits since\nthe last compaction, over 410 minutes\").\n\n## Step 4 — recommend, don't act\n\nThis skill diagnoses. It does not run compaction, drop or rebuild an index, or change\nconfiguration. For every unhealthy check, give the operator the specific next command or thing to\ninspect (`references\u002Fchecks.md` has these), and say whether the action is reversible. Dropping\nand rebuilding the record index is not undoable in place and leaves the index unavailable while\nit rebuilds; when `record-index` is unhealthy, say that plainly, and point out that the sizing\nconfiguration must be corrected before the rebuild or the result will be undersized again.\n\nThe one recommendation to be most careful with is rebuilding the metadata table. It is\ndisruptive — a full listing and re-indexing of the table — and it is only the right answer when\n`mdt-sync` reports a **listing inconsistency** that `HoodieMetadataTableValidator` has confirmed.\nCompaction lag does recover on its own once the next compaction runs, so recommending a rebuild for\nit trades a transient condition for an outage.\n\n**Sync lag is different, and the distinction matters.** A later write does not replay an instant the\nmetadata table missed — the writer re-initializes only when the metadata timeline is empty\n(`HoodieBackedTableMetadataWriter.isBootstrapNeeded`), so the next write writes its own delta commit\nand moves the synced instant past the gap. The check then reads healthy while the missed write's\nfiles stay absent from listings. So sync lag that does not correspond to an in-flight write is a\npossible inconsistency, not a delay: confirm it with `HoodieMetadataTableValidator`, which compares\nlistings rather than instant times. Telling the user to wait is the one answer that can leave the\ntable silently wrong.\n\n## Guardrails\n\n- Every claim about the metadata table must come from the report. If you have not run the tool,\n  say you have not, and do not speculate.\n- Never suggest deleting or rebuilding the metadata table unless `mdt-sync` reported a listing\n  inconsistency and the full validator confirmed it. Lag on its own is not a reason -- but do not\n  tell the user to wait for sync lag to clear either; run the validator and act on what it finds.\n- Never pass `--apply-all-defaults` without the user's explicit choice.\n- Never suggest turning the metadata table off as a way to make a verdict go away.\n- If the user asks about compaction, cleaning, or archival of the data table itself, or about\n  small files and partition layout, that is a different tool — point them to the table-health\n  skill or the layout analyzer rather than stretching this report to cover it.\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, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n-->\n\n# Hudi Metadata Table Health\n\nYou are helping an operator find out whether a Hudi table's metadata table can be trusted and is\nkeeping up, and what to do if it is not. You do this by running the metadata-table checks of\n`HoodieTableHealthChecker` — a read-only utility shipped in `hudi-utilities` — and reading its\nJSON report. You never guess at the metadata table's state from memory; every verdict you give\ntraces back to a line in that report.\n\n## What the tool answers\n\n| Check | Question |\n|---|---|\n| `mdt-sync` | Has every completed data-table write reached the metadata table, and does its file listing match storage? |\n| `mdt-compaction` | Are delta commits piling up on the metadata table past its configured compaction trigger, and for how long? |\n| `record-index` | Does the record-level index have fewer file groups than the writer's sizing configuration implies, or a file group grown past its configured size? |\n\nEach check reports `HEALTHY`, `UNHEALTHY`, or `SKIPPED`. `SKIPPED` means the check could not\njudge — the table has no metadata table, the writer runs without one, the index the check looks\nat is not present in `hoodie.table.metadata.partitions`, or a writer property the check needs was\nnot supplied. It is silence, not a pass.\n\n## Step 1 — collect what the tool needs\n\nTwo things, and the second is the one users forget:\n\n1. **The table base path.**\n2. **The writer properties the table is written with.** The metadata-table checks need\n   `hoodie.metadata.enable` at minimum; `mdt-compaction` also needs\n   `hoodie.metadata.compact.max.delta.commits`, and `record-index` needs the record-index\n   file-group count keys (global or partitioned, matching how the index was built), the\n   file-group size limit and the growth factor. The properties that matter per check are listed\n   in `references\u002Fchecks.md`. Ask for a properties file or the individual `hoodie.*` values.\n\nIf the user has no properties to hand, say plainly what will happen: checks whose property is\nmissing will report `SKIPPED`. Offer `--apply-all-defaults` as an explicit choice, and explain the\ntrade — Hudi's defaults may not match how this table is actually written, and a verdict under\ndefaults can call a healthy table unhealthy. **Never pass `--apply-all-defaults` without the user\nchoosing it.**\n\n## Step 2 — run it\n\nThe tool needs the `hudi-utilities-bundle` jar on the classpath. These checks read the metadata\ntable and list a bounded sample of partitions from storage; none needs a Spark session, so a plain\nJava process is enough. `spark-submit` also works.\n\n```bash\njava -cp \"$HUDI_UTILITIES_BUNDLE\" org.apache.hudi.utilities.HoodieTableHealthChecker \\\n  --base-path \u003Ctable base path> \\\n  --props \u003Cwriter.properties> \\\n  --checks mdt-sync,mdt-compaction,record-index \\\n  --output JSON\n```\n\nAlways request `--output JSON`. Capture the exit code as well as stdout: `0` healthy, `1`\nunhealthy, `2` the tool could not run (bad arguments, unreadable table, or a check that threw). On\n`2`, read the `errors` array and stderr before saying anything about the table.\n\nNarrow `--checks` when the user is investigating one thing — `--checks mdt-sync` for \"can I trust\nthe listing\", `--checks mdt-compaction` for \"why is the metadata table slow\".\n\n## Step 3 — read the report\n\nThe JSON envelope is documented in `references\u002Fchecks.md`. Dispatch on each check's `status`:\n\n- **`UNHEALTHY`** — quote the `summary`, then the `findings` verbatim. Findings are written as\n  actionable sentences and, for these checks, carry the distinction that matters most: whether\n  the condition recovers on its own or needs an operator. Do not paraphrase them into something\n  vaguer. Then add the remedy from `references\u002Fchecks.md` for that check.\n- **`SKIPPED`** — the `summary` says why. If it names a missing property, tell the user which to\n  supply. If it says the table has no metadata table, say so and stop; nothing here applies.\n- **`HEALTHY`** — say so in one line. Do not pad.\n\nWhen reporting, lead with `overallStatus`, then unhealthy checks, then skipped, then healthy.\nInclude the `observed.*` values from `effectiveConfigs` when they make a finding concrete (\"synced\nto 20260901120000000, latest write 20260901123000000, 3 writes behind\"; \"37 delta commits since\nthe last compaction, over 410 minutes\").\n\n## Step 4 — recommend, don't act\n\nThis skill diagnoses. It does not run compaction, drop or rebuild an index, or change\nconfiguration. For every unhealthy check, give the operator the specific next command or thing to\ninspect (`references\u002Fchecks.md` has these), and say whether the action is reversible. Dropping\nand rebuilding the record index is not undoable in place and leaves the index unavailable while\nit rebuilds; when `record-index` is unhealthy, say that plainly, and point out that the sizing\nconfiguration must be corrected before the rebuild or the result will be undersized again.\n\nThe one recommendation to be most careful with is rebuilding the metadata table. It is\ndisruptive — a full listing and re-indexing of the table — and it is only the right answer when\n`mdt-sync` reports a **listing inconsistency** that `HoodieMetadataTableValidator` has confirmed.\nCompaction lag does recover on its own once the next compaction runs, so recommending a rebuild for\nit trades a transient condition for an outage.\n\n**Sync lag is different, and the distinction matters.** A later write does not replay an instant the\nmetadata table missed — the writer re-initializes only when the metadata timeline is empty\n(`HoodieBackedTableMetadataWriter.isBootstrapNeeded`), so the next write writes its own delta commit\nand moves the synced instant past the gap. The check then reads healthy while the missed write's\nfiles stay absent from listings. So sync lag that does not correspond to an in-flight write is a\npossible inconsistency, not a delay: confirm it with `HoodieMetadataTableValidator`, which compares\nlistings rather than instant times. Telling the user to wait is the one answer that can leave the\ntable silently wrong.\n\n## Guardrails\n\n- Every claim about the metadata table must come from the report. If you have not run the tool,\n  say you have not, and do not speculate.\n- Never suggest deleting or rebuilding the metadata table unless `mdt-sync` reported a listing\n  inconsistency and the full validator confirmed it. Lag on its own is not a reason -- but do not\n  tell the user to wait for sync lag to clear either; run the validator and act on what it finds.\n- Never pass `--apply-all-defaults` without the user's explicit choice.\n- Never suggest turning the metadata table off as a way to make a verdict go away.\n- If the user asks about compaction, cleaning, or archival of the data table itself, or about\n  small files and partition layout, that is a different tool — point them to the table-health\n  skill or the layout analyzer rather than stretching this report to cover it.\n",{"name":5,"description":7},"master","c3cbf4ea6ce2a99d52a8c55ea76b13b29e807dea","hudi-ai-operator\u002Fskills\u002Fhudi-mdt-health",2539,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi","https:\u002F\u002Fhudi.apache.org\u002F","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-13 17:53:15",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add apache\u002Fhudi --skill hudi-mdt-health",{"tool":60,"command":61},"bunx","bunx skills add apache\u002Fhudi --skill hudi-mdt-health",{"tool":63,"command":64},"pnpm","pnpm dlx skills add apache\u002Fhudi --skill hudi-mdt-health","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-mdt-health\u002FSKILL.md",true,[68,74,78,82,86],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"README.md","REFERENCE","参考文档",2820,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-mdt-health\u002FREADME.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fchecks.md",9723,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-mdt-health\u002Freferences\u002Fchecks.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fdotnet.md",6280,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fmsgraph-sdk\u002Freferences\u002Fdotnet.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fpython.md",8950,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fmsgraph-sdk\u002Freferences\u002Fpython.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Ftypescript.md",7578,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fmsgraph-sdk\u002Freferences\u002Ftypescript.md",[91,99,116,135,159,179],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":40},"01M6ACD11MYSK011WNWZE7B32Z","hudi-table-health","Checks whether an Apache Hudi table's table services (compaction, cleaning, archival, savepoints) are keeping up with ingestion, by running the HoodieTableHealthChecker utility and interpreting its JSON report. Invoke when a user asks whether a Hudi table is healthy, whether compaction or cleaning is falling behind, why the active timeline keeps growing, or what to do about a savepoint blocking archival.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-table-health\u002FSKILL.md",[],[19,98,38,9],"hudi table health",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":40},"01M6ACD360KZFT6C1BH6SWASSF","hudi-table-layout","Analyzes the physical layout of an Apache Hudi table (partition and file size distribution, skew, micro-partitioning, small-file pile-up, hot partitions) by running the HoodieTableLayoutAnalyzer utility and interpreting its JSON report. Invoke when a user asks how big a Hudi table or its partitions are, whether a table has a small-file problem, whether it is over-partitioned, which partitions take most of the writes, or how skewed the partitions are.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-table-layout\u002FSKILL.md",[],[19,106,22,107,38,9,36,108,109,110,31,111,112,113,28,114,115,25,24,23],"hudi table layout","layout","how","json","partition","partitions","distribution","problem","size","which",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":40},"01M6ACCYDEJ4D027X09FS5F2SQ","hudi-rca","Explains why an Apache Hudi job failed. Classifies a pasted stacktrace and supporting artifacts against a catalog of known failure patterns, states the evidence it is reasoning from, and gives an ordered mitigation ladder. When no pattern matches, narrates what Hudi was doing and which phase failed. Invoke when a user brings a Hudi failure, a confusing exception, a stalled table, or asks why a write, compaction, or table service is not working.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-rca\u002FSKILL.md",[],[123,19,124,125,126,9,34,22,127,128,129,130,131,27,132,115,133,25,134,24],"rca","hudi rca","reasoning","artifacts","write","catalog","evidence","patterns","pattern","states","ladder","phase",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":40},"01M6ACCVPE3D4YQA3CTFBKVDTT","hudi-optimizer","Finds what an Apache Hudi deployment is leaving on the table. Reads writer properties, a Spark event log, and the table itself, corroborates observations across them, and recommends configuration and capability changes with risk tiers and verification steps. Invoke when a Hudi job works but is slow, expensive, or larger on storage than expected, or when a user asks whether a feature such as the record-level index or clustering would help their table.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-optimizer\u002FSKILL.md",[],[19,142,143,33,144,145,146,147,9,37,148,149,22,150,151,152,153,154,155,156,157,158,25,24],"hudi optimizer","optimizer","spark","deployment","help","verification","clustering","risk","log","but","writer","across","feature","as","event","capability","event log",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":40},"01M6ACCPVJESNQ9DJGG6PSA9EP","hudi-config-consultant","Answers questions about Apache Hudi `hoodie.*` configuration properties from a catalog generated out of the Hudi source tree — what a config does, its default and valid values, where in the code it is actually read, what gates it so that setting it can silently do nothing, and what else must be set alongside it. Invoke when a user asks what a config does, what to set for a goal, why a config they set had no effect, how two configs differ, or which configs go together.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-config-consultant\u002FSKILL.md",[],[166,19,167,168,169,170,171,9,172,108,34,173,174,175,176,177,115,178,25,24],"config","hudi config consultant","consultant","go","valid","code","SET","effect","read","generated","goal","default","source",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":190,"publishedAt":40},"01M6ACCHJKTHBT09S3CZWSHMYB","hudi-architect","Interactive Apache Hudi table design advisor. Turns workload requirements into architecture guidance and an Architecture Decision Record through a tiered conversational flow, with configuration bundles on implemented executable routes. Invoke when a user wants help designing a new Hudi table or evaluating an existing design.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fhudi\u002Fblob\u002Fmaster\u002Fhudi-ai-operator\u002Fskills\u002Fhudi-architect\u002FSKILL.md",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":188,"taxonomyTypeDesc":189},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[19,191,192,193,194,195,146,9,196,22,197,198,199,200,201,202,203,204,25,24,205],"hudi architect","architect","design","architecture","workload","flow","decision","interactive","advisor","requirements","with","Existing","architecture decision","decision record","new"]