ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sathwik Bantwal Premakumar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ODE-1049) Query optimization to findRoute and dequeueMessage queries - MATCHER job
Date Fri, 08 Jul 2016 07:16:10 GMT

     [ https://issues.apache.org/jira/browse/ODE-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sathwik Bantwal Premakumar resolved ODE-1049.
---------------------------------------------
    Resolution: Fixed

> Query optimization to findRoute and dequeueMessage queries - MATCHER job
> ------------------------------------------------------------------------
>
>                 Key: ODE-1049
>                 URL: https://issues.apache.org/jira/browse/ODE-1049
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>            Reporter: Sathwik Bantwal Premakumar
>            Assignee: Sathwik Bantwal Premakumar
>             Fix For: 1.3.7
>
>
> During the execution of MATCHER job the CorrelationKeySet used will only contain pre
initialised correlation keys. 
> https://github.com/apache/ode/blob/ode-1.3.x/bpel-runtime/src/main/java/org/apache/ode/bpel/runtime/PICK.java#L87
> https://github.com/apache/ode/blob/ode-1.3.x/bpel-runtime/src/main/java/org/apache/ode/bpel/runtime/EH_EVENT.java#L120
> Hence we can directly use the CorrelationKeySet's canonical value instead of its subsets
for both findRoute and dequeueMessage method calls within matcherEvent.
> This avoids the use of SQL IN clause in the findRoute and dequeueMessage queries and
improves the execution time of these queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message