You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2016/03/25 00:25:25 UTC
[jira] [Commented] (QUARKS-80) The TWindow.aggregate name could be
imporoved
[ https://issues.apache.org/jira/browse/QUARKS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211127#comment-15211127 ]
Daniel John Debrunner commented on QUARKS-80:
---------------------------------------------
I like the simplicity of the name, it aggregates the window, the stream produced always represents the aggregation of the window (partition).
Quarks is a per-tuple streaming paradigm, so the continuous nature is somewhat implied, we don't have 'filterOnTuple'.
> The TWindow.aggregate name could be imporoved
> ---------------------------------------------
>
> Key: QUARKS-80
> URL: https://issues.apache.org/jira/browse/QUARKS-80
> Project: Quarks
> Issue Type: Improvement
> Reporter: Will Marshall
> Assignee: Will Marshall
> Priority: Minor
>
> For example, TWindow.batch clearly provides batch functionality for tuples in the partition -- tuples are processed in bulk, and then evicted.
> The contract for TWindow.aggregate is less clear given the name. The way it currently works, the partition is aggregated any time its contents change (a tuple is inserted or evicted).
> Perhaps something like TWindow.aggregateOnChange would be better?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)