[
https://issues.apache.org/jira/browse/OAK-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071319#comment-14071319
]
David Gonzalez commented on OAK-1965:
-------------------------------------
[~jukkaz] FYI - after installing this, my instance has been "restarting" for 6+
hours; When I enabled DEBUG on org.jackrabbit logs, I see a wall of...
{noformat}
22.07.2014 23:08:46.051 *DEBUG* [TarMK compaction thread
[/xxx/repository/segmentstore], active since Tue Jul 22 02:00:00 EDT 2014,
previous max duration 0ms] org.apache.jackrabbit.oak.plugins.segment.SegmentId
Loading segment 4b993a00-2233-4c8c-a9fa-e9e4fab8a665
{noformat}
With 147 and counting new segment store tar files since the installation.
Doesn't seem directly related, but was an unexpected side effect of installing
this jar.
> Support for constraints like: foo = 'X' OR bar = 'Y'
> ----------------------------------------------------
>
> Key: OAK-1965
> URL: https://issues.apache.org/jira/browse/OAK-1965
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, query
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 1.1
>
> Attachments: oak-core-1.0.3-OAK-1965-SNAPSHOT.jar
>
>
> Consider the following query statement:
> {noformat}
> SELECT * FROM [nt:base] WHERE [foo] = 'X OR [bar] = 'Y'
> {noformat}
> Such a query could be fairly efficiently executed against a property index
> that indexes the values of both "foo" and "bar" properties. However, the
> query engine doesn't pass such OR constraints down to the index
> implementations, so we currently can't leverage such an index for this query.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
