[
https://issues.apache.org/jira/browse/APEXMALHAR-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312609#comment-15312609
]
Siyuan Hua commented on APEXMALHAR-2099:
----------------------------------------
[~ilganeli] Thanks for bring this up, I should have communicated more on my
side :) Well, Here is the progress right now, [~davidyan] is going to start
working on WindowedOperator today, [~thw] already has done some work in Beam
translation, and I still focus on high-level API (working on the trigger
expression now, precisely speaking :) ). I wouldn't say the design above is
the final agreement, when we work on it, we might change something. It's a big
feature and the completeness of Data Flow Model is very good. The ultimate goal
is to have a Windowed Operator family that can be shared in both High-Level API
and Beam translation.
[~thw] I agree that maybe DSL is better than Java in this case and flexibility
should be there in basic APIs
> 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)
