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

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

Commit edf0663a7e6f46e4adaf8cefa0245db3d09c12d2 in geode's branch 
refs/heads/develop from Naburun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=edf0663 ]

GEODE-7655:Restore context with distinct state after a recursion step.

        * After a recursion step within Compiled Select's evaluate statement, 
the distinct flag was lost for the outer query.
        * The solution was to reset the distinct state back using a temp 
variable to store the initial distinct flag value.
        * Also, in this diff a else part section was missing converting PDX 
strings to normal strings for comparison of distinct.
        * When we place this else section converting the PDX string to string 
for distinct comparison, we don't need to perform this check in the 'element' 
query function.

Removing the JPMC related configurations


> Prevent ClassCastException while running nested queries
> -------------------------------------------------------
>
>                 Key: GEODE-7655
>                 URL: https://issues.apache.org/jira/browse/GEODE-7655
>             Project: Geode
>          Issue Type: Bug
>          Components: querying
>            Reporter: Nabarun Nag
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> While running a nested query like :
> {noformat}
> select productId, productCodes['GMI'], contractSize from /product where 
> contractSize = null and productCodes['GMI'] in (select distinct 
> b.productCodes['GMI'] from /product b where b.contractSize != null and 
> b.status='ACTIVE') LIMIT 2000
> {noformat}
> Following Indexes need to be created for the Exception to occur
> 1. Primary Key Index on productID
> 2. Functional index on productID
> 3. Functional index on productCodes['GMI']



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to