lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trey Grainger (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1837) Reconstruct a Document (stored fields, indexed fields, payloads)
Date Sun, 21 Mar 2010 19:21:27 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Trey Grainger updated SOLR-1837:
--------------------------------

    Attachment: SOLR-1837.patch

Here's what I have thusfar.  Only bug I currently know about is that Solr multi-valued fields
(i.e. <field name="x">value1</field><field name="x">value2</field>)
currently display as concatenated together instead of as an array of separate fields in the
"stored fields" view.

I've referred to the tool in the admin interface as the "Document Inspector" instead of "Document
Reconstructor" to prevent confusion over lost/changed/added terms due to index-time analysis.

Any feedback appreciated.

> 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
>
>         Attachments: SOLR-1837.patch
>
>   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.


Mime
View raw message