You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2009/05/27 22:33:45 UTC
[jira] Created: (LUCENE-1665) Remove SortField.AUTO
Remove SortField.AUTO
---------------------
Key: LUCENE-1665
URL: https://issues.apache.org/jira/browse/LUCENE-1665
Project: Lucene - Java
Issue Type: Improvement
Components: Search
Reporter: Michael McCandless
Assignee: Michael McCandless
Priority: Minor
Fix For: 2.9
I'd like to remove SortField.AUTO... it's dangerous for Lucene to
guess the type of your field, based on the first term it encounters.
It can easily be wrong, and, whether it's wrong or right could
suddenly change as you index different documents.
It unexepctedly binds SortField to needing an IndexReader to do the
guessing.
It's caused various problems in the past (most recently, for me on
LUCENE-1656) as we fix other issues/make improvements.
I'd prefer that users of Lucene's field sort be explicit about the
type that Lucene should cast the field to. Someday, if we have
optional strong[er] typing of Lucene's fields, such type information
would already be known. But in the meantime, I think users should be
explicit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-1665) Remove SortField.AUTO
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713749#action_12713749 ]
Mark Miller commented on LUCENE-1665:
-------------------------------------
+1. It doesnt work correctly with MultiSearcher either.
> Remove SortField.AUTO
> ---------------------
>
> Key: LUCENE-1665
> URL: https://issues.apache.org/jira/browse/LUCENE-1665
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.9
>
>
> I'd like to remove SortField.AUTO... it's dangerous for Lucene to
> guess the type of your field, based on the first term it encounters.
> It can easily be wrong, and, whether it's wrong or right could
> suddenly change as you index different documents.
> It unexepctedly binds SortField to needing an IndexReader to do the
> guessing.
> It's caused various problems in the past (most recently, for me on
> LUCENE-1656) as we fix other issues/make improvements.
> I'd prefer that users of Lucene's field sort be explicit about the
> type that Lucene should cast the field to. Someday, if we have
> optional strong[er] typing of Lucene's fields, such type information
> would already be known. But in the meantime, I think users should be
> explicit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Resolved: (LUCENE-1665) Remove SortField.AUTO
Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-1665.
----------------------------------------
Resolution: Fixed
> Remove SortField.AUTO
> ---------------------
>
> Key: LUCENE-1665
> URL: https://issues.apache.org/jira/browse/LUCENE-1665
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.9
>
>
> I'd like to remove SortField.AUTO... it's dangerous for Lucene to
> guess the type of your field, based on the first term it encounters.
> It can easily be wrong, and, whether it's wrong or right could
> suddenly change as you index different documents.
> It unexepctedly binds SortField to needing an IndexReader to do the
> guessing.
> It's caused various problems in the past (most recently, for me on
> LUCENE-1656) as we fix other issues/make improvements.
> I'd prefer that users of Lucene's field sort be explicit about the
> type that Lucene should cast the field to. Someday, if we have
> optional strong[er] typing of Lucene's fields, such type information
> would already be known. But in the meantime, I think users should be
> explicit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org