Iceberg test4

[tarun-google]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @tarun-google, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new Dataflow template, PostgresToIcebergYaml, designed for efficient batch data migration from PostgreSQL databases to Apache Iceberg tables. The changes include updating project dependencies to support Iceberg and PostgreSQL connectors, enhancing the core YAML processing logic to dynamically handle template options and clean up unused parameters, and adding modular YAML configuration files for better parameter management. Comprehensive unit and integration tests have also been added to ensure the reliability and correctness of the new template.

Highlights

• New Template: Postgres to Iceberg (YAML): Introduced a new YAML-based Dataflow template, PostgresToIcebergYaml, enabling batch data transfer from PostgreSQL to Iceberg tables. This template leverages a flexible YAML structure for pipeline definition.
• Dependency Updates: Added new dependencies in pom.xml for PostgreSQL, Apache Iceberg (specifically iceberg-gcp), and Google Cloud BigDataOSS components (util-hadoop, gcs-connector, gcsio) to support the new template's functionality.
• Enhanced YAML Processing Logic: Modified main.py to include advanced Jinja templating capabilities, allowing for dynamic merging of options from external YAML files and intelligent removal of undefined or unused optional fields in the final pipeline configuration.
• Modular YAML Options: Created dedicated YAML option files (iceberg_options.yaml and postgres_options.yaml) to centralize and modularize parameter definitions for Iceberg and PostgreSQL, improving template reusability and clarity.
• Comprehensive Testing: Added new unit tests for the updated YAML processing logic in test_main.py and a robust integration test (PostgresToIcebergYamlIT.java) to validate the end-to-end data transfer from PostgreSQL to Iceberg using the new template.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.42%. Comparing base (5bdcf59) to head (2f33e9a).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #3060      +/-   ##
============================================
- Coverage     50.42%   50.42%   -0.01%     
+ Complexity     5022     5021       -1     
============================================
  Files           969      969              
  Lines         59548    59548              
  Branches       6493     6493              
============================================
- Hits          30030    30029       -1     
  Misses        27397    27397              
- Partials       2121     2122       +1     

Components	Coverage Δ
spanner-templates	70.64% <ø> (-0.01%)	⬇️
spanner-import-export	68.98% <ø> (-0.02%)	⬇️
spanner-live-forward-migration	80.04% <ø> (ø)
spanner-live-reverse-replication	77.50% <ø> (ø)
spanner-bulk-migration	88.28% <ø> (ø)
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.