Skip to content

docs: add integration_duckdb_example and refactor names of prev notebooks#2981

Closed
federicsp wants to merge 1 commit intoapache:mainfrom
federicsp:docs/add_notebook_integration_duckdb_example
Closed

docs: add integration_duckdb_example and refactor names of prev notebooks#2981
federicsp wants to merge 1 commit intoapache:mainfrom
federicsp:docs/add_notebook_integration_duckdb_example

Conversation

@federicsp
Copy link
Copy Markdown

Rationale for this change

This PR adds a new example notebook demonstrating integration between PyIceberg and DuckDB, including:

  • Creating a temporary warehouse and SQL catalog
  • Creating Iceberg tables and appending data (first and second snapshots)
  • Comparing snapshots in DuckDB (added/removed rows)
  • Adding computed columns, filtering, and aggregating data

It also refactors and renames previous notebooks for clarity and consistency.

Are these changes tested?

Yes, the notebooks have been tested.

Are there any user-facing changes?

No, these are documentation/example changes only.

@Fokko
Copy link
Copy Markdown
Contributor

Fokko commented Feb 7, 2026

Thanks @federicsp for adding this! This will help folks up to speed with DuckDB and PyIceberg.

Regarding testing, what do you think of adding someting like Papermill: https://papermill.readthedocs.io/en/latest/. This will allow us testing the Notebook in the CI. This ensures that the notebooks keep working.

@github-actions
Copy link
Copy Markdown

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that's incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Mar 19, 2026
@github-actions
Copy link
Copy Markdown

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@github-actions github-actions bot closed this Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants