Changing the subject for a JIRA-issue (Was: [jira] Created: (LUCENE-2335) optimization: when sorting by field, if index has one segment and field values are not needed, do not load String[] into field cache)

[Toke Eskildsen <te...@statsbiblioteket.dk>]

The current subject and description of
https://issues.apache.org/jira/browse/LUCENE-2335
is obsolete due to new knowledge.

Is it possible to change it? If not, what is the policy here? To open a
new issue and close the old one?

Cc: To Michael McCandless as he is the reporter of the issue.


If it can be changed, I would like to propose the following:

Optimization: Locale-based sort by field with low memory overhead

The current implementation of locale-based sort in Lucene uses the
FieldCache which keeps all sort-terms in memory. Beside the huge memory
overhead, searching requires comparison of terms with collator.compare
every time, making searches with millions of hits fairly expensive.

An idea for an alternative implementation is to create a packed list of
pre-sorted ordinals for the sort terms and a map from document-IDs to
entries in the sorted ordinals list.

This results in very low memory overhead and faster sorted searches, at
the cost of increased startup-time. As the ordinals can be resolved to
terms after the sorting has been performed, this approach supports
fillFields=true.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org

Re: Changing the subject for a JIRA-issue (Was: [jira] Created: (LUCENE-2335) optimization: when sorting by field, if index has one segment and field values are not needed, do not load String[] into field cache)

[Chris Hostetter <ho...@fucit.org>]

: > Is it possible to change it? If not, what is the policy here? To open a
: > new issue and close the old one?
	...
: In this case, that would mean either closing this issue and opening a new one,
: or taking the discussion to the mailing list where subject headers may be
: modified as the conversation evolves.  

Any one who can "edit" an issue (ie: all hte committers, and anyone in the 
"developer" group) can change the summary (which change the email 
subjects)

It's not clear to me what the summar of LUCENE-2335 should be, but 
McCandless opened the issue, he can certainly fix the summar as the issue 
evolves.




-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org

Re: Changing the subject for a JIRA-issue (Was: [jira] Created: (LUCENE-2335) optimization: when sorting by field, if index has one segment and field values are not needed, do not load String[] into field cache)

[Marvin Humphrey <ma...@rectangular.com>]

On Tue, Apr 06, 2010 at 11:26:23AM +0200, Toke Eskildsen wrote:
> The current subject and description of
> https://issues.apache.org/jira/browse/LUCENE-2335
> is obsolete due to new knowledge.
> 
> Is it possible to change it? If not, what is the policy here? To open a
> new issue and close the old one?

No policy, per se.  Here's my take, FWIW:

Do whatever it takes to keep the subject line of your messages in tune with
the content of your messages.  When they conflict, it becomes harder to follow
the conversation, and our knowledge base degrades because relevant posts
become harder to discover via search.

In this case, that would mean either closing this issue and opening a new one,
or taking the discussion to the mailing list where subject headers may be
modified as the conversation evolves.  

Marvin Humphrey


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org