Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
From: dguy <git@git.apache.org>
To: dev@kafka.apache.org
Reply-To: dev@kafka.apache.org
Message-ID: <git-pr-1453-kafka@git.apache.org>
Subject: [GitHub] kafka pull request: KAFKA-3561: Auto create through topic for KStream aggreg...
Content-Type: text/plain
Date: Wed,  1 Jun 2016 13:25:29 +0000 (UTC)
archived-at: Wed, 01 Jun 2016 13:25:32 -0000

GitHub user dguy opened a pull request:

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

    KAFKA-3561: Auto create through topic for KStream aggregation and join [WIP]

    @guozhangwang can you please take a look at this? It is not close to being done but i'd like some feedback to ensure i'm heading down the right path and understand what this JIRA is asking. The main things to look at are the `KStreamImpl.map(...)` method I added and the change made to `TopologyBuilder.copartitionGroups`
    
    There is also a test, `KStreamRepartitionMappedKeyTest`, that passes with these changes.


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

    $ git pull https://github.com/dguy/kafka KAFKA-3561

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

    https://github.com/apache/kafka/pull/1453.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 #1453
    
----
commit 053c809b5aa322327988909d53027d4682df6825
Author: Damian Guy <damian.guy@gmail.com>
Date:   2016-06-01T13:03:23Z

    repartition through internal topic on KStream.map()

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---