[
https://issues.apache.org/jira/browse/APEXMALHAR-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311571#comment-15311571
]
Ilya Ganelin commented on APEXMALHAR-2099:
------------------------------------------
[~siyuan][~thw] Thanks for the comments. I've been following along all the
linked work - Thomas, I've also looked into your Runner in detail. Based on the
discussion here, the work in
https://github.com/apache/incubator-beam/compare/master...tweise:master and in
https://issues.apache.org/jira/browse/APEXMALHAR-2085. This is a fantastic
start! Siyuan - it sounds like there's a clear agreement that we want to break
down the transformations into windowed and un-windowed transforms, I think the
next logical step is to build the Windowed Operator. This would allow us to
implement a number of the transforms already present in the Runner as windowed
transformations and subsequently implement trigger semantics. I'm obviously not
down on the ground with you guys, so I don't know in detail who is working on
what. If possible, I would propose that we work together to formulate a set of
concrete JIRAs that lay out the next steps so that we are not replicating
effort. It might even make sense to do this in person. Then, we can split up
the labor and move forward in tackling specific problems.
> Identify overlap between Beam API and existing Apex Stream API
> --------------------------------------------------------------
>
> Key: APEXMALHAR-2099
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2099
> Project: Apache Apex Malhar
> Issue Type: Sub-task
> Reporter: Ilya Ganelin
>
> There should be some overlap between the Beam API and the recently released
> Apex Stream API. This task captures the need to understand and document this
> overlap.
> AC:
> * A document or JIRA comment identifying which components of the Beam API are
> implement, similar, or absent within the Apex Stream API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
