[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288654#comment-13288654
]
Michael McCandless commented on LUCENE-4101:
--------------------------------------------
A third option is to add boolean isStored to each of XXXFields? So, it's not
stored by default, but then you can do:
{noformat}
new StringField("foo", "bar", true);
{noformat}
To make a both indexed and stored StringField ...
But I don't really like that; I think it doesn't read as well as adding a
separate StoredField also added to the doc. And I'd rather keep the XXXField
ctors simple...
> Remove XXXField.TYPE_STORED
> ---------------------------
>
> Key: LUCENE-4101
> URL: https://issues.apache.org/jira/browse/LUCENE-4101
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
