I performed the following validations:
* Verified all checksums and signatures.
* Built from source and ran unit tests.
* Ran the first quickstart steps for both ZK and KRaft.
* Spotchecked the Javadocs.
I am +1 (binding). Thanks for running the release!
Best,
David
On Tue, Jan 31, 2023 at 8:00
Hi,
thank you,
however I did not receive an e-mail with account details or ways to
setup the password. I tried the steps at
https://infra.apache.org/jira-guidelines.html#account but am blocked at the
step "If you need to log in, make sure you are using your ldap credentials
that you use for logging
I did the following:
- Validated all checksums and signatures
- Built from source and ran all the unit tests
- Ran quickstart steps for ZK, KRaft, and Kafka Streams (with KRaft)
- Spot checked the docs and Javadocs
Thanks for running the release!
+1(binding)
-Bill
On Fri, Feb 3,
Hi, we're investigating an issue where occasionally config changes don't
propagate to connectors/tasks.
When this occurs, the only way to ensure that the configuration takes effect is
to resize the number of tasks back down to 1 and then resize back up to the
original number of tasks.
In search
+1 (non-binding). I run my tests with the staged Scala 2.13 binaries and
staged Maven artifacts. All seems to work fine.
Thanks & Regards
Jakub
On Tue, Jan 31, 2023 at 8:01 PM David Arthur wrote:
> Hey folks, we found a couple of blockers with RC1 and have fixed them in
> the latest release can
+1 (non binding)
- Ran the unit and integration test suites with Java 17 and Scala 2.13
- Ran a series of basic examples and client configurations
- Spot checked the docs and Javadocs
Thanks
Fede
On Fri, Feb 3, 2023 at 5:29 PM Jakub Scholz wrote:
>
> +1 (non-binding). I run my tests with the st
Frank,
The inconsistentConnectors method is related to an extremely specific
inconsistency that can happen when a worker writes some task
configurations, and then disconnects without writing a following "commit
tasks record" to the config topic.
This is a hold-over from the early days of connect f
Frank,
I realized I didn't respond to the title directly, sorry about that.
The reason that `ClusterConfigState::inconsistentConnectors` is not used,
is that the effect of an inconsistent connector is applied via
`ClusterConfigState::tasks`.
If a connector is inconsistent, then the tasks method wi
Hi Jan,
It looks like there is another Jan Hendriks with the same username you
chose, I mistakenly thought another admin created your account.
Can you select another username other than dahoc or JanHendriks? Then we'll
get you squared away.
I'm sorry for the mixup.
Regards,
Bill
On Fri, Feb 3, 2
