[GitHub] kafka pull request #4081: KAFKA-6069: Properly tag KafkaStreams metrics with...
GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/4081 KAFKA-6069: Properly tag KafkaStreams metrics with the client id. You can merge this pull request into a Git repository by running: $ git pull https://github.com/twbecker/kafka KAFKA-6069 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/4081.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4081 commit d97881df251674b4c7f3d3f9a270b4691dc262c4 Author: Tommy Becker Date: 2017-10-17T13:48:07Z Properly tag KafkaStreams metrics with the client id. ---
[GitHub] kafka pull request #3455: KAFKA-5379 - ProcessorContext.appConfigs() should ...
GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/3455 KAFKA-5379 - ProcessorContext.appConfigs() should return parsed values. You can merge this pull request into a Git repository by running: $ git pull https://github.com/twbecker/kafka kafka-5379 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3455.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3455 commit 8ce6197f8190c74b5c6cb665af86432daaf2 Author: Tommy Becker Date: 2017-06-28T15:06:21Z KAFKA-5379 - ProcessorContext.appConfigs() should return parsed values. --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #3155: Fix KAKFA-5334.
GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/3155 Fix KAKFA-5334. Handle` rocksdb.config.setter` being set as a class name or class instance. You can merge this pull request into a Git repository by running: $ git pull https://github.com/twbecker/kafka KAFKA-5334 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3155.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3155 commit 08b837410b5a2fbdf65727f46c44d1a008897708 Author: Tommy Becker Date: 2017-05-26T14:25:31Z Fix KAKFA-5334. Handle rocksdb.config.setter being set as a class name or class instance. --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #3054: KAFKA-5241: GlobalKTable does not checkpoint offse...
GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/3054 KAFKA-5241: GlobalKTable does not checkpoint offsets after restoring state Ensure checkpointable offsets for GlobalKTables are always written on close. You can merge this pull request into a Git repository by running: $ git pull https://github.com/twbecker/kafka KAFKA-5241 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3054.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3054 commit 4f7263768ef73d18cf6b90894f4a0286bc79ea14 Author: Tommy Becker Date: 2017-05-15T12:13:07Z Fix KAFKA-5241. Ensure checkpointable offsets for GlobalKTables are always written on close. --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2827: Fix KAFKA-5044.
Github user twbecker closed the pull request at: https://github.com/apache/kafka/pull/2827 --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2827: Fix KAFKA-5044.
GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/2827 Fix KAFKA-5044. InFlightRequests#canSendMore should not require that previous sends completed if we are under the maxInFlightRequestsPerConnection limit. You can merge this pull request into a Git repository by running: $ git pull https://github.com/twbecker/kafka KAFKA-5044 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2827.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2827 commit fb3887d81eabd9af35e153bf0b5435623e01da3f Author: Tommy Becker Date: 2017-04-07T22:27:40Z Fix KAFKA-5044. InFlightRequests#canSendMore should not require that previous sends completed if we are under the maxInFlightRequestsPerConnection limit. --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2826: Fix KAFKA-5044.
Github user twbecker closed the pull request at: https://github.com/apache/kafka/pull/2826 --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2826: Fix KAFKA-5042.
GitHub user twbecker opened a pull request: https://github.com/apache/kafka/pull/2826 Fix KAFKA-5042. InFlightRequests#canSendMore should not require that previous sends completed if we are under the maxInFlightRequestsPerConnection limit. You can merge this pull request into a Git repository by running: $ git pull https://github.com/twbecker/kafka KAFKA-5042 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2826.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2826 commit 7769b58e12be2f5ff0d9af44126b761620399ecb Author: Tommy Becker Date: 2017-04-07T22:27:40Z Fix KAFKA-5042. InFlightRequests#canSendMore should not require that previous sends completed if we are under the maxInFlightRequestsPerConnection limit. --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
