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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/01/28 09:39:39 UTC

[jira] [Comment Edited] (OAK-3879) Lucene index / compatVersion 2: search for 'abc!' does not work

    [ https://issues.apache.org/jira/browse/OAK-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121032#comment-15121032 ] 

Vikas Saurabh edited comment on OAK-3879 at 1/28/16 8:39 AM:
-------------------------------------------------------------

{quote}
-2. \[ ] - Used for range queries. mod_date:\[20020101 TO 20030101]-
2. \[ ] - Used for range queries. \[20020101 TO 20030101]
3. \{ } - \{Aida TO Carmen}
{quote}
I think we can allow these as well. I think they fall in the realm of {{?, *, ~}}. I agree they might not be very useful/intuitive/user-friendly for a full text component - but they can allow for a custom code/servlet which generates the query based on user input. With fair clarity in doc, that code/servlet can escape stuff as needed. Fulltext search anyway picks the field, and these would allow giving ranges instead of looking for specific values.

I've no strong opinion for {{+}}.


was (Author: catholicon):
{quote}
2. \[ ] - Used for range queries. mod_date:\[20020101 TO 20030101]
3. \{ } - \{Aida TO Carmen}
{quote}
I think we can allow these as well. I think they fall in the realm of {{?, *, ~}}. I agree they might not be very useful/intuitive/user-friendly for a full text component - but they can allow for a custom code/servlet which generates the query based on user input. With fair clarity in doc, that code/servlet can escape stuff as needed. Fulltext search anyway picks the field, and these would allow giving ranges instead of looking for specific values.

I've no strong opinion for {{+}}.

> Lucene index / compatVersion 2: search for 'abc!' does not work
> ---------------------------------------------------------------
>
>                 Key: OAK-3879
>                 URL: https://issues.apache.org/jira/browse/OAK-3879
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Thomas Mueller
>            Assignee: Chetan Mehrotra
>             Fix For: 1.4
>
>         Attachments: OAK-3879-v1.patch
>
>
> When using a Lucene fulltext index with compatVersion 2, then the following query does not return any results. When using compatVersion 1, the correct result is returned.
> {noformat}
> SELECT * FROM [nt:unstructured] AS c 
> WHERE CONTAINS(c.[jcr:description], 'abc!') 
> AND ISDESCENDANTNODE(c, '/content')
> {noformat}
> With compatVersion 1 and 2, searching for just 'abc' works. Also, searching with '=' instead of 'contains' works.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)