[GitHub] kafka pull request #1787: KAFKA-3940 Log should check the return value of di...

2017-01-27 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1787


---
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 #2203: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2017-01-27 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/2203


---
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 #2288: MINOR: Create Hyperlinks in protocol api docs

2017-01-27 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/2288


---
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 #2288: MINOR: Create Hyperlinks in protocol api docs

2016-12-21 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/2288

MINOR: Create Hyperlinks in protocol api docs

Minor changes to generate hyperlinks in the protocol api documentation to 
ease lookup.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka HyperLink

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2288.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 #2288


commit d2afdc4d917ab4abeba4cbde5e4a9dd8eb985f7a
Author: Ishita Mandhan 
Date:   2016-12-22T03:18:53Z

MINOR: Create Hyperlinks in protocol api docs




---
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 #2203: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-12-02 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/2203

KAFKA-2857 ConsumerGroupCommand throws GroupCoordinatorNotAvailableEx…

…ception when describing a non-existent group before the offset topic is 
created #1548 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-2857-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2203.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 #2203


commit ea3a0609388d19caf2de6587a5efdbcb851a3224
Author: Ishita Mandhan 
Date:   2016-12-02T09:45:57Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created #1548




---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-12-02 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1548


---
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 #2013: MINOR: Code refactor - cleaning up some boolean as...

2016-10-17 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/2013


---
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 #2013: MINOR: Code refactor - cleaning up some boolean as...

2016-10-17 Thread imandhan
GitHub user imandhan reopened a pull request:

https://github.com/apache/kafka/pull/2013

MINOR: Code refactor - cleaning up some boolean assignments



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-refactor

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2013.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 #2013


commit a9d3b4369a11943c389e0ccc20ccfbafee0ce6f4
Author: Ishita Mandhan 
Date:   2016-10-12T00:51:29Z

MINOR: Code Refactor

Refactored some if else statements which had a boolean type and a boolean 
in the conditional, to remove explicitly stated booleans; cleaning up the code 
a little. For example - if (x==1) true else false is changed to (x==1)

commit db02aafdfcbc9b37587abd7a7f84f9d4edd66454
Author: Ishita Mandhan 
Date:   2016-10-12T00:51:29Z

MINOR: Code Refactor

Refactored some if else statements which had a boolean type and a boolean 
in the conditional, to remove explicitly stated booleans; cleaning up the code 
a little. For example - if (x==1) true else false is changed to (x==1)

commit 1813f6e759edeb99b8e91fae7e077afa7522fce4
Author: Ishita Mandhan 
Date:   2016-10-12T01:04:37Z

Merge branch 'KAFKA-refactor' of https://github.com/imandhan/kafka into 
KAFKA-refactor

commit 6050ca9a3c8ec7236df85c2778d593074355e7ce
Author: Ishita Mandhan 
Date:   2016-10-12T01:04:37Z

Merge branch 'KAFKA-refactor' of https://github.com/imandhan/kafka into 
KAFKA-refactor

commit dccea554822f7e41e84f7db035ff881d0022468d
Author: Ishita Mandhan 
Date:   2016-10-12T02:59:08Z

Merge branch 'KAFKA-refactor' of https://github.com/imandhan/kafka into 
KAFKA-refactor




---
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 #2013: MINOR: Code refactor - cleaning up some boolean as...

2016-10-11 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/2013

MINOR: Code refactor - cleaning up some boolean assignments



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-refactor

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2013.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 #2013


commit a9d3b4369a11943c389e0ccc20ccfbafee0ce6f4
Author: Ishita Mandhan 
Date:   2016-10-12T00:51:29Z

MINOR: Code Refactor

Refactored some if else statements which had a boolean type and a boolean 
in the conditional, to remove explicitly stated booleans; cleaning up the code 
a little. For example - if (x==1) true else false is changed to (x==1)

commit db02aafdfcbc9b37587abd7a7f84f9d4edd66454
Author: Ishita Mandhan 
Date:   2016-10-12T00:51:29Z

MINOR: Code Refactor

Refactored some if else statements which had a boolean type and a boolean 
in the conditional, to remove explicitly stated booleans; cleaning up the code 
a little. For example - if (x==1) true else false is changed to (x==1)

commit 1813f6e759edeb99b8e91fae7e077afa7522fce4
Author: Ishita Mandhan 
Date:   2016-10-12T01:04:37Z

Merge branch 'KAFKA-refactor' of https://github.com/imandhan/kafka into 
KAFKA-refactor




---
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 #1787: KAFKA-3940 Log should check the return value of di...

2016-08-29 Thread imandhan
GitHub user imandhan reopened a pull request:

https://github.com/apache/kafka/pull/1787

KAFKA-3940 Log should check the return value of dir.mkdirs()



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3940

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1787.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 #1787


commit e3f5f293104013da3aa765c9ba7cbdb2553f6485
Author: Ishita Mandhan 
Date:   2016-08-25T21:38:16Z

KAFKA-3940 Log should check the return value of dir.mkdirs()




---
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 #1787: KAFKA-3940 Log should check the return value of di...

2016-08-29 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1787


---
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 #1787: KAFKA-3940 Log should check the return value of di...

2016-08-25 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1787

KAFKA-3940 Log should check the return value of dir.mkdirs()



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3940

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1787.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 #1787


commit e3f5f293104013da3aa765c9ba7cbdb2553f6485
Author: Ishita Mandhan 
Date:   2016-08-25T21:38:16Z

KAFKA-3940 Log should check the return value of dir.mkdirs()




---
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 #1748: KAFKA-3940 Log should check the return value of di...

2016-08-25 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1748


---
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 #1748: KAFKA-3940 Log should check the return value of di...

2016-08-23 Thread imandhan
GitHub user imandhan reopened a pull request:

https://github.com/apache/kafka/pull/1748

KAFKA-3940 Log should check the return value of dir.mkdirs()

This commit changes all the occurrences of dir.mkdirs() with 
Files.createDirectory(dir.toPath())

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3940

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1748.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 #1748


commit baf70497759e636a55d50f03d0c5a9673ac71d2d
Author: Ishita Mandhan 
Date:   2016-08-17T00:32:22Z

KAFKA-3940 Log should check the return value of dir.mkdirs()

This commit changes all the occurrences of dir.mkdirs() with 
Files.createDirectory(dir.toPath())

commit c813091659336a7985353a518b4284ca1bd47cf9
Author: Ishita Mandhan 
Date:   2016-08-17T20:30:46Z

Kafka 3940: Log should check the return value of dir.mkdirs()

Fixed the failing errors in the previous commit that changed occurrences of 
dir.mkdirs() to Files.createDirectory()

commit 825c5e9a70b9781a09e033e6a8951a6319c29ae7
Author: Ishita Mandhan 
Date:   2016-08-24T01:59:16Z

KAFKA-3940 Log should check the return value of dir.mkdirs()




---
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 #1748: KAFKA-3940 Log should check the return value of di...

2016-08-23 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1748


---
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 #1748: KAFKA-3940 Log should check the return value of di...

2016-08-16 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1748

KAFKA-3940 Log should check the return value of dir.mkdirs()

This commit changes all the occurrences of dir.mkdirs() with 
Files.createDirectory(dir.toPath())

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3940

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1748.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 #1748


commit baf70497759e636a55d50f03d0c5a9673ac71d2d
Author: Ishita Mandhan 
Date:   2016-08-17T00:32:22Z

KAFKA-3940 Log should check the return value of dir.mkdirs()

This commit changes all the occurrences of dir.mkdirs() with 
Files.createDirectory(dir.toPath())




---
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 #1702: Kafka 3940: Log should check the return value of d...

2016-08-10 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1702


---
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 #1702: Kafka 3940: Log should check the return value of d...

2016-08-03 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1702

Kafka 3940: Log should check the return value of dir.mkdirs()

Changed occurrences of dir.mkdirs() to Files.createDirectory and similarly 
for File.delete to Files.delete

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3940

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1702.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 #1702


commit e0be207db0d9eef2eaa3d0b3638f50b8921bd9a3
Author: Ishita Mandhan 
Date:   2016-07-20T20:53:20Z

KAFKA-3940 Log should check the return value of dir.mkdirs()

Changed all occurrences of dir.mkdirs() with Files.createDirectory

commit 1106f1b3b674c4f759498966749dfa85a8eafc2c
Author: Ishita Mandhan 
Date:   2016-07-20T20:53:20Z

KAFKA-3940 Log should check the return value of dir.mkdirs()

Changed all occurrences of dir.mkdirs() with Files.createDirectory

commit 1015d0004a63fbcc00f2432227ade39ec1b064de
Author: Ishita Mandhan 
Date:   2016-07-22T18:18:44Z

Merge branch 'KAFKA-3940' of https://github.com/imandhan/kafka into 
KAFKA-3940

commit b9b6f34f1e99afdd92db3be354902a8d3901ed9c
Author: Ishita Mandhan 
Date:   2016-07-22T18:18:44Z

Merge branch 'KAFKA-3940' of https://github.com/imandhan/kafka into 
KAFKA-3940

commit dcda3a72c155bc237b5ba1085a41f813594905c9
Author: Ishita Mandhan 
Date:   2016-07-22T21:14:57Z

Merge branch 'KAFKA-3940' of https://github.com/imandhan/kafka into 
KAFKA-3940




---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-07-12 Thread imandhan
GitHub user imandhan reopened a pull request:

https://github.com/apache/kafka/pull/1548

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-2857

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1548.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 #1548


commit c27df5a17a6bbb34a6118bb7b74d6f3e80239612
Author: Ishita Mandhan 
Date:   2016-06-23T23:46:07Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately.

commit 9da78fa08688b691a954da164e6c8d28abc90500
Author: Ishita Mandhan 
Date:   2016-06-24T00:41:12Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately.

commit 8d157546152fc063a2aff92a3fade1b6947b5ffb
Author: Ishita Mandhan 
Date:   2016-06-24T00:51:20Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

commit f50c8dce19018e7f689d318795eb797a7d0d0f2d
Author: Ishita Mandhan 
Date:   2016-06-28T00:53:33Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

commit 7815008eeb4c2dabaf96707652f50425ac4d5923
Author: Ishita Mandhan 
Date:   2016-06-28T20:13:51Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

commit 2f2eca8091ef576e2f9c79859c7404b8d50733d7
Author: Ishita Mandhan 
Date:   2016-07-11T22:53:35Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created




---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-07-12 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1548


---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-07-05 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1548


---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-07-05 Thread imandhan
GitHub user imandhan reopened a pull request:

https://github.com/apache/kafka/pull/1548

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-2857

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1548.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 #1548


commit c27df5a17a6bbb34a6118bb7b74d6f3e80239612
Author: Ishita Mandhan 
Date:   2016-06-23T23:46:07Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately.

commit 9da78fa08688b691a954da164e6c8d28abc90500
Author: Ishita Mandhan 
Date:   2016-06-24T00:41:12Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately.

commit 8d157546152fc063a2aff92a3fade1b6947b5ffb
Author: Ishita Mandhan 
Date:   2016-06-24T00:51:20Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

commit f50c8dce19018e7f689d318795eb797a7d0d0f2d
Author: Ishita Mandhan 
Date:   2016-06-28T00:53:33Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

commit 7815008eeb4c2dabaf96707652f50425ac4d5923
Author: Ishita Mandhan 
Date:   2016-06-28T20:13:51Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created




---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-06-30 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1548


---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-06-30 Thread imandhan
GitHub user imandhan reopened a pull request:

https://github.com/apache/kafka/pull/1548

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-2857

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1548.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 #1548


commit c27df5a17a6bbb34a6118bb7b74d6f3e80239612
Author: Ishita Mandhan 
Date:   2016-06-23T23:46:07Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately.

commit 9da78fa08688b691a954da164e6c8d28abc90500
Author: Ishita Mandhan 
Date:   2016-06-24T00:41:12Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately.

commit 8d157546152fc063a2aff92a3fade1b6947b5ffb
Author: Ishita Mandhan 
Date:   2016-06-24T00:51:20Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

commit f50c8dce19018e7f689d318795eb797a7d0d0f2d
Author: Ishita Mandhan 
Date:   2016-06-28T00:53:33Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

commit 7815008eeb4c2dabaf96707652f50425ac4d5923
Author: Ishita Mandhan 
Date:   2016-06-28T20:13:51Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created




---
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 #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

2016-06-23 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1548

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-2857

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1548.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 #1548


commit c27df5a17a6bbb34a6118bb7b74d6f3e80239612
Author: Ishita Mandhan 
Date:   2016-06-23T23:46:07Z

KAFKA-2857 ConsumerGroupCommand throws 
GroupCoordinatorNotAvailableException when describing a non-existent group 
before the offset topic is created

Added a check to make sure different cases when offset topic hasn't been 
created and consumer group describe command is run, are handled appropriately.




---
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 #1506: KAFKA-3755 Tightening the offset check in ReplicaF...

2016-06-16 Thread imandhan
Github user imandhan closed the pull request at:

https://github.com/apache/kafka/pull/1506


---
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 #1506: KAFKA-3755 Tightening the offset check in ReplicaF...

2016-06-14 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1506

KAFKA-3755 Tightening the offset check in ReplicaFetcherThread

Including an additional check to make sure that the first offset in the 
message set to be appended to the log is >= than the log end offset.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3755

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1506.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 #1506


commit ed674a9b3e4b4ab5531326396ef59950a2930467
Author: Ishita Mandhan 
Date:   2016-06-14T22:28:24Z

KAFKA-3755 Tightening the offset check in ReplicaFetcherThread

Including additional check to make sure that the first offset in the 
message set to be appended to the log is >= than the log end offset.




---
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 #1480: KAFKA-3762 Log.loadSegments() should log the messa...

2016-06-07 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1480

KAFKA-3762 Log.loadSegments() should log the message in exception

Adding an error logging message in Log.loadSegments() in the case when an 
index file corresponding to a log file exists but an exception is thrown.

Signed-off-by: Ishita Mandhan 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3762

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1480.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 #1480


commit 7d4246efabdc482fab126697ff0457dda0f785ba
Author: Ishita Mandhan 
Date:   2016-06-07T21:34:41Z

KAFKA-3762 Log.loadSegments() should log the message in exception

Adding an error logging message in Log.loadSegments() in the case when an 
index file corresponding to a log file exists but an exception is thrown.

Signed-off-by: Ishita Mandhan 




---
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-3158: ConsumerGroupCommand should tell w...

2016-05-25 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1429

KAFKA-3158: ConsumerGroupCommand should tell whether group is actually dead

This patch fix differentiates between when a consumer group is rebalancing 
or dead and reports the appropriate error message.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka KAFKA-3158

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1429.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 #1429


commit a0c64a404ba7a33cff95684f104c69dffa5d45fb
Author: Ishita Mandhan 
Date:   2016-05-25T19:18:01Z

KAFKA-3158

Differentiates between when a consumer group is rebalancing or dead and 
reports the appropriate
error message.




---
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

2016-04-19 Thread imandhan
GitHub user imandhan opened a pull request:

https://github.com/apache/kafka/pull/1240

MINOR: Fix typos in code comments

This patch fixes all occurances of two consecutive 'the's in the code 
comments.

Author: Ishita Mandhan (iman...@us.ibm.com)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/imandhan/kafka typofixes

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1240.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 #1240


commit be9c2415d740af1338c9e4045420fb158a322406
Author: Ishita Mandhan 
Date:   2016-04-19T23:37:28Z

MINOR: Fix typos in code comments

This patch fixes all occurances of two consecutive 'the's in the code 
comments.

Author: Ishita Mandhan (iman...@us.ibm.com)




---
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.
---