Interface's (FieldCache is an interface) fields are always static (and final? - I think they are., else it would make no sense). So in general you should not be able to change the field in an interface.
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Shai Erera [mailto:[email protected]] > Sent: Friday, June 04, 2010 6:55 PM > To: [email protected]; [email protected] > Subject: Re: Extending FieldCache > > Actually DEFAULT is not defined final, but I haven't tried assigning a value to > it. > > Anyway, even if that's resolved, the API relies only on the field name, and if I > need to pass a Term then it's not reallly possible. > I've also looked at LUCENE-831 but it seems this work is on hold for more > than a year . > > I can impl my cache layer and duplicate TopFieldCollector logic. > > Thanks anyway, > Shai > > On Friday, June 4, 2010, Yonik Seeley <[email protected]> wrote: > > On Fri, Jun 4, 2010 at 4:38 AM, Shai Erera <[email protected]> wrote: > >> I've looked into extending FieldCache, so that I can read the values > >> to cache in a custom manner (not necessarily from the field's > >> values). Just want to confirm my understanding - it looks like if I > >> want to do it, I'll need to create my own FieldCache impl, and then > >> set FieldCache.DEFAULT with it? > > > > Interface members are final, so you can't actually implement your own. > > > > -Yonik > > http://www.lucidimagination.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For > > additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
