You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2009/02/25 00:28:02 UTC
[jira] Created: (SOLR-1036) change default QParser to eliminate
confusion regarding legacy semi-colon sort spec
change default QParser to eliminate confusion regarding legacy semi-colon sort spec
-----------------------------------------------------------------------------------
Key: SOLR-1036
URL: https://issues.apache.org/jira/browse/SOLR-1036
Project: Solr
Issue Type: Improvement
Components: search
Reporter: Hoss Man
Assignee: Hoss Man
Fix For: 1.4
on the trunk, defType currently defaults to the "luceneWithSort" option, which has legacy support for syntax like "field:value;sort_field desc" where the semi-colon character is considered special if-and-only-if there is no "sort" param.
this syntax has proved confusing to new users on at least one occasion, and has been deprecated for a while.
In 1.4 we should change the default to use defType=lucene and add a note for people upgrading about how to force the legacy semicolon behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1036) change default QParser to eliminate
confusion regarding legacy semi-colon sort spec
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-1036:
---------------------------
Description:
on the trunk, defType currently defaults to the "lucenePlusSort" option, which has legacy support for syntax like "field:value;sort_field desc" where the semi-colon character is considered special if-and-only-if there is no "sort" param.
this syntax has proved confusing to new users on at least one occasion, and has been deprecated for a while.
In 1.4 we should change the default to use defType=lucene and add a note for people upgrading about how to force the legacy semicolon behavior.
was:
on the trunk, defType currently defaults to the "luceneWithSort" option, which has legacy support for syntax like "field:value;sort_field desc" where the semi-colon character is considered special if-and-only-if there is no "sort" param.
this syntax has proved confusing to new users on at least one occasion, and has been deprecated for a while.
In 1.4 we should change the default to use defType=lucene and add a note for people upgrading about how to force the legacy semicolon behavior.
> change default QParser to eliminate confusion regarding legacy semi-colon sort spec
> -----------------------------------------------------------------------------------
>
> Key: SOLR-1036
> URL: https://issues.apache.org/jira/browse/SOLR-1036
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 1.4
>
> Attachments: SOLR-1036.patch
>
>
> on the trunk, defType currently defaults to the "lucenePlusSort" option, which has legacy support for syntax like "field:value;sort_field desc" where the semi-colon character is considered special if-and-only-if there is no "sort" param.
> this syntax has proved confusing to new users on at least one occasion, and has been deprecated for a while.
> In 1.4 we should change the default to use defType=lucene and add a note for people upgrading about how to force the legacy semicolon behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1036) change default QParser to eliminate
confusion regarding legacy semi-colon sort spec
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-1036:
---------------------------
Attachment: SOLR-1036.patch
patch that changes the default, adds an upgrade notes to CHANGES.txt for people who want the legacy behavior, and modifies any tests of the semicolon sortspec behavior to specify defType=lucenePlusSort explicitly.
> change default QParser to eliminate confusion regarding legacy semi-colon sort spec
> -----------------------------------------------------------------------------------
>
> Key: SOLR-1036
> URL: https://issues.apache.org/jira/browse/SOLR-1036
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 1.4
>
> Attachments: SOLR-1036.patch
>
>
> on the trunk, defType currently defaults to the "luceneWithSort" option, which has legacy support for syntax like "field:value;sort_field desc" where the semi-colon character is considered special if-and-only-if there is no "sort" param.
> this syntax has proved confusing to new users on at least one occasion, and has been deprecated for a while.
> In 1.4 we should change the default to use defType=lucene and add a note for people upgrading about how to force the legacy semicolon behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-1036) change default QParser to eliminate
confusion regarding legacy semi-colon sort spec
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-1036.
----------------------------
Resolution: Fixed
Committed revision 748763.
> change default QParser to eliminate confusion regarding legacy semi-colon sort spec
> -----------------------------------------------------------------------------------
>
> Key: SOLR-1036
> URL: https://issues.apache.org/jira/browse/SOLR-1036
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 1.4
>
> Attachments: SOLR-1036.patch
>
>
> on the trunk, defType currently defaults to the "lucenePlusSort" option, which has legacy support for syntax like "field:value;sort_field desc" where the semi-colon character is considered special if-and-only-if there is no "sort" param.
> this syntax has proved confusing to new users on at least one occasion, and has been deprecated for a while.
> In 1.4 we should change the default to use defType=lucene and add a note for people upgrading about how to force the legacy semicolon behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.