Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Mon, 13 Jun 2011 23:34:59 +0300 (EEST)
From: Hassan <hassan.ismail@hicxsolutions.com>
To: users@jackrabbit.apache.org
Subject: multi-selector OR constraints in join queries does not work when free
 text contraints are used
Message-ID: 
 <131b8bb3-2df8-401c-9192-9f6960354fb8@hassan-HP-Pavilion-dv6-Notebook-PC>
In-Reply-To: 
 <0d0373cd-605b-4934-aa96-9a2dbcf60de0@hassan-HP-Pavilion-dv6-Notebook-PC>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0

Hi,

Although 2.2.7 fixes the "Unsupported" exception when using multi-selector OR constraints, it seems to return wrong results when using free text search constraints for both selectors. The query seems to return ALL nodes.

Example Query:
elect c.* from [internal:content]  as c   inner  JOIN [nt:resource] as b  ON isdescendantnode(b,c)  where  (  
CONTAINS(b.*, 'message*')  or  CONTAINS(c.*, 'message*') 
 ) 

Note: the query above used to give an "Unsupported" exception  in 2.2.5

Is this a bug or am I just doing something wrong?

Thanks,
Hassan