lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-3288) audit tutorial before 4.0 release
Date Mon, 20 Aug 2012 14:23:38 GMT


Yonik Seeley commented on SOLR-3288:

Although such a string field could be used for sorting as well as faceting.
Any other ideas for a good name?

The conventions we already have involve appending an "s" for multiValued dynamic fields, and
I'm just worried that trying to do something like append a "U" for unstored or an "I" for
indexed-only starts to make names too ugly.

Maybe something slightly more radical is called for: perhaps we should never store copyField
targets - that would allow us to use the same dynamic field multiple ways.

> audit tutorial before 4.0 release
> ---------------------------------
>                 Key: SOLR-3288
>                 URL:
>             Project: Solr
>          Issue Type: Task
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Blocker
>             Fix For: 4.0
> Prior to the 4.0 release, audit the tutorial and verify...
> * command line output looks reasonable
> * analysis examples/discussion matches field types used
> * links to admin UI are correct for new UI.

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