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

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

Commit 6e35c201ea605075433203d4e64ca887bafd8fcb in geode's branch 
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6e35c20 ]

GEODE-7728: Fix Assertion Failures in OQL (#4639)

- Added unit and integration tests.
- Back off from the single index optimisation during join queries if
  we can't find the (single) best filter, allowing the regular
  execution to continue and use multiple indexes.
- If there are multiple indexes, add the filter evaluable operand at
  the beginning of the internal list to evaluate it first in the chain.

> org.apache.geode.InternalGemFireError: ERROR: Assertion failed
> --------------------------------------------------------------
>
>                 Key: GEODE-7728
>                 URL: https://issues.apache.org/jira/browse/GEODE-7728
>             Project: Geode
>          Issue Type: Bug
>          Components: querying
>            Reporter: Juan Ramos
>            Assignee: Juan Ramos
>            Priority: Major
>              Labels: GeodeCommons
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When trying to run a simple equi-join query (both fields are indexed) with 
> additional filters on a single region, the execution fails with the following 
> exception:
> {noformat}
> org.apache.geode.InternalGemFireError: ERROR: Assertion failed: '  '
>       at 
> org.apache.geode.cache.query.internal.Support.assertionFailed(Support.java:76)
>       at org.apache.geode.cache.query.internal.Support.Assert(Support.java:65)
>       at org.apache.geode.cache.query.internal.Support.Assert(Support.java:46)
>       at 
> org.apache.geode.cache.query.internal.AbstractGroupOrRangeJunction.filterEvaluate(AbstractGroupOrRangeJunction.java:150)
>       at 
> org.apache.geode.cache.query.internal.CompiledJunction.filterEvaluate(CompiledJunction.java:190)
>       at 
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:538)
>       at 
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:53)
>       at 
> org.apache.geode.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:432)
>       at 
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:267)
>       at 
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:199)
> {noformat}
> The problem seems to be that, in order to optimise the execution for a more 
> general form of join queries, we fail to find the "optimal" filter on which 
> to operate and, thus, the exception is thrown.
> The problem is not reproducible whenever one of the fields used for the 
> comparison is not indexed, or when both indexes are passed to the query 
> engine using the *HINT* keyword.



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

Reply via email to