Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
MIME-Version: 1.0
References: <CAG_7j8xgROKfg4J_R4UVQjCeka+1HBwnQjoWksWfnjxoSM6xpQ@mail.gmail.com>
In-Reply-To: <CAG_7j8xgROKfg4J_R4UVQjCeka+1HBwnQjoWksWfnjxoSM6xpQ@mail.gmail.com>
From: Sandesh Hegde <sandesh@datatorrent.com>
Date: Tue, 19 Jul 2016 04:17:12 +0000
Message-ID: <CAJhKGzqChaNwsGKL9edsovRZZNX+rXBD=kXR41KENVf6z2dxsg@mail.gmail.com>
Subject: Re: Dynamic partition is not working in Kafka Input Operator
To: dev@apex.apache.org
Content-Type: multipart/alternative; boundary=001a113503f878e2ed0537f55c92
archived-at: Tue, 19 Jul 2016 04:17:33 -0000

--001a113503f878e2ed0537f55c92
Content-Type: text/plain; charset=UTF-8

Was this resolved?

My understanding is that, Kafka Input operator doesn't support the changes
in Kafka partitions after the initial launch.

On Mon, Jul 18, 2016 at 1:54 AM Chaitanya Chebolu <chaitanya@datatorrent.com>
wrote:

> Hi All,
>
>    I am facing dynamic partition issues in 0.8 version of Kafka Input
> Operator. My application has the following DAG:
>
>    KafkaSinglePortStringInputOperator(Input) ->
> ConsoleOutputOperator(Output)
>
>    I launched the application with below configuration:
> Kafka topic created with single partition and replication factor as 1.
> Partition Strategy: ONE_TO_ONE
>
>    Launched the application successfully. After some time, I increased the
> topic partitions to 2. After re-partition, the window of down stream
> operator is not moving. By looking into the app Physical DAG, it looks like
> there is an issue in construction of Physical DAG after re-partition.
>
> Please let me know if any one observed the same behavior. Do we have JIRA
> for tracking this issue.
> I am attaching some of the screenshots of this application.
>
> Regards,
> Chaitanya
>
>

--001a113503f878e2ed0537f55c92--