[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289093#comment-13289093
]
Chris Male commented on LUCENE-4101:
------------------------------------
bq. A third option is to add boolean isStored to each of XXXFields? So, it's
not stored by default, but then you can do:
I think this would be a step backwards in some ways. As you say, it doesn't
read well and then it's also a question of why stop there? why not set other
metadata via the constructor and we end up where we once were.
At the same time maybe it's a good intermediate step for 4.x while we tackle
the large issue of stored field decoupling in 5.0. Users will be able to
fairly easily control whether the field is stored or not without having to use
any of the expert APIs.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
