[
https://issues.apache.org/jira/browse/APEXMALHAR-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311017#comment-15311017
]
Ilya Ganelin commented on APEXMALHAR-2099:
------------------------------------------
The biggest lack we presently have seems to be GroupByKey. Implementing
GroupByKey will need either a new operator (that emits a map of {Key ->
List[Value]} on window boundaries) or a pairing with the ApexStream
implementation (that an incoming stream is split up into multiple new streams)
(Preferred).
Implementing the flatten operator should be straightforward.
In terms of windowing and triggering, I think Siyuan's present API which
provides the "with" construct, should be more than sufficient for specifying
windowing or trigger semantics that can then be translated by the ApexStream
implementation.
[~thw][~siyuan] Thoughts? Which route would you recommend?
> 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)
