From oak-issues-return-56514-apmail-jackrabbit-oak-issues-archive=jackrabbit.apache.org@jackrabbit.apache.org Mon Nov 13 09:00:09 2017 Return-Path: X-Original-To: apmail-jackrabbit-oak-issues-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 707B310657 for ; Mon, 13 Nov 2017 09:00:09 +0000 (UTC) Received: (qmail 42259 invoked by uid 500); 13 Nov 2017 09:00:09 -0000 Delivered-To: apmail-jackrabbit-oak-issues-archive@jackrabbit.apache.org Received: (qmail 42220 invoked by uid 500); 13 Nov 2017 09:00:09 -0000 Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-issues@jackrabbit.apache.org Received: (qmail 42209 invoked by uid 99); 13 Nov 2017 09:00:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Nov 2017 09:00:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A37891A0FA2 for ; Mon, 13 Nov 2017 09:00:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id csZfjA455qnk for ; Mon, 13 Nov 2017 09:00:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C904C6116A for ; Mon, 13 Nov 2017 09:00:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7D5A1E0D27 for ; Mon, 13 Nov 2017 09:00:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4BF27240DA for ; Mon, 13 Nov 2017 09:00:02 +0000 (UTC) Date: Mon, 13 Nov 2017 09:00:02 +0000 (UTC) From: "Thomas Mueller (JIRA)" To: oak-issues@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OAK-6217) Document tricky statements MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OAK-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-6217: -------------------------------- Fix Version/s: (was: 1.8) 1.9 > Document tricky statements > -------------------------- > > Key: OAK-6217 > URL: https://issues.apache.org/jira/browse/OAK-6217 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query > Reporter: Thomas Mueller > Assignee: Thomas Mueller > Fix For: 1.9 > > > There are some cases, specially if fulltext conditions and aggregation are used, where a query sometimes returns no results even thought with the right index it does return the results. This is a bit hard to understand, because it doesn't match the rule "indexes should only affect performance, not results". One such example is if a query uses one or the other index, but not both. Or if a query uses fulltext conditions on different nodes (parent and child). Examples: > {noformat} > /jcr:root/home//element(*, rep:User) > [jcr:contains(.,'Kerr*') > and jcr:like(@rep:impersonators, '%ccibu%')]/profile > /jcr:root/home//element(*, rep:User) > [jcr:contains(profile,'Kerr*') > and jcr:like(@rep:impersonators, '%ccibu%')]/profile > {noformat} > Related is the usage of relative properties in indexes, excluded / included paths. -- This message was sent by Atlassian JIRA (v6.4.14#64029)