[ https://issues.apache.org/jira/browse/SOLR-9185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Rowe updated SOLR-9185: ----------------------------- Attachment: SOLR-9185.patch Another WIP patch. Progress: parser generates (with {{ant javacc}}), compiles (after first applying the patch from LUCENE-2605 and regenerating), and most tests pass with the default split-on-whitespace option (i.e.: *true* - preserve old behavior). Failing tests (haven't investigated yet): * {{TestSolrQueryParser.testComments()}} * {{TestPostingsSolrHighlighter}}: {{testDefaultSummary()}} and {{testEmptySnippet()}} > Solr's "Lucene"/standard query parser should not split on whitespace before > sending terms to analysis > ----------------------------------------------------------------------------------------------------- > > Key: SOLR-9185 > URL: https://issues.apache.org/jira/browse/SOLR-9185 > Project: Solr > Issue Type: Bug > Reporter: Steve Rowe > Assignee: Steve Rowe > Attachments: SOLR-9185.patch, SOLR-9185.patch > > > Copied from LUCENE-2605: > The queryparser parses input on whitespace, and sends each whitespace > separated term to its own independent token stream. > This breaks the following at query-time, because they can't see across > whitespace boundaries: > n-gram analysis > shingles > synonyms (especially multi-word for whitespace-separated languages) > languages where a 'word' can contain whitespace (e.g. vietnamese) > Its also rather unexpected, as users think their > charfilters/tokenizers/tokenfilters will do the same thing at index and > querytime, but > in many cases they can't. Instead, preferably the queryparser would parse > around only real 'operators'. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org