[GitHub] kafka pull request: KAFKA-2957: Fix typos in Kafka documentation
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/641 KAFKA-2957: Fix typos in Kafka documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2957 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/641.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 #641 commit 3d2410946d3cd675de0ab4a45ee57bed18c3e4ca Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2015-12-08T19:29:50Z Fix some typos in documentation (resolves KAFKA-2957) --- 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: MINOR: Fix typos in code comments
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/662 MINOR: Fix typos in code comments You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo02/fix_typos_in_code_comments Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/662.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 #662 commit f61181d73d82ad9ed5cfe400926aa7e586bad1d8 Author: vahidhashemian <vahidhashem...@us.ibm.com> Date: 2015-12-10T19:54:45Z Merge pull request #1 from apache/trunk Update 2015-12-10 commit 56ea7b74dad8635039651fb00cbf830e9655bbbe Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2015-12-10T20:00:03Z Fix typos in source code comments --- 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: MINOR: Fix Broken Documentation Link
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/692 MINOR: Fix Broken Documentation Link The link to 'Producer Configs' section of the documentation is updated with this PR. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo03/fix_broken_doc_link Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/692.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 #692 commit af74e4ba84b1094c29a9882b71ea2f100af761ec Author: vahidhashemian <vahidhashem...@us.ibm.com> Date: 2015-12-17T20:38:45Z Merge pull request #3 from apache/trunk Update 2015-12-17 commit 32901158b4b042d15287335a208f7e529017b70c Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2015-12-17T22:28:55Z Fix broken link in documentation and code comments Fix the link pointing to 'Producer Configs' section in the documentation. --- 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: MINOR: Fix typos in code comments
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/673 MINOR: Fix typos in code comments You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo02/fix_typos_in_code_comments Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/673.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 #673 commit 8ecca04547822698ff01d002467624279a0a6b6e Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2015-12-10T20:00:03Z Fix typos in source code comments --- 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: MINOR: Fix typos in code comments
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/662 --- 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: Update 2015-12-21
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/706 --- 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: Update 2015-12-21
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/706 Update 2015-12-21 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/706.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 #706 commit af74e4ba84b1094c29a9882b71ea2f100af761ec Author: vahidhashemian <vahidhashem...@us.ibm.com> Date: 2015-12-17T20:38:45Z Merge pull request #3 from apache/trunk Update 2015-12-17 --- 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: MINOR: Fix typo in documentation
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/707 MINOR: Fix typo in documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo04/fix_documentation_typos Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/707.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 #707 commit 3f6dfb78af7b46d0d216cd605780f3b6db2d231c Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2015-12-21T23:42:11Z Fix a minor documentation typo --- 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: MINOR: Fix broken documentation link
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/692 --- 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: MINOR: Fix broken documentation link
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/692 MINOR: Fix broken documentation link The link to 'Producer Configs' section of the documentation is updated with this PR. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo03/fix_broken_doc_link Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/692.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 #692 commit af74e4ba84b1094c29a9882b71ea2f100af761ec Author: vahidhashemian <vahidhashem...@us.ibm.com> Date: 2015-12-17T20:38:45Z Merge pull request #3 from apache/trunk Update 2015-12-17 commit 32901158b4b042d15287335a208f7e529017b70c Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2015-12-17T22:28:55Z Fix broken link in documentation and code comments Fix the link pointing to 'Producer Configs' section in the documentation. --- 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 #1495: Minor: Respect the default value for partition arg...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1495 Minor: Respect the default value for partition argument in SimpleConsumerShell The `partition` argument is not marked as required, and has a default of `0`, according to the tool's help message. However, if `partition` is not provided the command returns with `Missing required argument "[partition]"`. This patch is to fix the required arguments of the tool by removing `partition` from them. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka minor/simple_consumer_shell_update_required_args Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1495.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 #1495 commit 54e7fba208d83526044d78b8ae85a428cb94157e Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-10T23:53:07Z Minor: Respect the default value for partition argument in SimpleConsumerShell The 'partition' argument is not marked as required, and has a default of 0, according to the tool's help message. However, if 'partition' is not provided the command returns with 'Missing required argument "[partition]"'. This patch is to fix the required arguments of the tool by removing 'partition' from them. --- 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 #1492: KAFKA-3818: Change Mirror Maker default assignment...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1492 --- 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 #1492: Change Mirror Maker default assignment strategy to...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1492 Change Mirror Maker default assignment strategy to round robin Update Mirror Maker to to use round robin assignment by default since it gives a better balance between the instances, in particular when the number of Mirror Maker instances exceeds the typical number of partitions per topic. There doesn't seem to be any need to keep range assignment since co-partitioning is not an issue. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3818 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1492.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 #1492 --- 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 #1493: KAFKA-3818: Change Mirror Maker default assignment...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1493 KAFKA-3818: Change Mirror Maker default assignment strategy to round robin Update Mirror Maker to use round robin assignment by default since it gives a better balance between the instances, in particular when the number of Mirror Maker instances exceeds the typical number of partitions per topic. There doesn't seem to be any need to keep range assignment since co-partitioning is not an issue. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3818 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1493.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 #1493 commit 24884d4ab13294d9e557e0698e9dafb672155208 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-10T22:29:06Z KAFKA-3818: Change Mirror Maker default assignment strategy to round robin It might make more sense to use round robin assignment by default for Mirror Maker since it gives a better balance between the instances, in particular when the number of Mirror Maker instances exceeds the typical number of partitions per topic. There doesn't seem to be any need to keep range assignment since copartitioning is not an issue. --- 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 #1499: KAFKA-3831: Prepare for updating Mirror Maker's de...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1499 KAFKA-3831: Prepare for updating Mirror Maker's default partition assignment strategy to round robin This patch adds proper warning message and necessary doc updates for updating the default partition assignment strategy of Mirror Maker from range to round robin. The actual switch would occur as part of a major release cycle (to be scheduled). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3831 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1499.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 #1499 commit 4ee0fd612f0e34a8a218de237fb869904b49af7e Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-13T17:08:49Z KAFKA-3831: Prepare for updating Mirror Maker's default partition assignment strategy to round robin This patch adds proper warning message and necessary doc updates for updating the default partition assignment strategy of Mirror Maker from range to round robin. The actual switch would occur as part of a major release cycle (to be scheduled). --- 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 #1500: MINOR: Fix javadoc typos in ConsumerRebalanceListe...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1500 MINOR: Fix javadoc typos in ConsumerRebalanceListener You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo07/fix_javadoc_typos_consumerrebalancelistener Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1500.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 #1500 commit b1548d2dc0bafe4513922790756b7d60dc101201 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-13T20:02:46Z MINOR: Fix Javadoc Typos in ConsumerRebalanceListener --- 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: MINOR: Fix a couple of typos
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1440 MINOR: Fix a couple of typos You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo06/fix_typos_in_code_comments Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1440.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 #1440 commit d0898e35c2e3d1a6630256bd38a71dbb5365ea9e Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-27T16:15:42Z MINOR: Fix a couple of typos --- 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 #1457: KAFKA-3774: Make 'time' an optional argument of Ge...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1457 KAFKA-3774: Make 'time' an optional argument of GetOffsetShell tool Since the 'time' argument has a default value of -1, it makes sense to make it an optional argument. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3774 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1457.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 #1457 commit aee6b5aba22394f4f7fba6b5e5bacc21acf96986 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-01T20:48:33Z KAFKA-3774: Make 'time' an optional argument of GetOffsetShell tool Since the 'time' argument has a default value of -1, it makes sense to make it an optional argument. --- 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 #1536: MINOR: KAFKA-3176 Follow-up to fix minor issues
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1536 --- 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 #1536: MINOR: KAFKA-3176 Follow-up to fix minor issues
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1536 MINOR: KAFKA-3176 Follow-up to fix minor issues You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka minor/KAFKA-3176-Followup Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1536.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 #1536 commit 843026de9c224235fe46f3fc0e882cfd4f4fbf15 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-21T17:36:53Z MINOR: KAFKA-3176 Follow-up to fix minor issues --- 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 #1536: MINOR: KAFKA-3176 Follow-up to fix minor issues
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1536 MINOR: KAFKA-3176 Follow-up to fix minor issues You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka minor/KAFKA-3176-Followup Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1536.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 #1536 commit 843026de9c224235fe46f3fc0e882cfd4f4fbf15 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-21T17:36:53Z MINOR: KAFKA-3176 Follow-up to fix minor issues --- 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 #1500: MINOR: Fix javadoc typos in ConsumerRebalanceListe...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1500 --- 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 #1500: MINOR: Fix javadoc typos in ConsumerRebalanceListe...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1500 MINOR: Fix javadoc typos in ConsumerRebalanceListener You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo07/fix_javadoc_typos_consumerrebalancelistener Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1500.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 #1500 commit 7e4bfffe54ae8b9ffdd3549e2973067c86ff6712 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-06-13T20:02:46Z MINOR: Fix Javadoc Typos in ConsumerRebalanceListener --- 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 #922: KAFKA-3176: Add partition/offset options to the new...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- 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 #922: KAFKA-3176: Add partition/offset options to the new...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to the new consumer With this pull request the new console consumer can be provided with optional --partition and --offset arguments so only messages from a particular partition and starting from a particular offset are consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition or --offset is provided --new-consumer has to be provided too. - If --partition is provided --topic has to be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. This patch is co-authored with @rajinisivaram. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3176 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/922.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 #922 commit 5058e4f1c81ed8f47f021248490cf8d3ad1ecc3c Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-16T13:24:38Z KAFKA-3176: Add partition/offset options to the new console consumer With this feature the new console consumer can be provided with optional --partition and --offset arguments so messages from a particular partition and starting from a particular offset are consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition and/or --offset are provided --new-consumer has to be provided too. - If --partition is provided --topic has to be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. --- 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 #922: KAFKA-3176: Add partition/offset options to the new...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- 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 #1336: KAFKA-3144: Report members with no assigned partit...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1336 --- 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 #922: KAFKA-3176: Add partition/offset options to the new...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to the new consumer With this pull request the new console consumer can be provided with optional --partition and --offset arguments so only messages from a particular partition and starting from a particular offset are consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition or --offset is provided --new-consumer has to be provided too. - If --partition is provided --topic has to be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. This patch is co-authored with @rajinisivaram. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3176 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/922.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 #922 commit 5058e4f1c81ed8f47f021248490cf8d3ad1ecc3c Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-16T13:24:38Z KAFKA-3176: Add partition/offset options to the new console consumer With this feature the new console consumer can be provided with optional --partition and --offset arguments so messages from a particular partition and starting from a particular offset are consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition and/or --offset are provided --new-consumer has to be provided too. - If --partition is provided --topic has to be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. --- 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 #1336: KAFKA-3144: Report members with no assigned partit...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1336 KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes a couple of enhancements to the `--describe` option of `ConsumerGroupCommand`: 1. Listing members with no assigned partitions. 2. Showing the member id along with the owner of each partition (owner is supposed to be the logical application id and all members in the same group are supposed to set the same owner). Note: The third request on the corresponding JIRA (listing group active offsets for groups with no members for the new consumer) is not implemented as part of this PR. I suggest moving that into a separate JIRA as it seems to be a more involved change and potentially requires making changes to the server side too. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3144 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1336.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 #1336 commit 861ec0425a20b1e57b076c821907a644545344ea Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-06T22:16:38Z KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes some enhancements to the implementation of the "--describe" option of ConsumerGroupCommand: 1. Listing members with no assigned partitions. 2. Showing the member id along with the owner of each partition (owner is supposed to be the logical application id and all members in the same group are supposed to set the same owner). Note: The third request on the corresponding JIRA (listing group active offsets for groups with no members for the new consumer) is moved to KAFKA-3853. --- 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 #922: KAFKA-3176: Add partition/offset options to the new...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to the new consumer With this pull request the new console consumer can be provided with optional --partition and --offset arguments so only messages from a particular partition and starting from a particular offset are consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition or --offset is provided --new-consumer has to be provided too. - If --partition is provided --topic has to be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. This patch is co-authored with @rajinisivaram. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3176 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/922.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 #922 commit 5058e4f1c81ed8f47f021248490cf8d3ad1ecc3c Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-16T13:24:38Z KAFKA-3176: Add partition/offset options to the new console consumer With this feature the new console consumer can be provided with optional --partition and --offset arguments so messages from a particular partition and starting from a particular offset are consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition and/or --offset are provided --new-consumer has to be provided too. - If --partition is provided --topic has to be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. --- 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 #922: KAFKA-3176: Add partition/offset options to the new...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- 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 #1336: KAFKA-3144: Report members with no assigned partit...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1336 KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes a couple of enhancements to the `--describe` option of `ConsumerGroupCommand`: 1. Listing members with no assigned partitions. 2. Showing the member id along with the owner of each partition (owner is supposed to be the logical application id and all members in the same group are supposed to set the same owner). Note: The third request on the corresponding JIRA (listing group active offsets for groups with no members for the new consumer) is not implemented as part of this PR. I suggest moving that into a separate JIRA as it seems to be a more involved change and potentially requires making changes to the server side too. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3144 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1336.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 #1336 commit 861ec0425a20b1e57b076c821907a644545344ea Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-06T22:16:38Z KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes some enhancements to the implementation of the "--describe" option of ConsumerGroupCommand: 1. Listing members with no assigned partitions. 2. Showing the member id along with the owner of each partition (owner is supposed to be the logical application id and all members in the same group are supposed to set the same owner). Note: The third request on the corresponding JIRA (listing group active offsets for groups with no members for the new consumer) is moved to KAFKA-3853. --- 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 #1336: KAFKA-3144: Report members with no assigned partit...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1336 --- 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: MINOR: Improve Kafka documentation
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/778 MINOR: Improve Kafka documentation Improve the documentation by fixing typos, punctuations, and correcting the content. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka typo05/fix_documentation_typos Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/778.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 #778 commit 94f9ba73131470be8bcbf8d9dfcd8f7994e70a7b Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-01-14T22:19:07Z MINOR: Improve Kafka documentation Improve the documentation by fixing typos, punctuations, and correcting the content. --- 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: KAFKA-3111: Fix ConsumerPerformance output for...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/788 --- 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: KAFKA-3111: Fix ConsumerPerformance output for...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/788 KAFKA-3111: Fix ConsumerPerformance output for zero interval lengths Interval lengths for ConsumerPerformance could sometime be calculated as zero. In such cases, when the bytes read or messages read are also zero a NaN output is returned for mbRead per second or for nMsg per second, whereas zero would be a more appropriate output. In cases where interval length is zero but there have been data and messages to read, an output of Infinity is returned, as expected. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3111 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/788.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 #788 commit 34c54e98c5e641986d74506edfd17b0c0ba105c2 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-01-18T21:50:02Z KAFKA-3111: Fix ConsumerPerformance output for zero interval lengths --- 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: KAFKA-3111: Fix ConsumerPerformance output for...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/788 KAFKA-3111: Fix ConsumerPerformance output for zero interval lengths Interval lengths for ConsumerPerformance could sometime be calculated as zero. In such cases, when the bytes read or messages read are also zero a NaN output is returned for mbRead per second or for nMsg per second, whereas zero would be a more appropriate output. In cases where interval length is zero but there have been data and messages to read, an output of Infinity is returned, as expected. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3111 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/788.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 #788 commit 34c54e98c5e641986d74506edfd17b0c0ba105c2 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-01-18T21:50:02Z KAFKA-3111: Fix ConsumerPerformance output for zero interval lengths --- 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: KAFKA-3219: Fix long topic name validation
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/898 KAFKA-3219: Fix long topic name validation This fixes an issue with long topic names by considering, during topic validation, the '-' and the partition id that is appended to the log folder created for each topic partition. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3219 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/898.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 #898 commit 413f1f657b810032c94c8d59908e4bc5e39c26fe Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-10T16:37:35Z KAFKA-3219: Fix long topic name validation This fixes an issue with long topic names by considering, during topic validation, the '-' and the partition id that is appended to the log folder created for each topic partition. --- 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: KAFKA-2832: Add a consumer config option to ex...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/932 KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are used to specify consumers. The new option takes a boolean value, with a default 'false' value (i.e. no exclusion). This patch is co-authored with @rajinisivaram. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2832 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/932.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 #932 commit 1b03ad9d1e8dd0a40adb3272ff857c48289b1e05 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-18T15:53:39Z KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are used to specify consumers. The new option takes a boolean value, with a default of 'true' (i.e. exclude internal topics). This patch is co-authored with @rajinisivaram. --- 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: KAFKA-2832: Add a consumer config option to ex...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/932 --- 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: KAFKA-3116: Specify minimum Gradle version req...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/813 KAFKA-3116: Specify minimum Gradle version required in Readme You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3116 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/813.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 #813 commit 977a257a6cbff1a7293ba1ae6fefa2b0ec32fea0 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-01-26T19:52:20Z KAFKA-3116: Update Readme to specify minimum Gradle version for buliding Kafka --- 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: KAFKA-3116: Specify minimum Gradle version req...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/813 --- 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: KAFKA-3116: Specify minimum Gradle version req...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/813 KAFKA-3116: Specify minimum Gradle version required in Readme You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3116 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/813.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 #813 commit 977a257a6cbff1a7293ba1ae6fefa2b0ec32fea0 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-01-26T19:52:20Z KAFKA-3116: Update Readme to specify minimum Gradle version for buliding Kafka --- 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: KAFKA-3176: Add partition/offset options to bo...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to both old and new console consumers With this pull request both old and new console consumers can be provided with optional --partition and --offset arguments so messages from a particular partition and starting from a particular offset are only consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition is provided --topic has to be provided too. - If --partition is provided --bootstrap-server (and not --zookeeper) should be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3176 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/922.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 #922 commit 5164a0d7ae344bb6cded0975849f6d36f9596982 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-16T13:24:38Z Add partition/offset options to both old and new console consumers With this change both old and new console consumers can be provided with optional --partition and --offset arguments so messages from a particular partition and starting from a particular offset are only consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition is provided --topic has to be provided too. - If --partition is provided --bootstrap-server (and not --zookeeper) should be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. --- 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: KAFKA-3176: Add partition/offset options to bo...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to both old and new console consumers With this pull request both old and new console consumers can be provided with optional --partition and --offset arguments so messages from a particular partition and starting from a particular offset are only consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition is provided --topic has to be provided too. - If --partition is provided --bootstrap-server (and not --zookeeper) should be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3176 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/922.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 #922 commit 5164a0d7ae344bb6cded0975849f6d36f9596982 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-16T13:24:38Z Add partition/offset options to both old and new console consumers With this change both old and new console consumers can be provided with optional --partition and --offset arguments so messages from a particular partition and starting from a particular offset are only consumed. The following rules are also implemented to avoid invalid combinations of arguments: - If --partition is provided --topic has to be provided too. - If --partition is provided --bootstrap-server (and not --zookeeper) should be provided too. - If --offset is provided --partition has to be provided too. - --offset and --from-beginning cannot be used at the same time. --- 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: KAFKA-3176: Add partition/offset options to bo...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- 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: KAFKA-2832: Add a consumer config option to ex...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/932 KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are used to specify consumers. The new option takes a boolean value, with a default 'false' value (i.e. no exclusion). This patch is co-authored with @rajinisivaram. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2832 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/932.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 #932 commit 558e49a39dca3004203707b791dbd371fad0d5db Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-18T15:53:39Z KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are used to specify consumers. The new option takes a boolean value, with a default 'false' value (i.e. no exclusion). This patch is co-authored with @rajinisivaram. --- 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: KAFKA-2832: Add a consumer config option to ex...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/932 KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are used to specify consumers. The new option takes a boolean value, with a default 'false' value (i.e. no exclusion). This patch is co-authored with @rajinisivaram. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2832 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/932.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 #932 commit ca4c47fce1a2c6615bf41a68249ffc7e315ea12f Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-18T15:53:39Z KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are used to specify consumers. The new option takes a boolean value, with a default of 'true' (i.e. exclude internal topics). This patch is co-authored with @rajinisivaram. --- 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: KAFKA-2832: Add a consumer config option to ex...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/932 --- 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: KAFKA-3312: Add utility offset methods to ZkUt...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1025 KAFKA-3312: Add utility offset methods to ZkUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3312 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1025.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 #1025 commit 8ee7711d11c6eb32f160c66202c54af2e17c3ed6 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-03-05T00:47:05Z KAFKA-3312: Add utility offset methods to ZkUtils --- 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: KAFKA-2273: Sticky partition assignment strate...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1020 KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or, in other words, preserves existing partition assignments as much as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2273 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1020.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 #1020 commit 1f774ea784e57377752f55dd4fe91212e8bcbda1 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-18T13:44:17Z KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or in other words, preserving partition assignments as much as possible. --- 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: KAFKA-2273: Sticky partition assignment strate...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1020 --- 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: KAFKA-2273: Sticky partition assignment strate...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1020 KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or, in other words, preserves existing partition assignments as much as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2273 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1020.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 #1020 commit 2a48c9fbf9260d6c8659a97ae2c8673607badd13 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-18T13:44:17Z KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or in other words, preserving partition assignments as much as possible. --- 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: KAFKA-3312: Add utility offset methods to ZkUt...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1025 KAFKA-3312: Add utility offset methods to ZkUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3312 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1025.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 #1025 commit ac6d6926d5e23640b53fa2bca927ae5e423c12f7 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-03-05T00:47:05Z KAFKA-3312: Add utility offset methods to ZkUtils --- 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: KAFKA-2273: Sticky partition assignment strate...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1020 KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or, in other words, preserves existing partition assignments as much as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2273 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1020.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 #1020 commit 2a48c9fbf9260d6c8659a97ae2c8673607badd13 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-18T13:44:17Z KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or in other words, preserving partition assignments as much as possible. --- 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: KAFKA-2273: Sticky partition assignment strate...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1020 --- 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: KAFKA-2273: Sticky partition assignment strate...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1020 --- 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: KAFKA-2273: Sticky partition assignment strate...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1020 KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or, in other words, preserves existing partition assignments as much as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-2273 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1020.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 #1020 commit 2a48c9fbf9260d6c8659a97ae2c8673607badd13 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-02-18T13:44:17Z KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way that minimizes moving partitions around, or in other words, preserving partition assignments as much as possible. --- 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: KAFKA-3312: Add utility offset methods to ZkUt...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1025 KAFKA-3312: Add utility offset methods to ZkUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3312 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1025.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 #1025 commit 8ee7711d11c6eb32f160c66202c54af2e17c3ed6 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-03-05T00:47:05Z KAFKA-3312: Add utility offset methods to ZkUtils --- 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: KAFKA-3312: Add utility offset methods to ZkUt...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1025 --- 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: KAFKA-3312: Add utility offset methods to ZkUt...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1025 --- 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: KAFKA-3614: Consolidate duplicate code in KGro...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1268 KAFKA-3614: Consolidate duplicate code in KGroupedTableImpl Two methods aggregate() and reduce() share common code that is consolidated in this patch. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3614 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1268.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 #1268 commit 70a2e718bbd8b50f561002751e968392e54af280 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-04-25T21:56:07Z KAFKA-3614: Consolidate duplicate code in KGroupedTableImpl Two methods aggregate() and reduce() share common code that is consolidated in this patch. --- 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: KAFKA-3614: Consolidate duplicate code in KGro...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1268 --- 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: KAFKA-3579 - Update reference to the outdated ...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3579 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1239.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 #1239 commit 0940eb35c989cb2610ccc152f368d80a87683ea1 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-04-19T18:21:45Z KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. Also create and leverage a static variable for the default value of the new consumer property. --- 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: KAFKA-3579 - Update reference to the outdated ...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1239 --- 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: KAFKA-3579 - Update reference to the outdated ...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1239 --- 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: KAFKA-3579 - Update reference to the outdated ...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3579 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1239.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 #1239 --- 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: KAFKA-3608: Fix ZooKeeper structures and outpu...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1257 KAFKA-3608: Fix ZooKeeper structures and output format in documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3608 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1257.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 #1257 commit 61157d384741a8348c49be98350d77638bf18413 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-04-22T18:31:26Z KAFKA-3608: Fix ZooKeeper structures and output format in documentation --- 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: KAFKA-3579 - Update reference to the outdated ...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3579 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1239.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 #1239 commit fbd579331e8136209356bc572e978908fbde2c1e Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-04-19T18:21:45Z KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. --- 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: KAFKA-3579 - Update reference to the outdated ...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1239 --- 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: KAFKA-3608: Fix ZooKeeper structures and outpu...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1257 --- 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: KAFKA-3579 - Update reference to the outdated ...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3579 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1239.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 #1239 commit 86239fb3b9271ad6b06740fb8b16374242119346 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-04-19T18:21:45Z KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. Also create and leverage a static variable for the default value of the new consumer property. --- 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: KAFKA-3579 - Update reference to the outdated ...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1239 --- 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: KAFKA-3664: Commit offset of unsubscribed part...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1363 --- 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: KAFKA-3664: Commit offset of unsubscribed part...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1363 --- 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: KAFKA-3664: Commit offset of unsubscribed part...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 commit 68e6b5507e6c587b035655c5c010bef5c282c7f7 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-13T00:23:27Z KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions are immediately removed and their offset are not committed. This pull request fixes this issue. --- 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: KAFKA-3664: Commit offset of unsubscribed part...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 commit 68e6b5507e6c587b035655c5c010bef5c282c7f7 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-13T00:23:27Z KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions are immediately removed and their offset are not committed. This pull request fixes this issue. --- 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: KAFKA-3664: Commit offset of unsubscribed part...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1363 --- 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: KAFKA-3664: Commit offset of unsubscribed part...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 commit 7794f181ce65bf7fe5800dd792eb996e5aba71e1 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-13T00:23:27Z KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions are immediately removed and their offset are not committed. This pull request fixes this issue. --- 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: KAFKA-3664: Commit offset of unsubscribed part...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 commit 68e6b5507e6c587b035655c5c010bef5c282c7f7 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-13T00:23:27Z KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions are immediately removed and their offset are not committed. This pull request fixes this issue. --- 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: KAFKA-3664: Commit offset of unsubscribed part...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1363 --- 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: KAFKA-3664 (WIP): Commit offset of unsubscribe...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664 (WIP): Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 commit 68e6b5507e6c587b035655c5c010bef5c282c7f7 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-13T00:23:27Z KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions are immediately removed and their offset are not committed. This pull request fixes this issue. --- 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: KAFKA-3664 (WIP): Commit offset of unsubscribe...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1363 --- 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: KAFKA-3664: Commit offset of unsubscribed part...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 commit 68e6b5507e6c587b035655c5c010bef5c282c7f7 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-13T00:23:27Z KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions are immediately removed and their offset are not committed. This pull request fixes this issue. --- 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: KAFKA-3664: Commit offset of unsubscribed part...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1363 --- 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: KAFKA-3664: Commit offset of unsubscribed part...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 commit 68e6b5507e6c587b035655c5c010bef5c282c7f7 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-13T00:23:27Z KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions are immediately removed and their offset are not committed. This pull request fixes this issue. --- 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: KAFKA-3664: Commit offset of unsubscribed part...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1363 --- 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: KAFKA-3664: Commit unsubscribed partitions of ...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed. Also the revoked partitions passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not include those partitions. This pull request fixes this issue by following the design suggested by @becketqin [here](https://issues.apache.org/jira/browse/KAFKA-3664?focusedCommentId=15274470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15274470). You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3664 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1363.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 #1363 --- 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: KAFKA-3312: Add utility offset methods to ZkUt...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1025 KAFKA-3312: Add utility offset methods to ZkUtils Create utility getOffset(...) and updateOffset(...) methods to replace readData(...), readDataMaybeNull(...) and updatePersistentPath(...) method calls where they deal with getting or setting offsets. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3312 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1025.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 #1025 commit d379ef6944e7dbed930f97ff51f6c9f98e9f9376 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-03-05T00:47:05Z KAFKA-3312: Add utility offset methods to ZkUtils Create utility getOffset(...) and updateOffset(...) methods to replace readData(...), readDataMaybeNull(...) and updatePersistentPath(...) method calls where they deal with getting or setting offsets. --- 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: KAFKA-3312: Add utility offset methods to ZkUt...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1025 --- 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: KAFKA-2832: Add a consumer config option to ex...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/932 --- 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: KAFKA-3579 - Update reference to the outdated ...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3579 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1239.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 #1239 commit 818650dbdf4ef6184bc6c2496813524810646947 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-04-19T18:21:45Z KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. --- 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: KAFKA-3579 - Update reference to the outdated ...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1239 --- 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: KAFKA-3579 - Update reference to the outdated ...
GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3579 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1239.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 #1239 commit fbd579331e8136209356bc572e978908fbde2c1e Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-04-19T18:21:45Z KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new consumer 'max.partition.fetch.bytes'. --- 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: KAFKA-3144: Report members with no assigned pa...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1336 KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes a couple of enhancements to the `--describe` option of `ConsumerGroupCommand`: 1. Listing members with no assigned partitions. 2. Showing the member id along with the owner of each partition (owner is supposed to be the logical application id and all members in the same group are supposed to set the same owner). Note: The third request on the corresponding JIRA (listing group active offsets for groups with no members for the new consumer) is not implemented as part of this PR. I suggest moving that into a separate JIRA as it seems to be a more involved change and potentially requires making changes to the server side too. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3144 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1336.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 #1336 commit 9e9561cd27ec7c81a86317bd2746ec8fb0b46c5e Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-05-06T22:16:38Z KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes some enhancements to the implementation of the "--describe" option of ConsumerGroupCommand: 1. Listing members with no assigned partitions. 2. Showing the member id along with the owner of each partition (owner is supposed to be the logical application id and all members in the same group are supposed to set the same owner). Note: The third request on the corresponding JIRA (listing group active offsets for groups with no members for the new consumer) is not implemented as part of this PR. I suggest moving that into a separate JIRA as it seems to be a more involved change and potentially requires making changes to the server side too. --- 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 #1618: KAFKA-3945: Fix validation of 'acks' config in con...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1618 KAFKA-3945: Fix validation of 'acks' config in console producer The `acks` config that is provided to console producer with `request-required-acks` comes with `all`, `-1`, `0`, `1` as valid options (`all` and `-1` being interchangeable). This PR input validation so that `all` is also accepted as an input value. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3945 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1618.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 #1618 commit fba6a2b1e272a43196b7d7125e202b9da3f29949 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-07-12T23:03:04Z KAFKA-3945: Fix validation of 'acks' config in console producer The 'acks' config that is provided to console producer with 'request-required-acks' comes with 'all', -1, 0, 1 as valid options (with 'all' and -1 being interchangeable). This PR input validation so that 'all' is also accepted as an input value. --- 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 #1655: KAFKA-3982: Fix processing order of some of the co...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1655 KAFKA-3982: Fix processing order of some of the consumer properties This PR updates processing of console consumer's input properties. For both old and new consumer, the value provided for `auto.offset.reset` indirectly through `consumer.config` or `consumer.property` arguments will now take effect. For new consumer and for `key.deserializer` and `value.deserializer` properties, the precedence order is fixed to first the value directly provided as an argument, then the value provided indirectly via `consumer.property` and then `consumer.config`, and finally a default value. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3982 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1655.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 #1655 commit 6e112c8d097d55cbd5cd6dd81077180b89f175e3 Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-07-22T20:48:59Z KAFKA-3982: Fix processing order of some of the consumer properties This PR updates processing of console consumer's input properties. For both old and new consumer, the value provided for `auto.offset.reset` indirectly through `consumer.config` or `consumer.property` arguments will now take effect. For new consumer and for `key.deserializer` and `value.deserializer` properties, the precedence is fixed to first the value directly provided as an argument, then the value provided indirectly via `consumer.property` and then `consumer.config`, and finally a default value. --- 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 #1684: KAFKA-4000: Aggregate partitions of each topic for...
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1684 KAFKA-4000: Aggregate partitions of each topic for consumer metrics Fix the consumer metric collection to record metrics per topic instead of per partition of topic. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-4000 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1684.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 #1684 commit a69c8fe3d1a9d99310f99db4821a6d70cf06104b Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-07-29T20:55:14Z KAFKA-4000: Aggregate partitions of each topic for consumer metrics Fix the consumer metric collection to record metrics per topic instead of per partition of topic. --- 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 #1698: KAFKA-3999: Record raw size of fetch responses
GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1698 KAFKA-3999: Record raw size of fetch responses Currently, only the decompressed size of fetch responses is recorded. This PR adds a sensor to keep track of the raw size as well. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3999 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1698.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 #1698 commit ae9b0abf60e20923761eda7d5f351625a2b2c0dc Author: Vahid Hashemian <vahidhashem...@us.ibm.com> Date: 2016-08-02T23:07:27Z KAFKA-3999: Record raw size of fetch responses Currently, only the decompressed size of fetch responses is recorded. This PR adds a sensor to keep track of their raw size as well. --- 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 #1698: KAFKA-3999: Record raw size of fetch responses as ...
Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1698 --- 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. ---
