-
Notifications
You must be signed in to change notification settings - Fork 1.5k
feat: Make MAX_DOWNLOADED_QUERY_RESULT_ROWS configurable #2167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat: Make MAX_DOWNLOADED_QUERY_RESULT_ROWS configurable #2167
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
- Add max_downloaded_rows field to BigQueryToolConfig with default value 50 - Add optional max_rows parameter to execute_sql function - Parameter takes precedence over config when both provided - Maintain backward compatibility with existing code - Add comprehensive tests for config and parameter functionality - Update truncation logic to use resolved max_downloaded_rows value
35fa798
to
9481f9b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Over all the change looks good, left some small comments.
Thank you for contributing.
- Create private constant _DEFAULT_MAX_DOWNLOADED_QUERY_RESULT_ROWS = 50 - Consolidate max_downloaded_rows logic to avoid duplication - Remove redundant None check in truncation logic
…:lupuletic/adk-python into feature/configurable-max-downloaded-rows
🤖 Generated with Claude Code