Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CADS+zCtNY+i=+Mrg7C1ufpjzRBU2A9vip+6VY8rmNdkQ85QE4g@mail.gmail.com>
References: 
 <CADS+zCtNY+i=+Mrg7C1ufpjzRBU2A9vip+6VY8rmNdkQ85QE4g@mail.gmail.com>
Date: Mon, 14 Dec 2015 09:46:41 -0800
Message-ID: 
 <CAMqituOkjgMu8Mq-90vU+XCoi9AjcT-kLeNeo1=bOmQ=1FcE=w@mail.gmail.com>
Subject: Re: Operator Utility To Convert Time Into Number Of Windows
From: David Yan <david@datatorrent.com>
To: dev@apex.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113fc1107565130526df41c2

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

Similar utilities are already in WindowGenerator in apex core.  Maybe add
to that class instead of creating a separate class?

David
On Dec 11, 2015 4:13 PM, "Timothy Farkas" <tim@datatorrent.com> wrote:

> I'd like to propose creating an operator utility in
> com.datatorrent.lib.operatorutils to convert time into number of windows
> and tuples / second into tuples / window. The way in which this currently
> can be specified is through a property like operationWindowCount or
> tuplesPerWindow. This works but I've observed that this can lead to
> confusion. The confusion comes from the fact that the people who develop
> apps are not necessarily the ones who test deployment configurations and
> manage the apps, so they think in time not application windows. Also the
> default application window count and streaming window size is not common
> knowledge, so it's not easy to compute the conversion from windows to time.
> This small utility method could be reused across operators.
>
> Any feedback?
>
> Thanks,
> Tim
>

--001a113fc1107565130526df41c2--