On Mon, Apr 2, 2018 at 9:55 PM, Ahmet Altay <al...@google.com> wrote:
> >> I’m specifically interested in stateful processing and timers as basic >> building blocks that could be used with a global window to implement >> session functionality and other higher level abstractions without being >> constrained by window functions and predefined triggers. >> > > These are missing. Charles started working on those [1]. We can use any > help we can get if you are interested. > Are there any existing discussions or docs for BEAM-2687 <https://issues.apache.org/jira/browse/BEAM-2687>? > >> >> Also since we have the runner capability matrix >> <https://beam.apache.org/documentation/runners/capability-matrix/>, >> would it be useful to track SDK capabilities in a similar way so that >> users know what’s supported? >> > > I think this would be really helpful. Especially now that we have multiple > SDKs in master. Recently Rafael proposed having per-transform documentation > [2]. Building an SDK capability matrix would be natural extension of it. > To have some basic orientation, it might be good add the Python SDK to the existing matrix? First column currently is "Beam Model", should that become Java SDK instead? > > [1] https://issues.apache.org/jira/browse/BEAM-2687 > [2] https://lists.apache.org/thread.html/626427f65a97eb5b40ecb4963202e7 > bdb43fccf139d82add698a7113@%3Cdev.beam.apache.org%3E > > > >> >> Thanks, >> Thomas >> >> >
