You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/02/16 08:07:12 UTC
[jira] [Updated] (OAK-2517) Support IS NULL based property
restrictions in LucenePropertyIndex
[ https://issues.apache.org/jira/browse/OAK-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra updated OAK-2517:
---------------------------------
Attachment: OAK-2517.patch
Patch implementing the above approach. Here it is assumed that a PropertyRestriction mean following
{code}
static boolean propertyNotNullRestriction(PropertyRestriction pr) {
return pr.first == null && pr.last == null && !pr.lastIncluding && !pr.firstIncluding;
}
static boolean propertyIsNullRestriction(PropertyRestriction pr) {
return pr.first == null && pr.last == null && pr.lastIncluding && pr.firstIncluding;
}
{code}
> Support IS NULL based property restrictions in LucenePropertyIndex
> ------------------------------------------------------------------
>
> Key: OAK-2517
> URL: https://issues.apache.org/jira/browse/OAK-2517
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: oak-lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.2, 1.0.12
>
> Attachments: OAK-2517.patch
>
>
> Currently queries involving IS NULL perform slow with Lucene as they are implemented as a filter. Instead such restriction should be evaluated via index itself
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)