[GitHub] kafka pull request #1826: KAFKA-4129: Processor throw exception when getting...

2016-09-06 Thread xiaotao183
GitHub user xiaotao183 opened a pull request:

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

KAFKA-4129: Processor throw exception when getting channel remote address 
after closing the channel

Get channel remote address before calling ```channel.close```

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

$ git pull https://github.com/xiaotao183/kafka KAFKA-4129

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

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


commit 3d4a4b01789c46ac940caba6be35f73c3db715fa
Author: Tao Xiao <xiaotao...@gmail.com>
Date:   2016-09-06T13:12:35Z

get channel remote address before calling channel.close




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #1466: KAFKA-3787: Preserve the message timestamp in mirr...

2016-06-03 Thread xiaotao183
GitHub user xiaotao183 opened a pull request:

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

KAFKA-3787: Preserve the message timestamp in mirror maker

The timestamp of messages consumed by mirror maker is not preserved after 
sending to target cluster. The correct behavior is to keep create timestamp the 
same in both source and target clusters.

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

$ git pull https://github.com/xiaotao183/kafka KAFKA-3787

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

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


commit 29b874b01bfdd1d7114e5eb431307b5031a80754
Author: Tao Xiao <xiaotao...@gmail.com>
Date:   2016-06-03T09:08:37Z

KAFKA-3787: Preserve the message timestamp in mirror maker




---
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-3157 - Mirror maker doesn't commit offse...

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

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


---
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-3157 - Mirror maker doesn't commit offse...

2016-02-02 Thread xiaotao183
GitHub user xiaotao183 reopened a pull request:

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

KAFKA-3157 - Mirror maker doesn't commit offset

Mirror maker doesn't commit offset with new consumer enabled when data 
volume is low. This is caused by infinite loop in ```receive()``` which would 
never jump out of loop if no data coming

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

$ git pull https://github.com/xiaotao183/kafka KAFKA-3157

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

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


commit c3221c0d0391080889ab899f8570b629561a8529
Author: Tao Xiao <xiaotao...@gmail.com>
Date:   2016-01-28T07:42:27Z

KAFKA-3157 - Mirror maker doesn't commit offset with new consumer enabled 
if data volume is low

commit f674012525cc17b6d68e18ccf8819f9e84936ef9
Author: Tao Xiao <xiaotao...@gmail.com>
Date:   2016-02-02T10:58:09Z

Reuse NewShinyConsumer receive to make receive behavior in mirror maker 
consistent across the board

commit 18fe1a60ddcc2b75d357f664bdedb5cebfb5bb3a
Author: Tao Xiao <xiaotao...@gmail.com>
Date:   2016-02-02T11:12:58Z

add parentheses to next

commit 3f193b04ab9fa6f2abaf80b07c259cbf8fb5dba2
Author: Tao Xiao <xiaotao...@gmail.com>
Date:   2016-02-02T11:14:31Z

avoid whitespace in empty line




---
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-3157 - Mirror maker doesn't commit offse...

2016-01-27 Thread xiaotao183
GitHub user xiaotao183 opened a pull request:

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

KAFKA-3157 - Mirror maker doesn't commit offset

Mirror maker doesn't commit offset with new consumer enabled when data 
volume is low. This is caused by infinite loop in ```receive()``` which would 
never jump out of loop if no data coming

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

$ git pull https://github.com/xiaotao183/kafka KAFKA-3157

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

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


commit c3221c0d0391080889ab899f8570b629561a8529
Author: Tao Xiao <xiaotao...@gmail.com>
Date:   2016-01-28T07:42:27Z

KAFKA-3157 - Mirror maker doesn't commit offset with new consumer enabled 
if data volume is low




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