Thanks Everyone for the responses. Yes, the way Eric described would work for trivial debugging but when i actually need to debug something in production this would be a big hassle ;-)
For now I am going to mark the field to be stored="true" to get around this problem. We are migrating away from FAST and FAST has a feature where it can dump the entire documents content from the index to a txt file. Thanks again. On Mon, Aug 29, 2011 at 8:27 AM, Erick Erickson <erickerick...@gmail.com>wrote: > You can use Luke to re-construct the doc from > the indexed terms. It takes a while, because it's > not a trivial problem, so I'd use a small index for > verification first.... If you have Luke show > you the doc, it'll return stored fields, but as I remember > there's a button like "reconstruct and edit" that does > what you want... > > You can use the TermsComponent to see what's in > the inverted part of the index, but it doesn't tell > you which document is associated with the terms, > so might not help much. > > But it seems you could do this empirically by > controlling the input to a small set of docs and then > querying on terms you *know* you didn't have in > the input but were in the synonyms.... > > Best > Erick > > On Mon, Aug 29, 2011 at 3:55 AM, pravesh <suyalprav...@yahoo.com> wrote: > > Reconstructing the document might not be possible, since,only the stored > > fields are actually stored document-wise(un-inverted), where as the > > indexed-only fields are put as inverted way. > > In don't think SOLR/Lucene currently provides any way, so, one can > > re-construct document in the way you desire. (It's sort of reverse > > engineering not supported) > > > > Thanx > > Pravesh > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/Viewing-the-complete-document-from-within-the-index-tp3288076p3292111.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > >
