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, 09 Jun 2012 11:59:43 GMT


Robert Muir commented on LUCENE-4101:

Well I think for people like you, if you enjoy that type of API you should be able to do it.
But such a factory API ultimately requires a real CTOR anyway :)
So it can just be seen as sugar-on-top.

As far as doc/field I think we should just provide the most minimal/simplest api that meets
two use cases:
# non-expert users just trying to use our simple apis to get stuff indexed.
# expert users trying to build things on top.

I think its this mix of use cases that makes this API such a bikeshed.

But i totally think something like this patch is the right way to go so that non-expert users
store things! 

Perhaps the issue title should be renamed, i could care less if XXXField.TYPE_STORED 
is there or not, thats the expert API? I think it should take a backseat to the non-expert

> ---------------------------
>                 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, LUCENE-4101.patch, 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