[jira] [Updated] (SOLR-1980) Implement boundary match support
[ https://issues.apache.org/jira/browse/SOLR-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-1980: --- Fix Version/s: (was: 4.0) removing fixVersion=4.0 since there is no evidence that anyone is currently working on this issue. (this can certainly be revisited if volunteers step forward) > Implement boundary match support > > > Key: SOLR-1980 > URL: https://issues.apache.org/jira/browse/SOLR-1980 > Project: Solr > Issue Type: New Feature > Components: query parsers, Schema and Analysis >Reporter: Jan Høydahl > > Sometimes you need to specify that a query should match only at the start or > end of a field, or be an exact match. > We should have a query syntax for boundary match, preferably on a lowest > possible level such as the "lucene" query parser. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-1980) Implement boundary match support
[
https://issues.apache.org/jira/browse/SOLR-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-1980:
--
Component/s: query parsers
Description:
Sometimes you need to specify that a query should match only at the start or
end of a field, or be an exact match.
We should have a query syntax for boundary match, preferably on a lowest
possible level such as the "lucene" query parser.
was:
Sometimes you need to specify that a query should match only at the start or
end of a field, or be an exact match.
Example content:
1) a quick fox is brown
2) quick fox is brown
Example queries:
"^quick fox" -> should only match 2)
"brown$" -> should match 1) and 2)
"^quick fox is brown$" -> should only match 2)
Proposed way of implmementation is through a new BoundaryMatchTokenFilter which
behaves like this:
On the index side it inserts special unique tokens at beginning and end of
field. These could be some weird unicode sequence.
On the query side, it looks for the first character matching "^" or the last
character matching "$" and replaces them with the special tokens.
Shortening down the description field. I removed these paragraphs:
{quote}
Proposed way of implmementation is through a new BoundaryMatchTokenFilter which
behaves like this:
On the index side it inserts special unique tokens at beginning and end of
field. These could be some weird unicode sequence.
On the query side, it looks for the first character matching "^" or the last
character matching "$" and replaces them with the special tokens.
{quote}
> Implement boundary match support
>
>
> Key: SOLR-1980
> URL: https://issues.apache.org/jira/browse/SOLR-1980
> Project: Solr
> Issue Type: New Feature
> Components: query parsers, Schema and Analysis
>Reporter: Jan Høydahl
> Fix For: 4.0
>
>
> Sometimes you need to specify that a query should match only at the start or
> end of a field, or be an exact match.
> We should have a query syntax for boundary match, preferably on a lowest
> possible level such as the "lucene" query parser.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-1980) Implement boundary match support
[ https://issues.apache.org/jira/browse/SOLR-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-1980: -- Fix Version/s: 4.0 Tagging this for 4.0, hoping to revive some work on it... Btw. Any comments to my last syntax suggestion, utilizing term positions @N:M ? > Implement boundary match support > > > Key: SOLR-1980 > URL: https://issues.apache.org/jira/browse/SOLR-1980 > Project: Solr > Issue Type: New Feature > Components: Schema and Analysis >Reporter: Jan Høydahl > Fix For: 4.0 > > > Sometimes you need to specify that a query should match only at the start or > end of a field, or be an exact match. > Example content: > 1) a quick fox is brown > 2) quick fox is brown > Example queries: > "^quick fox" -> should only match 2) > "brown$" -> should match 1) and 2) > "^quick fox is brown$" -> should only match 2) > Proposed way of implmementation is through a new BoundaryMatchTokenFilter > which behaves like this: > On the index side it inserts special unique tokens at beginning and end of > field. These could be some weird unicode sequence. > On the query side, it looks for the first character matching "^" or the last > character matching "$" and replaces them with the special tokens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
