I understand that by having LazyField extend Field it would probably override all methods, but it still seems cleaner given the existing code base. LazyField would only need a package level ctor.
-----Original Message----- From: Yonik Seeley [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 3:45 PM To: java-dev@lucene.apache.org Cc: [EMAIL PROTECTED] Subject: Re: [jira] Commented: (LUCENE-609) Lazy field loading breaks backward compat On 6/21/06, Chris Hostetter <[EMAIL PROTECTED]> wrote: > LazyField doesn't extend Field. Yeah, that's the crux of the matter. I assume this is the case because people need to instantiate Field to add it to a Document at index time, and I guess there is some FIeld baggage that LazyField didn't want to bring along. Which also brings us back to the fact that the Field you index should have never been the Field you get back (but as I've said, it's water long under the bridge). -Yonik http://incubator.apache.org/solr Solr, the open-source Lucene search server --------------------------------------------------------------------- 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]
