Thanks. Sort of what I was thinking of was the fact that document X, field N, was built via tokenizer/analyzer N. If I need to search an index of document Xs, then I should be using tokenizer/analyzer N without having to "know" that it was built that way.
-----Original Message----- From: Steven Rowe [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 8:04 AM To: java-user@lucene.apache.org Subject: Re: Documents that know more? There has been a long-running thread on the java-dev list about how to allow application-specific "extra stuff" to be placed in the index, at multiple levels of granularity. Some of this conversation is captured on the Wiki at: http://wiki.apache.org/jakarta-lucene/FlexibleIndexing Maybe you could modify the above page to include your requirements? Steve Furash Gary wrote: > I'm sure this is just a design point that I'm missing, but is there a > way to have my document objects know more about themselves? > > At the time I create my document, I know a bit about how information > is being stored in it (e.g., this field represents a SOUNDEX copy, > etc.), yet the logic for that kind of stuff is kept in separate, > unrelated classes that have to be used properly in the document > creation/retrieval programs. > > Would it make sense and, if so, is there a way to embed more logic in > my document objects (or some kind of subclass)? > > Gary Furash, MBA, PMP > Applications Manager, Maricopa County Attorney's Office > > --------------------------------------------------------------------- > 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]
