In my case it was translation of Apache Samoa topology into Apex DAG. An "add node" in Samoa can be translated to an "add operator" in Apex. However, these topologies do not define how many streams / ports will be produced by the operator upfront. It is only until we encounter a "add stream" which gives the hint that another port is needed to produce that stream.
-Bhupesh On Thu, Dec 24, 2015 at 12:33 PM, Thomas Weise <[email protected]> wrote: > Can you provide examples of such use cases? > > On Wed, Dec 23, 2015 at 10:58 PM, Chinmay Kolhatkar < > [email protected] > > wrote: > > > Hi, > > > > This is coming from > > https://github.com/apache/incubator-apex-malhar/pull/142 > > > > The code changes uses ports wrapped in the collections. > > Currently Apex does not support collection of ports. > > > > But, I think this is a good idea to support for the use cases where the > > number of ports are not know upfront. > > > > Thoughts? > > > > ~ Chinmay. > > >
