You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dharam Thacker (JIRA)" <ji...@apache.org> on 2017/12/01 10:24:00 UTC
[jira] [Updated] (GEODE-4041) Add support for 'Union All' flow in
Oql
[ https://issues.apache.org/jira/browse/GEODE-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dharam Thacker updated GEODE-4041:
----------------------------------
Description:
There are lot of applications in Financial services world driven by 'Lookup based rules'/'Decision Table' approach.
*+Example:+*
Give me all rules where counterParty matches to "XYZ" and Products matches "INDEX|TRANCHE" and clearingJurisdictions matches "ICE|ESMA"
UNION ALL
Give me all rules where counterParty matches to "XYZ" and Products matches "ALL" and clearingJurisdictions matches "ALL" and targetParty is not same as "$TradeFacts.Entity"
Purpose of above query is to get either exact rule/default rule which is a super set of given trade facts.
As of now, one has to write function logic to deal with such situations to avoid round trip between client/server due to invocation of multiple queries
was:
There are lot of applications in Financial services world driven by 'Lookup based rules'/'Decision Table' approach.
*+Example:+*
Give me all rules where counterParty matches to "XYZ" and Products matches "INDEX|TRANCHE" and clearingJurisdictions matches "ICE|ESMA"
UNION ALL
Give me all rules where counterParty matches to "XYZ" and Products matches "ALL" and clearingJurisdictions matches "ALL"
Purpose of above query is to get either exact rule/default rule which is a super set of given trade facts.
As of now, one has to write function logic to deal with such situations to avoid round trip between client/server due to invocation of multiple queries
> Add support for 'Union All' flow in Oql
> ---------------------------------------
>
> Key: GEODE-4041
> URL: https://issues.apache.org/jira/browse/GEODE-4041
> Project: Geode
> Issue Type: New Feature
> Components: querying
> Reporter: Dharam Thacker
>
> There are lot of applications in Financial services world driven by 'Lookup based rules'/'Decision Table' approach.
> *+Example:+*
> Give me all rules where counterParty matches to "XYZ" and Products matches "INDEX|TRANCHE" and clearingJurisdictions matches "ICE|ESMA"
> UNION ALL
> Give me all rules where counterParty matches to "XYZ" and Products matches "ALL" and clearingJurisdictions matches "ALL" and targetParty is not same as "$TradeFacts.Entity"
> Purpose of above query is to get either exact rule/default rule which is a super set of given trade facts.
> As of now, one has to write function logic to deal with such situations to avoid round trip between client/server due to invocation of multiple queries
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)