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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/12/08 09:08:13 UTC

[jira] [Commented] (OAK-2301) QueryEngine should not tokenize fulltext expression by default

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

Thomas Mueller commented on OAK-2301:
-------------------------------------

In theory this information is already available using:
{noformat}
Filter.getSelector().getSelectorConstraints()
{noformat}
but I'm not sure if that's the right approach.

I guess the question is, do we need to distinguish between

{noformat}
(a) contains(., 'fox is running')
(b) contains(., 'fox is') and contains(., 'running')
{noformat}

Right now, both results in +fox +is +running. To get +"fox is running", one has to use:

{noformat}
(c) contains(., '"fox is running"')
{noformat}


> QueryEngine should not tokenize fulltext expression by default
> --------------------------------------------------------------
>
>                 Key: OAK-2301
>                 URL: https://issues.apache.org/jira/browse/OAK-2301
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>            Reporter: Chetan Mehrotra
>            Assignee: Thomas Mueller
>             Fix For: 1.2
>
>
> QueryEngine currently parses the fulltext expression on its own. This would cause issue with index implementation like Lucene which use a different analysis logic. For fulltext search to work properly it should be possible for LuceneIndex to get access to non tokenized text
> For more details refer to http://markmail.org/thread/syoha44std3fm4j2



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