chore(samples): add sample for AddToCell mutation

[daniel-sanche]

Replaces #1231
Fixes b/452032333

Adds a sample for the new AddToCell incrementation mutation

[snippet-bot]

Here is the summary of changes.

You are about to add 1 region tag.

• samples/snippets/data_client/data_client_snippets_async.py:140, tag bigtable_async_write_aggregate

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[gemini-code-assist]

Summary of Changes

Hello @daniel-sanche, 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 asynchronous code sample for Google Cloud Bigtable, demonstrating the use of the AddToCell mutation to increment values within a table. This enhancement provides developers with a clear example of how to leverage Bigtable's aggregation capabilities, ensuring proper setup of aggregate column families and robust error handling. The accompanying test updates validate the new sample's functionality, improving the overall coverage and utility of the Bigtable client library examples.

Highlights

• New AddToCell Mutation Sample: A new asynchronous sample, write_aggregate, has been added to demonstrate how to use the AddToCell mutation to increment values in a Bigtable table. This includes proper setup for aggregate column families and error handling.
• Test Suite Enhancements for Aggregation: The test suite now includes a new column_family_config fixture to define an aggregate column family (counters) with an int64 input type, which is essential for AddToCell mutations. The table_id fixture was updated to use this configuration.
• New Asynchronous Test: A new asynchronous test, test_write_aggregate, has been added to validate the functionality of the newly introduced write_aggregate sample.

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 a new sample for the AddToCell mutation. I've identified a critical issue in the sample code where a required argument is missing, which will lead to a TypeError. Additionally, I found a syntax error and another minor issue in the test file. My review includes suggestions to fix these problems.