-
Notifications
You must be signed in to change notification settings - Fork 637
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
Zeebe java client didn't get the region from the configuration #11846
Comments
After inspecting the tests, I saw that Is this still valid as we support more regions and the default region for Free clusters is North America? There is a property for the region missing in io.camunda.zeebe.client.ClientProperties. Would this be the fix to add the property? |
This is a great issue to get started with contributing to Zeebe. It's quite clear what needs to happen: add It may teach you about how the java client works, and how it can be configured to connect to a cluster. There are workarounds available: use the |
Hello @korthout please review the PR ^_^.Thanks! |
Hi @ogkunald, I think that you should add some more tests on this topic here: https://github.com/camunda/zeebe/blob/main/clients/java/src/test/java/io/camunda/zeebe/client/ZeebeClientTest.java What happens, if a value for your new property is given? -> The client should connect to the given region My expectation is, that especially this statement |
Thanks @ingorichtsmeier You beat me to it, but that would be what I would ask for as well. @ogkunald Please have a look at our Contributing guide for details on how to build from source and run the tests |
#11870
Please review and revert in-case of anything. |
11837: [Backport stable/8.0] fix: don't re-wrap runtime exceptions thrown inside a transaction r=oleschoenburg a=oleschoenburg Manual backport of #11701 without the last commit which contained a test that is not straight forward to re-implement without the stream-platform abstraction. 11915: [Backport stable/8.0] added region property to client properties r=korthout a=backport-action # Description Backport of #11870 to `stable/8.0`. relates to #11846 Co-authored-by: Ole Schönburg <ole.schoenburg@gmail.com> Co-authored-by: ogkunald <kunaldongare111@gmail.com>
11837: [Backport stable/8.0] fix: don't re-wrap runtime exceptions thrown inside a transaction r=oleschoenburg a=oleschoenburg Manual backport of #11701 without the last commit which contained a test that is not straight forward to re-implement without the stream-platform abstraction. 11915: [Backport stable/8.0] added region property to client properties r=korthout a=backport-action # Description Backport of #11870 to `stable/8.0`. relates to #11846 Co-authored-by: Ole Schönburg <ole.schoenburg@gmail.com> Co-authored-by: ogkunald <kunaldongare111@gmail.com> Co-authored-by: Nico Korthout <nico.korthout@camunda.com>
Describe the bug
If I set up a java client for Zeebe with the CloudClientBuilder, it will only connect to the bru-2 cluster. I cannot use this client for other regions.
To Reproduce
Build a client with
and properties
Expected behavior
Running this should cause an exception, as
bru-3
doesn't exist (at least for Zeebe).Instead, it returns the topology from my cluster in bru-2.
Environment:
The text was updated successfully, but these errors were encountered: