Install parquet-cli with Homebrew

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• parquet

Project history

parquet-cli developed within Apache parquet-java, the Java implementation of the Apache Parquet columnar storage format.

Its command set expanded from basic schema, metadata, and record display into validation, format conversion, column-index inspection, bloom-filter inspection, masking, compression changes, and file rewriting.

Adoption history

The CLI is primarily a format-aware diagnostic utility for Parquet developers and data engineers. It is maintained and released as a module of parquet-java rather than as an independent end-user data platform.

Homebrew packages the module as a directly invocable parquet command, removing the need for users to assemble its Java or Hadoop invocation manually.

How it is used

Users invoke subcommands such as meta, pages, dictionary, schema, footer, cat, scan, check-stats, convert, and rewrite against Parquet or convertible data files.

It is especially useful when diagnosing encoding, statistics, schema, or file-layout problems hidden by higher-level analytical interfaces.

The CLI accepts an explicitly selected properties or XML file through --config-file, but the official documentation does not define a default config-file location.

Why package nerds care

Apache Parquet CLI is valuable to package enthusiasts as the upstream Java implementation's own toolbox for inspecting and transforming the on-disk structures behind a major analytics format.

Unlike a general SQL engine or dataframe library, it exposes commands for pages, dictionaries, indexes, bloom filters, footers, statistics validation, and file rewrites.

Timeline

• Project integration: parquet-cli became a module of the Apache parquet-java implementation.
• Subsequent development: Its command set grew to cover schemas, metadata, pages, dictionaries, indexes, bloom filters, conversion, validation, and rewriting.

Related projects

• The CLI is built and maintained inside parquet-java and operates on files conforming to the Apache Parquet format.
• Higher-level query engines such as DuckDB complement it by analyzing Parquet data through SQL rather than exposing the same low-level diagnostic command set.

Sources

• https://github.com/apache/parquet-java
• https://github.com/apache/parquet-java/blob/master/parquet-cli/README.md
• https://parquet.apache.org/
• source_facts.package-manager