lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] Commented: (SOLR-1837) Reconstruct a Document (stored fields, indexed fields, payloads)
Date Sun, 21 Mar 2010 13:52:27 GMT


Andrzej Bialecki  commented on SOLR-1837:

Re: bugs in Luke that result in missing terms - I recently fixed one such bug, and indeed
it was located in the DocReconstructor - if you are aware of others then please report them
using the Luke issue tracker.

Document reconstruction is a very IO-intensive operation, so I would advise against using
it on a production system, and also it produces inexact results (because analysis is usually
a lossy operation).

> Reconstruct a Document (stored fields, indexed fields, payloads)
> ----------------------------------------------------------------
>                 Key: SOLR-1837
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: Schema and Analysis, web gui
>    Affects Versions: 1.5
>         Environment: All
>            Reporter: Trey Grainger
>            Priority: Minor
>             Fix For: 1.5
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> One Solr feature I've been sorely in need of is the ability to inspect an index for any
particular document.  While the analysis page is good when you have specific content and a
specific field/type your want to test the analysis process for, once a document is indexed
it is not currently possible to easily see what is actually sitting in the index.
> One can use the Lucene Index Browser (Luke), but this has several limitations (gui only,
doesn't understand solr schema, doesn't display many non-text fields in human readable format,
doesn't show payloads, some bugs lead to missing terms, exposes features dangerous to use
in a production Solr environment, slow or difficult to check from a remote location, etc.).
 The document reconstruction feature of Luke provides the base for what can become a much
more powerful tool when coupled with Solr's understanding of a schema, however.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message