Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: Enable storing _cq_client_id. #2046

Merged
merged 2 commits into from
Jan 8, 2025
Merged

Conversation

marianogappa
Copy link
Contributor

We need to be able to store _cq_client_id on every table for certain use cases where we need to know where a row came from in terms of multiplexed clients.

This PR adds the ability for the SDK and all its schedulers to store _cq_client_id on all tables.

I added this feature to the example plugin in the SDK and it does store it properly:

Screenshot 2025-01-08 at 10 45 04

If you want to try this yourself, please note that, very unfortunately, the simple plugin also stores a client_id column that is unrelated (and doesn't work, since it thinks it's supposed to be an integer).

@marianogappa marianogappa requested a review from a team as a code owner January 8, 2025 13:50
@marianogappa marianogappa requested a review from dcelasun January 8, 2025 13:50
@github-actions github-actions bot added the feat label Jan 8, 2025
@marianogappa marianogappa merged commit 3b28991 into main Jan 8, 2025
10 checks passed
@marianogappa marianogappa deleted the mariano/add-client-id branch January 8, 2025 14:13
kodiakhq bot pushed a commit that referenced this pull request Jan 8, 2025
🤖 I have created a release *beep* *boop*
---


## [4.73.0](v4.72.6...v4.73.0) (2025-01-08)


### Features

* Enable storing _cq_client_id. ([#2046](#2046)) ([3b28991](3b28991))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants