You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Sam Hough (JIRA)" <ji...@apache.org> on 2005/10/19 10:58:44 UTC
[jira] Created: (LUCENE-457) FieldCacheImpl take advantage of term info already being sorted
FieldCacheImpl take advantage of term info already being sorted
---------------------------------------------------------------
Key: LUCENE-457
URL: http://issues.apache.org/jira/browse/LUCENE-457
Project: Lucene - Java
Type: Improvement
Components: Search
Versions: 1.4
Reporter: Sam Hough
Priority: Minor
FieldCacheImpl.getStrings could take advantage of term info already being sorted
lexically. Would it be possible to have a "index order" mode which returns an array
of ints rather than strings storing a scalar value that increments by one for each
new term.
Presumably there would be a big memory profile advantage in not holding onto
the term value Strings and a lesser one in int comparison being slightly quicker than
String.compareTo.
Sorry if I have missed something obvious. I don't know the code very well.
Regards
Sam
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Closed: (LUCENE-457) FieldCacheImpl take advantage of term info already being sorted
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-457?page=all ]
Otis Gospodnetic closed LUCENE-457:
-----------------------------------
Resolution: Won't Fix
> FieldCacheImpl take advantage of term info already being sorted
> ---------------------------------------------------------------
>
> Key: LUCENE-457
> URL: http://issues.apache.org/jira/browse/LUCENE-457
> Project: Lucene - Java
> Type: Improvement
> Components: Search
> Versions: 1.4
> Reporter: Sam Hough
> Priority: Minor
>
> FieldCacheImpl.getStrings could take advantage of term info already being sorted
> lexically. Would it be possible to have a "index order" mode which returns an array
> of ints rather than strings storing a scalar value that increments by one for each
> new term.
> Presumably there would be a big memory profile advantage in not holding onto
> the term value Strings and a lesser one in int comparison being slightly quicker than
> String.compareTo.
> Sorry if I have missed something obvious. I don't know the code very well.
> Regards
> Sam
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-457) FieldCacheImpl take advantage of term info already being sorted
Posted by "Sam Hough (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-457?page=comments#action_12332532 ]
Sam Hough commented on LUCENE-457:
----------------------------------
Doh. Guess could do merge sort but does make it much less attractive.
Presumably making sorting algorithm better than O(N) for memory would
mean changes to storage format so be 2.0 thing :(
Thanks Yonik.
Guess this should be closed. I for one can't think of a way of making it work.
> FieldCacheImpl take advantage of term info already being sorted
> ---------------------------------------------------------------
>
> Key: LUCENE-457
> URL: http://issues.apache.org/jira/browse/LUCENE-457
> Project: Lucene - Java
> Type: Improvement
> Components: Search
> Versions: 1.4
> Reporter: Sam Hough
> Priority: Minor
>
> FieldCacheImpl.getStrings could take advantage of term info already being sorted
> lexically. Would it be possible to have a "index order" mode which returns an array
> of ints rather than strings storing a scalar value that increments by one for each
> new term.
> Presumably there would be a big memory profile advantage in not holding onto
> the term value Strings and a lesser one in int comparison being slightly quicker than
> String.compareTo.
> Sorry if I have missed something obvious. I don't know the code very well.
> Regards
> Sam
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-457) FieldCacheImpl take advantage of term info already being sorted
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-457?page=comments#action_12332477 ]
Yonik Seeley commented on LUCENE-457:
-------------------------------------
I've thought the same thing... StringIndex without storing the strings.
The actual string values are sometimes needed though... a MultiSearcher needs them in order to sort documents from multiple indicies.
> FieldCacheImpl take advantage of term info already being sorted
> ---------------------------------------------------------------
>
> Key: LUCENE-457
> URL: http://issues.apache.org/jira/browse/LUCENE-457
> Project: Lucene - Java
> Type: Improvement
> Components: Search
> Versions: 1.4
> Reporter: Sam Hough
> Priority: Minor
>
> FieldCacheImpl.getStrings could take advantage of term info already being sorted
> lexically. Would it be possible to have a "index order" mode which returns an array
> of ints rather than strings storing a scalar value that increments by one for each
> new term.
> Presumably there would be a big memory profile advantage in not holding onto
> the term value Strings and a lesser one in int comparison being slightly quicker than
> String.compareTo.
> Sorry if I have missed something obvious. I don't know the code very well.
> Regards
> Sam
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org