Guides Java SDK development in Apache Beam, from finding relevant modules to building code, running focused tests, and trying examples. Also explains how to publish modified modules locally and build SDK containers.
Learn Apache Beam's core concepts through Java and Python examples. Understand distributed datasets, processing steps, pipeline execution, and time windows, with guidance on aggregation, late data, error handling, and sharing processing steps across languages.
Guides adding metadata, extra information attached to data elements, to Apache Beam's WindowedValue. Maps the changes needed across serialization, storage, processing, and runner interfaces so new fields remain available during pipeline execution.
Inspect an Apache Hudi table’s storage layout using a read-only analysis tool. Get report-based findings on table size, uneven data distribution, excessive partitions, small files, and concentrated writes, with suggested next steps.
Check whether Apache Hudi table maintenance is keeping pace with incoming data. Runs a read-only utility, interprets its JSON report, and explains unhealthy or skipped checks with concrete next steps.
Design or review Apache Hudi tables through questions about data volume, updates, and usage. Get architecture recommendations, a decision record explaining tradeoffs, and configuration artifacts for supported processing paths.
Migrate Java projects from FastExcel 1.3 to Apache Fesod by updating Maven or Gradle dependencies, package imports, and entry class calls. Handles both legacy package namespaces and identifies conditional helper class changes.
Review Apache Pinot changes for compatibility with existing configurations and consumers. Covers public APIs, extension interfaces, serialized data formats, and REST responses, helping focus code review on changes that may affect existing users.
Compare baseline and current Pinot benchmark results from JMH, a tool for measuring code performance. The skill uses a separate baseline worktree, a working directory kept apart from the current code.
Validate and fix Pinot pre-commit checks for modules affected by a change. Use it before a commit or pull request to address check failures in the relevant parts of the project.
Review Apache Pinot changes for correctness in null handling, numeric types, type-based processing, and resource lifecycles. Use it to examine changes to calculations, aggregations, window functions, and segment cleanup or persistence.
Review Apache Pinot changes affecting frequently executed code or making performance claims in a pull request. Relevant areas include operators, segment readers, aggregation functions, and locking inside loops that process individual rows.
Review the scope and process of Apache Pinot changes, including pull request descriptions, reverts, retries, and compatibility notes. Use it to examine large changes, test workarounds, and documentation needed for changes that break backward compatibility.
Review architecture changes in Apache Pinot, focusing on module dependencies, extension interfaces, abstractions, and class placement. Use it to examine changes that cross module boundaries or introduce new plugins and interfaces.
Review regression coverage and test quality in Apache Pinot when behavior or tests change. Use it to assess whether code changes and bug fixes have relevant tests, including paths that handle different types or null values.
Start a local Pinot quickstart and verify it using modes supported by the checked-out code. Use it to bring up a local trial environment that matches the version you are working with.
Review Apache Pinot changes against naming and API conventions, including public names, method signatures, REST endpoints, JSON fields, and documentation. Use it when adding or renaming elements exposed to other code or users.
Review Apache Pinot changes for concurrency and state safety, including locks, shared callbacks, lifecycle changes, and distributed metadata. Use it to examine how changes affect shared state when multiple operations run at the same time.
Run a named Pinot test class or individual method in the Maven module that contains it. Use it to focus test execution on a specific target within the project's module structure.
Investigate Pinot tests that fail intermittently in GitHub Actions. Use the skill to produce a report describing the evidence found and likely causes, helping explain failures that do not occur consistently.
Guides Apache OpenDAL release managers through preparation, release candidates, verification, voting, and publication. It tracks the current stage, checks external systems, and distinguishes core, candidate, and package versions when deciding the next release action.
Review pull requests, branches, or uncommitted changes across eight areas, including security, correctness, and tests. Verify findings against the code, group problems by type, and assess whether the change needs redesign or smaller fixes.
Extract Markdown and metadata from PDFs, Office documents, emails, archives, and other formats using Apache Tika. Keep attachments and embedded items separate in structured output, detect parsing problems, and read selected portions without overwhelming the agent's context.
Maintain Tika's registry of metadata keys, the names used for document attributes. Guides regeneration after key changes, checks generated files against code, applies naming rules, and finds outdated references after renaming.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)