iparq 0.1.5__tar.gz → 0.1.7__tar.gz

iparq-0.1.7/.github/copilot-instructions.md

@@ -0,0 +1,12 @@
+# Copilot instructions
+
+## Package management
+
+Use UV for package management.
+
+## Python
+
+Since this is a CLI tool, use typer for the CLI interface.
+
+Use pydantic for data validation and settings management.
+Use pytest for testing.

{iparq-0.1.5 → iparq-0.1.7}/.gitignore

@@ -171,3 +171,4 @@ cython_debug/
 .pypirc
 .github/.DS_Store
 yellow_tripdata_2024-01.parquet
+filter.parquet

iparq-0.1.7/CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing to iparq
+
+Thank you for considering contributing to iparq! We're excited to collaborate with you. Here are some guidelines to help you get started:
+
+## How to Contribute
+
+1. **Fork the repository**: Click the "Fork" button at the top right of this page to create a copy of the repository.
+2. **Clone your fork**: Use `git clone <your-fork-url>` to clone your forked repository to your local machine.
+3. **Create a branch**: Use `git checkout -b <branch-name>` to create a new branch for your changes.
+4. **Make your changes**: Make the necessary changes in your local repository.
+5. **Commit your changes**: Use `git commit -m "Description of changes"` to commit your changes.
+6. **Push your changes**: Use `git push origin <branch-name>` to push your changes to your forked repository.
+7. **Create a pull request**: Go to the original repository and create a pull request from your forked repository.
+
+## Guidelines
+
+- **Code of Conduct**: Please adhere to our [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a welcoming and friendly environment.
+- **Documentation**: Ensure your code changes are well-documented. Update any relevant documentation in the `docs` folder.
+- **Tests**: Include tests for your changes to ensure functionality and avoid regressions.
+- **Commit Messages**: Write clear and concise commit messages. Follow the format: `type(scope): message`.
+
+## Reporting Issues
+
+If you encounter any issues or bugs, please open an issue in the repository. Provide as much detail as possible, including steps to reproduce the issue and any relevant logs or screenshots.
+
+## License
+
+By contributing to this project, you agree that your contributions will be licensed under the [MIT License](LICENSE).
+
+Thank you for your contributions and support!
+
+Happy coding!

{iparq-0.1.5 → iparq-0.1.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: iparq
-Version: 0.1.5
+Version: 0.1.7
 Summary: Display version and compression information about a parquet file
 Author-email: MiguelElGallo <miguel.zurcher@gmail.com>
 License-File: LICENSE
@@ -26,6 +26,10 @@ Description-Content-Type: text/markdown
 ![alt text](media/iparq.png)
 After reading [this blog](https://duckdb.org/2025/01/22/parquet-encodings.html), I began to wonder which Parquet version and compression methods the everyday tools we rely on actually use, only to find that there’s no straightforward way to determine this. That curiosity and the difficulty of quickly discovering such details motivated me to create iparq (Information Parquet). My goal with iparq is to help users easily identify the specifics of the Parquet files generated by different engines, making it clear which features—like newer encodings or certain compression algorithms—the creator of the parquet is using.
 
+***New*** Bloom filters information: Displays if there are bloom filters.
+Read more about bloom filters in this [great article](https://duckdb.org/2025/03/07/parquet-bloom-filters-in-duckdb.html).
+
+
 ## Installation
 
 ### Using pip
@@ -80,7 +84,63 @@ iparq <filename>
 
 Replace `<filename>` with the path to your .parquet file. The utility will read the metadata of the file and print the compression codecs used in the parquet file.
 
-## Example output
+## Example ouput - Bloom Filters
+
+```log
+ParquetMetaModel(
+    created_by='DuckDB version v1.2.1 (build 8e52ec4395)',
+    num_columns=1,
+    num_rows=100000000,
+    num_row_groups=10,
+    format_version='1.0',
+    serialized_size=1196
+)
+Column Compression Info:
+Row Group 0:
+  Column 'r' (Index 0): SNAPPY
+Row Group 1:
+  Column 'r' (Index 0): SNAPPY
+Row Group 2:
+  Column 'r' (Index 0): SNAPPY
+Row Group 3:
+  Column 'r' (Index 0): SNAPPY
+Row Group 4:
+  Column 'r' (Index 0): SNAPPY
+Row Group 5:
+  Column 'r' (Index 0): SNAPPY
+Row Group 6:
+  Column 'r' (Index 0): SNAPPY
+Row Group 7:
+  Column 'r' (Index 0): SNAPPY
+Row Group 8:
+  Column 'r' (Index 0): SNAPPY
+Row Group 9:
+  Column 'r' (Index 0): SNAPPY
+Bloom Filter Info:
+Row Group 0:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 1:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 2:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 3:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 4:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 5:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 6:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 7:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 8:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 9:
+  Column 'r' (Index 0): Has bloom filter
+Compression codecs: {'SNAPPY'}
+```
+
+## Example output 
 
 ```log
 ParquetMetaModel(

{iparq-0.1.5 → iparq-0.1.7}/README.md

@@ -9,6 +9,10 @@
 ![alt text](media/iparq.png)
 After reading [this blog](https://duckdb.org/2025/01/22/parquet-encodings.html), I began to wonder which Parquet version and compression methods the everyday tools we rely on actually use, only to find that there’s no straightforward way to determine this. That curiosity and the difficulty of quickly discovering such details motivated me to create iparq (Information Parquet). My goal with iparq is to help users easily identify the specifics of the Parquet files generated by different engines, making it clear which features—like newer encodings or certain compression algorithms—the creator of the parquet is using.
 
+***New*** Bloom filters information: Displays if there are bloom filters.
+Read more about bloom filters in this [great article](https://duckdb.org/2025/03/07/parquet-bloom-filters-in-duckdb.html).
+
+
 ## Installation
 
 ### Using pip
@@ -63,7 +67,63 @@ iparq <filename>
 
 Replace `<filename>` with the path to your .parquet file. The utility will read the metadata of the file and print the compression codecs used in the parquet file.
 
-## Example output
+## Example ouput - Bloom Filters
+
+```log
+ParquetMetaModel(
+    created_by='DuckDB version v1.2.1 (build 8e52ec4395)',
+    num_columns=1,
+    num_rows=100000000,
+    num_row_groups=10,
+    format_version='1.0',
+    serialized_size=1196
+)
+Column Compression Info:
+Row Group 0:
+  Column 'r' (Index 0): SNAPPY
+Row Group 1:
+  Column 'r' (Index 0): SNAPPY
+Row Group 2:
+  Column 'r' (Index 0): SNAPPY
+Row Group 3:
+  Column 'r' (Index 0): SNAPPY
+Row Group 4:
+  Column 'r' (Index 0): SNAPPY
+Row Group 5:
+  Column 'r' (Index 0): SNAPPY
+Row Group 6:
+  Column 'r' (Index 0): SNAPPY
+Row Group 7:
+  Column 'r' (Index 0): SNAPPY
+Row Group 8:
+  Column 'r' (Index 0): SNAPPY
+Row Group 9:
+  Column 'r' (Index 0): SNAPPY
+Bloom Filter Info:
+Row Group 0:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 1:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 2:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 3:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 4:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 5:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 6:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 7:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 8:
+  Column 'r' (Index 0): Has bloom filter
+Row Group 9:
+  Column 'r' (Index 0): Has bloom filter
+Compression codecs: {'SNAPPY'}
+```
+
+## Example output 
 
 ```log
 ParquetMetaModel(

{iparq-0.1.5 → iparq-0.1.7}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "iparq"
-version = "0.1.5"
+version = "0.1.7"
 description = "Display version and compression information about a parquet file"
 readme = "README.md"
 authors = [

{iparq-0.1.5 → iparq-0.1.7}/src/iparq/source.py

@@ -120,6 +120,45 @@ def print_compression_types(parquet_metadata) -> None:
         pass
 
 
+def print_bloom_filter_info(parquet_metadata) -> None:
+    """
+    Prints information about bloom filters for each column in each row group of the Parquet file.
+    """
+    try:
+        num_row_groups = parquet_metadata.num_row_groups
+        num_columns = parquet_metadata.num_columns
+        has_bloom_filters = False
+
+        console.print("[bold underline]Bloom Filter Info:[/bold underline]")
+
+        for i in range(num_row_groups):
+            row_group = parquet_metadata.row_group(i)
+            bloom_filters_in_group = False
+
+            for j in range(num_columns):
+                column_chunk = row_group.column(j)
+                column_name = parquet_metadata.schema.column(j).name
+
+                # Check if this column has bloom filters using is_stats_set
+                if hasattr(column_chunk, "is_stats_set") and column_chunk.is_stats_set:
+                    if not bloom_filters_in_group:
+                        console.print(f"[bold]Row Group {i}:[/bold]")
+                        bloom_filters_in_group = True
+                    has_bloom_filters = True
+                    console.print(
+                        f"  Column '{column_name}' (Index {j}): [green]Has bloom filter[/green]"
+                    )
+
+        if not has_bloom_filters:
+            console.print("  [italic]No bloom filters found in any column[/italic]")
+
+    except Exception as e:
+        console.print(
+            f"Error while printing bloom filter information: {e}",
+            style="blink bold red underline on white",
+        )
+
+
 @app.command()
 def main(filename: str):
     """
@@ -135,6 +174,7 @@ def main(filename: str):
 
     print_parquet_metadata(parquet_metadata)
     print_compression_types(parquet_metadata)
+    print_bloom_filter_info(parquet_metadata)
     print(f"Compression codecs: {compression}")