[ 
https://issues.apache.org/jira/browse/KAFKA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034929#comment-15034929
 ] 

ASF GitHub Bot commented on KAFKA-1851:
---------------------------------------

GitHub user apovzner opened a pull request:

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

    KAFKA-1851 Using random dir under /temp for local kdc files to avoid 
conflicts.

    when multiple test jobs are running.
    
    I manually separated changes for KAFKA-2851 from this PR:  
https://github.com/apache/kafka/pull/570 which also had KAFKA-2825 changes.

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

    $ git pull https://github.com/apovzner/kafka kafka-2851

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

    https://github.com/apache/kafka/pull/609.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 #609
    
----
commit d19a8533243a77f026a4f547bad40fd10dd68745
Author: Anna Povzner <a...@confluent.io>
Date:   2015-12-02T00:02:13Z

    KAFKA-1851 Using random dir under /temp for local kdc files to avoid 
conflicts when multiple test jobs are running.

----


> OffsetFetchRequest returns extra partitions when input only contains unknown 
> partitions
> ---------------------------------------------------------------------------------------
>
>                 Key: KAFKA-1851
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1851
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.2.0
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>            Priority: Blocker
>             Fix For: 0.8.2.0
>
>         Attachments: kafka-1851.patch
>
>
> When issuing an OffsetFetchRequest with an unknown topic partition, the 
> OffsetFetchResponse unexpectedly returns all partitions in the same consumer 
> group, in addition to the unknown partition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to