You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Eric Newton (Created) (JIRA)" <ji...@apache.org> on 2012/03/06 18:36:58 UTC
[jira] [Created] (ACCUMULO-447) BooleanLogicIterator cannot handle
ORs correctly
BooleanLogicIterator cannot handle ORs correctly
------------------------------------------------
Key: ACCUMULO-447
URL: https://issues.apache.org/jira/browse/ACCUMULO-447
Project: Accumulo
Issue Type: Bug
Components: wikisearch
Reporter: Eric Newton
Assignee: Eric Newton
Fix For: 1.4.0
When an OR clause in a query tree has negations in that subtree and does not have a document which matches the query, the BooleanLogicIterator cannot ascertain whether that subtree has more results to search or whether the subtree is exhausted.
eg. if we search for
{noformat}
(field1 == 'a' && field2 != 'a') || (field2 == 'a' && field1 != 'a')
{noformat}
and say DOC1 has both field1 and field2 equal to 'a', BooleanLogicIterator cannot determine whether it needs to call next() to find more reults ore whether to set its own topKey to null and quit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ACCUMULO-447) BooleanLogicIterator cannot handle
ORs correctly
Posted by "Eric Newton (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton resolved ACCUMULO-447.
----------------------------------
Resolution: Fixed
> BooleanLogicIterator cannot handle ORs correctly
> ------------------------------------------------
>
> Key: ACCUMULO-447
> URL: https://issues.apache.org/jira/browse/ACCUMULO-447
> Project: Accumulo
> Issue Type: Bug
> Components: wikisearch
> Reporter: Eric Newton
> Assignee: Eric Newton
> Fix For: 1.4.0
>
>
> When an OR clause in a query tree has negations in that subtree and does not have a document which matches the query, the BooleanLogicIterator cannot ascertain whether that subtree has more results to search or whether the subtree is exhausted.
> eg. if we search for
> {noformat}
> (field1 == 'a' && field2 != 'a') || (field2 == 'a' && field1 != 'a')
> {noformat}
> and say DOC1 has both field1 and field2 equal to 'a', BooleanLogicIterator cannot determine whether it needs to call next() to find more reults ore whether to set its own topKey to null and quit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira