Hi kishanthan, In BAM 2.4.0, you can define the stream definition with any publisher/agent, and then you can add the incremental processing later on for the existing stream. But in BAM 2.4.1, it has been broken and i experienced exception as mentioned in [1], this will be resolved during the restart of the BAM Receiver node.
We'll fix this in the next release. [1] https://wso2.org/jira/browse/BAM-1643 Thanks, Sinthuja. On Sat, May 31, 2014 at 4:38 PM, Kishanthan Thangarajah <[email protected] > wrote: > Hi, > > When using BAM mediator, there is little control over how the streams gets > defined. This will make some inconsistent behavior when we try to use some > features at BAM side. For example, how to use the incremental analysis > feature[1] for streams which are created when using BAM mediator? > > The doc mentions about how this feature can be enabled using toolbox > approach when defining streams. But with BAM mediator, the streams are > automatically created. As a workaround, what we can do is pre-define the > stream with toolbox and then start using BAM mediator. But this also leads > to a situation where you will have to know the exact definition of the > stream beforehand. > > Do we have a proper workaround for this or can we take this as an > improvement? > > Thanks, > Kishanthan. > [1] https://docs.wso2.org/display/BAM241/Incremental+Analysis > > -- > *Kishanthan Thangarajah* > Senior Software Engineer, > Platform Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* > Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* > -- *Sinthuja Rajendran* Senior Software Engineer <http://wso2.com/> WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
