lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (Updated) (JIRA)" <>
Subject [jira] [Updated] (SOLR-2989) Solr admin (Luke request handler) doesn't order the fields alphabetically
Date Wed, 28 Dec 2011 20:30:30 GMT


Erick Erickson updated SOLR-2989:

    Attachment: SOLR-2989.patch

First cut at a patch. This is for 3x because that's where I happened to be working, but if
we carry this forward, I can put it on trunk to I assume.
> Solr admin (Luke request handler) doesn't order the fields alphabetically
> -------------------------------------------------------------------------
>                 Key: SOLR-2989
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: SearchComponents - other
>    Affects Versions: 3.6, 4.0
>         Environment: all
>            Reporter: Erick Erickson
>            Priority: Minor
>         Attachments: SOLR-2989.patch
> It's always bugged me that the fields list for admin/schema browser haven't been alphabetical.
We have users who have 100s of fields and it's hard to orient in an unordered list. 
> I'll attach a patch momentarily that starts moves toward this. The thing I need someone
to render judgement on is whether implementing the Comparable interface on SchemaField and
FieldType are in any way dangerous. Note that they only compare on name, secondary and tertiary
sources are unnecessary I think.
> The other interesting bit is that the list of fields is actually (apparently) fetched
in two stages. The first stage gets the ones in the schema and the second one gets dynamic
fields that have been realized. So the "fields" section actually has two separate ordered
sections. Which is kind of ugly, but given the new admin interface coming in 4.x I don't feel
the urge to fix this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message