lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED
Date Sat, 02 Jun 2012 21:37:23 GMT


Robert Muir commented on LUCENE-4101:

having to now add 2 fields (stored and indexed separately) is a pretty big change.

I'm not sure we should rush it in: personally i dont like the fact you have to
add the field twice.

I think we should have a completed design hashed out for LUCENE-3312
before we go committing intermediate changes to our stable branch. Why must this
issue block 4.0? Can't we do it iteratively in trunk or a development branch, only 
backporting when/if things are solidified and that makes sense?

> ---------------------------
>                 Key: LUCENE-4101
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Blocker
>             Fix For: 4.0, 5.0
>         Attachments: LUCENE-4101.patch
> Spinoff from LUCENE-3312.
> For 4.0 I think we should simplify the sugar field APIs by requiring
> that you add a StoredField if you want to store the field.  Expert users
> can still make a custom FieldType that both stores and indexes...

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