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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749249#comment-15749249 ] 

ASF subversion and git services commented on GEODE-2183:
--------------------------------------------------------

Commit d65c1fe26289d6d0d34acfc83c9a0c92f6c0fb3a in geode's branch refs/heads/develop from [~huynhja]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d65c1fe ]

GEODE-2183: Region.query now allows full syntax as a predicate on server


> 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)