Github user ConcurrencyPractitioner closed the pull request at:
https://github.com/apache/kafka/pull/4334
---
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/4340
[KAFKA-6265] GlobalKTable missing #queryableStoreName()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ConcurrencyPractitioner
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/4339
[KAFKA-6328] Exclude node groups belonging to global stores in
InternalTopologyBuilder#makeNodeGroups
You can merge this pull request into a Git repository by running:
$ git
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/4334
[KAFKA-6265] GlobalKTable missing #queryableStoreName()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/4258
[KAFKA-4499] Add all() and fetchAll() API for querying
*More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/4162
[KAFKA-4499] Add "getAllKeys" for querying windowed KTable stores
You can merge this pull request into a Git repository by running:
$ git pull https://
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/4110
[KAFKA-5212] Consumer ListOffsets request can starve group heartbeats
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/4049
[KAFKA-5212] Consumer ListOffsets request can starve group heartbeats
Through the identification of the poll method in ConsumerCoordinator as the
place where the heartbeat is sent
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/3916
KAFKA-5765 Move merge() from StreamsBuilder to KStream
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ConcurrencyPractitioner
Github user ConcurrencyPractitioner closed the pull request at:
https://github.com/apache/kafka/pull/3880
---
GitHub user ConcurrencyPractitioner reopened a pull request:
https://github.com/apache/kafka/pull/3880
KAFKA-5765 Move merge() from StreamsBuilder to KStream
I have defined a {{merge()}} method to KStream.
KStreamImpl overrides the {{merge()}} method.
You can merge this pull
Github user ConcurrencyPractitioner closed the pull request at:
https://github.com/apache/kafka/pull/3880
---
GitHub user ConcurrencyPractitioner reopened a pull request:
https://github.com/apache/kafka/pull/3880
KAFKA-5765 Move merge() from StreamsBuilder to KStream
I have defined a {{merge()}} method to KStream.
KStreamImpl overrides the {{merge()}} method.
You can merge this pull
Github user ConcurrencyPractitioner closed the pull request at:
https://github.com/apache/kafka/pull/3880
---
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/3880
KAFKA-5765 Move merge() from StreamsBuilder to KStream
I have defined a {{merge()}} method to KStream.
KStreamImpl overrides the {{merge()}} method.
You can merge this pull
Github user ConcurrencyPractitioner closed the pull request at:
https://github.com/apache/kafka/pull/3842
---
GitHub user ConcurrencyPractitioner reopened a pull request:
https://github.com/apache/kafka/pull/3842
KAFKA-5301 Improve exception handling on consumer path
This is an improvised approach towards fixing @guozhangwang 's second
issue.
I have changed the method return ty
Github user ConcurrencyPractitioner closed the pull request at:
https://github.com/apache/kafka/pull/3842
---
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/3842
[Kafka-5301] Improve exception handling on consumer path
This is an improvised approach towards fixing @guozhangwang 's second
issue.
I have changed the method return ty
GitHub user ConcurrencyPractitioner opened a pull request:
https://github.com/apache/kafka/pull/3745
[KAFKA-4468] Correctly calculate the window end timestamp after read from
state stores
I have decided to use the following approach to fixing this bug:
1) Since the Window
20 matches
Mail list logo
