add logging for dpo

[isha97]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @isha97, 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 focuses on improving the observability and debuggability of data write operations, particularly those involving dynamic partition overwrites in the BigQuery connector. By introducing comprehensive logging at key stages, including method entry points, partition detection, query execution, and condition checks, the changes aim to provide clearer insights into the system's behavior, making it easier to diagnose issues and understand the flow of data writes to BigQuery.

Highlights

• Enhanced Logging for Dynamic Partition Overwrite: Added detailed log statements within the overwriteDestinationWithTemporaryDynamicPartitons method in BigQueryClient.java to provide better visibility into the process, including input table IDs, detected partition types (time or range), and the SQL query being executed for dynamic partition overwrites.
• Debug Stack Traces: Introduced debug stack traces at the entry points of overwriteDestinationWithTemporaryDynamicPartitons and overwriteDestinationWithTemporary methods to assist in tracing the call stack during execution.
• Fallback Logging: Added a log message in BigQueryClient.java to indicate when no partition definition is found for a destination table, leading to a fallback to the standard overwrite mechanism.
• Conditions Check Logging: Implemented a log statement in BigQueryWriteHelper.java to display critical conditions (write disposition, partition overwrite mode, table existence, and partitioning status) before the dynamic partition overwrite logic is applied, aiding in understanding the decision-making process.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds several info level log statements to aid in debugging dynamic partition overwrites. While most of the logging is helpful, there are a few instances where stack traces are being logged at the INFO level. This is generally discouraged in production code due to performance overhead and log verbosity. I've recommended changing these to DEBUG level. Additionally, I've suggested lowering the log level for a statement that logs a full SQL query to DEBUG to prevent potential sensitive data exposure and reduce log noise.