Re: [Dev] [CEP-1415] Siddhi Event Table - Insert if not requirement

[Sriskandarajah Suhothayan]

+1 need to create "update or insert" for this usecase.
We'll work on this this for the next release.

Suho

On Wed, Oct 21, 2015 at 10:37 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Wed, Oct 21, 2015 at 2:55 PM, Tishan Dahanayakage 
> wrote:
>
>> Hi,
>>
>> As explained in this JIRA[1] a query where we check whether certain item
>> exists and then insert(more like initializing table) fails if query
>> receives burst events. Reason is multiple events will evaluate condition
>> 'not((itemNo==avgQty.itemNo) in avgQty)' to be true before the first insert
>> is committed.
>> For this exact scenario Seshika pointed out that we can get rid of this
>> by making that field the primary key. But for some scenarios that can also
>> generate false results because there can be situations where this
>> initialization insert may overwrite a calculated result put into table by
>> another query.
>> In summary we should state that we do not support atomic execution of a
>> query hence users will not be misled.
>>
>> Also since this type of requirement is practical and will be useful, I
>> think we should consider adding this functionality for next minor release
>> after comparing between implementation cost and added value.
>>
>> WDYT?
>>
>
> +1, we thought of adding this improvement even in CEP 4.0.0 but our
> priorities are got changed :) ..  Let's add this for next immediate
> release..
>
>
>> [1] https://wso2.org/jira/browse/CEP-1415
>>
>> Thanks
>> Tishan
>>
>> --
>> Tishan Dahanayakage
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 716481328
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 

*S. Suhothayan*
Technical Lead & Team Lead of WSO2 Complex Event Processor
*WSO2 Inc. *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 *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [CEP-1415] Siddhi Event Table - Insert if not requirement

[Mohanadarshan Vivekanandalingam]

On Wed, Oct 21, 2015 at 2:55 PM, Tishan Dahanayakage 
wrote:

> Hi,
>
> As explained in this JIRA[1] a query where we check whether certain item
> exists and then insert(more like initializing table) fails if query
> receives burst events. Reason is multiple events will evaluate condition
> 'not((itemNo==avgQty.itemNo) in avgQty)' to be true before the first insert
> is committed.
> For this exact scenario Seshika pointed out that we can get rid of this by
> making that field the primary key. But for some scenarios that can also
> generate false results because there can be situations where this
> initialization insert may overwrite a calculated result put into table by
> another query.
> In summary we should state that we do not support atomic execution of a
> query hence users will not be misled.
>
> Also since this type of requirement is practical and will be useful, I
> think we should consider adding this functionality for next minor release
> after comparing between implementation cost and added value.
>
> WDYT?
>

+1, we thought of adding this improvement even in CEP 4.0.0 but our
priorities are got changed :) ..  Let's add this for next immediate
release..


> [1] https://wso2.org/jira/browse/CEP-1415
>
> Thanks
> Tishan
>
> --
> Tishan Dahanayakage
> Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>



-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev