On Wed, Jul 17, 2013 at 8:15 AM, Samisa Abeysinghe <[email protected]> wrote:
> > > > On Tue, Jul 16, 2013 at 10:02 AM, Sriskandarajah Suhothayan <[email protected] > > wrote: > >> >> >> >> On Tue, Jul 16, 2013 at 5:40 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> >>> >>> >>> On Wed, Jul 10, 2013 at 6:31 PM, Mohanadarshan Vivekanandalingam < >>> [email protected]> wrote: >>> >>>> Hi Cyril, >>>> >>>> We are on the way of creating the documentation for CEP 3.0.0... >>>> >>> >>> If there are no docs on the features shipped with the milestone, who can >>> we consider those to be "done-done"? >>> >> >> CEP 3.0.0 M2 is just an incremental release and it does not have any >> features in done-done state. >> > > This does not sound right. If a single feature is not done, what are we > shipping in the milestone, only bug fixes? > And the CEP Jira dashboard does not shoe any significant fixes either. > https://wso2.org/jira/secure/Dashboard.jspa?selectPageId=10406 > > I am confused. > > Its a valid question. CEP 3.0.0 is a complete rewrite on the carbon server side. On CEP 2.1.0 we had three components broker, broker-manager and cep, but in CEP 3.0.0 we changed the fundamental architecture according the architecture mail thread "CEP 3.0 towards a Complete eventing solution to the platform" and because of that now we have five components input transport adaptor, output transport adaptor, event builder, event formatter and event processor. Since we were writing all features in parallel and since this is a complete rewrite, we had trouble delivering working milestones having features at done-done level. On CEP 3.0.0 M2 we were able to make all the core features work together, therefore no the next release "CEP 3.0.0 alpha" we will be able to deliver all the features in done-done level. Thanks Suho Both documentation and integration tests are still pending. >> Currently it has almost all the features with their core functionality >> implemented and a simple ReadMe on how to run the samples using its >> available functionality. >> >> In future releases we will be focusing more on brining these features to >> the done-done state. >> >> Thanks >> Suho >> >> >>> >>> >>>> We'll share the documentation with the CEP 3.0.0 release soon... >>>> >>>> Yes, 'non occurrence' of events is already implemented and can be >>>> achieved using the event tables in CEP 3.0.0.. >>>> >>>> We'll update when CEP 3.0.0 released... Thanks for your interest on >>>> CEP... >>>> >>>> Regards, >>>> Mohan >>>> >>>> >>>> >>>> >>>> >>>> On Wed, Jul 10, 2013 at 1:47 PM, Cyril Rognon <[email protected]>wrote: >>>> >>>>> Hello cep team, >>>>> >>>>> thank you for this new milestone. I am wondering if there is any >>>>> documentation link for the upcoming 3.0.0 version. >>>>> >>>>> As far as I know, there is still no logical 'not' operator that we >>>>> could use to filter the 'non occurrence' of events >>>>> >>>>> in siddhi language there is >>>>> >>>>> *<stream> **::= <stream-name> <condition-list>* >>>>> >>>>> it would be nice to be able to say* >>>>> * >>>>> >>>>> *<stream> **::= not <stream-name> <condition-list>* >>>>> I reckon I have not looked into the code to evaluate the cost of this >>>>> requirement, so feel free to turn it down if it is prohibitive. >>>>> >>>>> Maybe eventTables will allow one to simulate this ? >>>>> >>>>> thanks, >>>>> Cyril >>>>> >>>>> >>>>> On Fri, Jul 5, 2013 at 10:47 PM, Mohanadarshan Vivekanandalingam < >>>>> [email protected]> wrote: >>>>> >>>>>> *WSO2 Complex Event Processor 3.0.0 Milestone 2 Released!* >>>>>> >>>>>> Date :5th July 2013 >>>>>> >>>>>> This milestone is available at : >>>>>> https://svn.wso2.org/repos/wso2/people/suho/packs/cep/3.0.0/wso2cep-3.0.0-M2.zip >>>>>> >>>>>> To run the samples please follow the read-me, >>>>>> wso2cep-3.0.0/samples/cep-samples/ReadMe.txt >>>>>> >>>>>> >>>>>> Following are the bug fixes, improvements and the new features >>>>>> >>>>>> Bug >>>>>> >>>>>> - [CEP-258 <https://wso2.org/jira/browse/CEP-258>] - When trying >>>>>> to deploy the multiple configuration files, File reference is missing >>>>>> - [CEP-261 <https://wso2.org/jira/browse/CEP-261>] - Table is not >>>>>> properly generated when creating WSO2 Event mapping and Map mapping >>>>>> >>>>>> Improvement >>>>>> >>>>>> - [CEP-179 <https://wso2.org/jira/browse/CEP-179>] - It is better >>>>>> if the UI supports to check the validity of "Event Sink URL" when >>>>>> subscribing to a topic >>>>>> - [CEP-243 <https://wso2.org/jira/browse/CEP-243>] - Separate >>>>>> implementation classes & UI for handing in/out sequences of transport >>>>>> adapators >>>>>> - [CEP-247 <https://wso2.org/jira/browse/CEP-247>] - Making >>>>>> Coalesce as a ExecutorFunction >>>>>> - [CEP-248 <https://wso2.org/jira/browse/CEP-248>] - Removing >>>>>> conversion types from output attribute processor >>>>>> - [CEP-249 <https://wso2.org/jira/browse/CEP-249>] - Replacing >>>>>> Condition Extentions using bool returning Expression Extentions >>>>>> - [CEP-251 <https://wso2.org/jira/browse/CEP-251>] - White-board >>>>>> pattern for Transport Adaptors and Event sources >>>>>> - [CEP-257 <https://wso2.org/jira/browse/CEP-257>] - Event Tracer >>>>>> output in UI need to be formatted >>>>>> - [CEP-260 <https://wso2.org/jira/browse/CEP-260>] - UI to >>>>>> retrieve the deployed Event Formatter configuration details >>>>>> - [CEP-262 <https://wso2.org/jira/browse/CEP-262>] - >>>>>> EventFormatter to receive WSO2Event and format it to other different >>>>>> types.. For products like BAM >>>>>> - [CEP-267 <https://wso2.org/jira/browse/CEP-267>] - >>>>>> Listing/editing undeployed event builders >>>>>> - [CEP-268 <https://wso2.org/jira/browse/CEP-268>] - Handing >>>>>> dependency between the components when removing the configuration >>>>>> files >>>>>> >>>>>> New Feature >>>>>> >>>>>> - [CEP-156 <https://wso2.org/jira/browse/CEP-156>] - Add a >>>>>> default timeStamp convertor >>>>>> - [CEP-162 <https://wso2.org/jira/browse/CEP-162>] - Add >>>>>> Attribute Type Convetors to Siddhi >>>>>> - [CEP-215 <https://wso2.org/jira/browse/CEP-215>] - Adding >>>>>> snapshot output support for Siddhi window >>>>>> - [CEP-231 <https://wso2.org/jira/browse/CEP-231>] - New >>>>>> component called "EventFormatter" to handle the events when sending >>>>>> out >>>>>> from the CEP >>>>>> - [CEP-250 <https://wso2.org/jira/browse/CEP-250>] - >>>>>> IsMatchExecutorFunction to regex matching >>>>>> - [CEP-252 <https://wso2.org/jira/browse/CEP-252>] - Wiring >>>>>> between the components when adding the configuration files >>>>>> - [CEP-253 <https://wso2.org/jira/browse/CEP-253>] - >>>>>> ConvertExecutorFunction for type conversion >>>>>> - [CEP-264 <https://wso2.org/jira/browse/CEP-264>] - Added the >>>>>> ability for Siddhi to retrieve properties from registry >>>>>> - [CEP-265 <https://wso2.org/jira/browse/CEP-265>] - Added the >>>>>> ability for Siddhi to retrieve resources from registry >>>>>> - [CEP-266 <https://wso2.org/jira/browse/CEP-266>] - >>>>>> Adding/editing event builders through UI >>>>>> >>>>>> Task >>>>>> >>>>>> - [CEP-246 <https://wso2.org/jira/browse/CEP-246>] - Merging >>>>>> Transport adaptors and manager compoenents >>>>>> - [CEP-263 <https://wso2.org/jira/browse/CEP-263>] - Added new >>>>>> icon images >>>>>> >>>>>> >>>>>> >>>>>> We welcome your feedback and would love to hear your thoughts on this >>>>>> release of CEP. >>>>>> >>>>>> CEP team >>>>>> >>>>>> -- >>>>>> *V. Mohanadarshan* >>>>>> *Software Engineer,* >>>>>> *Data Technologies Team,* >>>>>> *WSO2, Inc. http://wso2.com * >>>>>> *lean.enterprise.middleware.* >>>>>> * >>>>>> * >>>>>> email: [email protected] >>>>>> phone:(+94) 771117673 >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> *V. Mohanadarshan* >>>> *Software Engineer,* >>>> *Data Technologies Team,* >>>> *WSO2, Inc. http://wso2.com * >>>> *lean.enterprise.middleware.* >>>> * >>>> * >>>> email: [email protected] >>>> phone:(+94) 771117673 >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *S. Suhothayan >> * >> Associate Technical Lead, >> *WSO2 Inc. *http://wso2.com * >> <http://wso2.com/>* >> lean . enterprise . middleware >> >> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >> twitter: http://twitter.com/suhothayan | linked-in: >> http://lk.linkedin.com/in/suhothayan* >> * >> * >> > > > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > -- *S. Suhothayan * Associate Technical Lead, *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan* * *
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
