Github user theduderog closed the pull request at:
https://github.com/apache/kafka/pull/1667
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1761
KAFKA-4064 Add support for infinite endpoints for range queries in Kafka
Streams KV stores
@guozhangwang
I had to fix the bug with in-memory ranges being exclusive and RocksDB
being
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1667
KAFKA-3993 Console Producer Drops Data
@ijuma Would you mind taking a look?
This fixes the problem for me using this test script.
```
export BOOTSTRAP_SERVERS=localhost
GitHub user theduderog reopened a pull request:
https://github.com/apache/kafka/pull/1437
KAFKA-3761: Remove BrokerState "RunningAsController"
The reasons to remove it are:
1. It's currently broken. The purpose of the
[JIRA](https://issues.apache.org/jira/browse/
Github user theduderog closed the pull request at:
https://github.com/apache/kafka/pull/1437
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1501
MINOR: Expose window store sequence number
@guozhangwang @mjsax @enothereska
Currently, Kafka Streams does not have a util to get access to the sequence
number added to the key
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1437
KAFKA-3761: Controller has RunningAsBroker instead of RunningAsController
state
@junrao @ijuma
This works for me in local testing. Do you see any issues?
You can merge this pull
Github user theduderog closed the pull request at:
https://github.com/apache/kafka/pull/1436
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1436
KAFKA-3760: Set broker state as running after publishing to ZooKeeper
Redoing PR #1426 with a JIRA
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1426
Setting broker state as running after publishing to ZK
@junrao
Currently, the broker state is set to running before it registers itself in
ZooKeeper. This is too early in the broker
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1309
Minor fixes to AWS init script for testing
A path was wrong in the script and in the documentation.
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1308
KAFKA-3650: Fix vagrant download URL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/theduderog/kafka fix_vagrant_dl
Alternatively you can
12 matches
Mail list logo
