[
https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847866#action_12847866
]
Trey Grainger commented on SOLR-1837:
-------------------------------------
I've been working on implementing the document reconstruction feature over the
past week and have created an additional admin page which exposes it. The
functionality is essentially a reworking of the lucene document reconstruction
functionality in Luke, but with improvements to handle the problems listed in
the jira issue description above.
I'll be pushing up a patch soon and will look forward to any additional
recommendations after others have had a chance to try it out.
> Reconstruct a Document (stored fields, indexed fields, payloads)
> ----------------------------------------------------------------
>
> Key: SOLR-1837
> URL: https://issues.apache.org/jira/browse/SOLR-1837
> 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.
