Fix typo in WriteToKafka docstring: deserializer -> serializer

[ANONYMOUSZED-beep]

Fixed documentation parameter names in WriteToKafka.init:

• key_deserializer -> key_serializer
• value_deserializer -> value_serializer

Fixes #36931

[gemini-code-assist]

Summary of Changes

Hello @ANONYMOUSZED-beep, 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 addresses a minor but important documentation error within the WriteToKafka class. The docstring for the __init__ method incorrectly referred to key_deserializer and value_deserializer parameters when they should have been key_serializer and value_serializer, respectively. This change ensures the documentation accurately reflects the function of these parameters, improving clarity for developers using the Kafka I/O connector.

Highlights

• Documentation Correction: Corrected a typo in the WriteToKafka.__init__ docstring, changing key_deserializer to key_serializer.
• Documentation Correction: Corrected a typo in the WriteToKafka.__init__ docstring, changing value_deserializer to value_serializer.

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

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[Abacn]

Thanks. Looks like an typo due to copy-pasted from kafka_read