-
Notifications
You must be signed in to change notification settings - Fork 3
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
Confluent OWNERS #228
Comments
Totally agree! |
Gentle ping on this. @ypmahajan @aakashnshah @ncliang @sagarrao12 @ManasjyotiSharma |
New MRs: And I have few others in my private repository In the current repository, there are many deadlocks/raceconditions causing the connector to stop consuming, or not handled failures. If anyone is interested, I can create a fork that some of the interested community can work on. |
Would be really nice if Confluent can work and help with addressing @FreCap 's CRs which like they mentioned above community and even customers like us would greatly benefit from. |
Hi Confluent owners @ypmahajan @aakashnshah @gharris1727 @ncliang,
could you please share any insights on the future maintenance of the project/MR check-in?
The CI seems tied to Confluent systems, and it only succeeds if Confluent employees trigger it.
There are a few really good contributions that should be ready to be checked in, e.g.:
batch
priority for intermediate table DELETEs #206And a few others I would like to contribute myself.
Would you accept external contributions, or Confluent policies prefer contributing to external Forks?
I'd be happy to be add as a owner and run codereviews .
Thank you,
Francesco
The text was updated successfully, but these errors were encountered: