You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geode.apache.org by "Jason Huynh (JIRA)" <ji...@apache.org> on 2016/12/20 00:01:58 UTC

[jira] [Resolved] (GEODE-2183) Region.query behaves differently on client and server when full syntax is passed as a predicate

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

Jason Huynh resolved GEODE-2183.
--------------------------------
    Resolution: Fixed

> Region.query behaves differently on client and server when full syntax is passed as a predicate
> -----------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2183
>                 URL: https://issues.apache.org/jira/browse/GEODE-2183
>             Project: Geode
>          Issue Type: Bug
>          Components: querying
>            Reporter: Jason Huynh
>            Assignee: Jason Huynh
>             Fix For: 1.1.0
>
>
> When the full query syntax is passed into region.query(String predicate), the client will allow such executions but when the query is executed on a server, it will throw a compile exception.  
> This should be made consistent, even though full query "select * from /region" technically shouldn't be allowed, due to possible legacy users, we will probably need to keep allowing this to happen for now...?



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