jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Parvulescu <alex.parvule...@gmail.com>
Subject Re: multi-selector OR constraints in join queries does not work when free text contraints are used
Date Fri, 17 Jun 2011 11:49:06 GMT
Hi Hassan,

Can you be a bit more specific about this?
What do you mean all nodes? You have an 'or' so it should match a lot.
Also, are you sure the join works as you expect?

I'd also try changing from full text to a simple query on property first,
just to make sure it works, if you think the full text is not working


On Mon, Jun 13, 2011 at 10:34 PM, Hassan <hassan.ismail@hicxsolutions.com>wrote:

> 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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message