lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1837) Reconstruct a Document (stored fields, indexed fields, payloads)
Date Mon, 31 May 2010 22:03:40 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873803#action_12873803
] 

Hoss Man commented on SOLR-1837:
--------------------------------

1) Solr is moving away from having any JSPs at all -- we've been focusing on having RequestHandlers
return all of the data in a structured machine parsable form (with UIs being made possible
using XSLT or AJAX)

2) it seems like instead of adding a new requesthandler (or JSP) for this, it would make more
sense to add this as optional info that could be requested when using LukeRequestHandler's
"id" (or docId) functionality...

http://wiki.apache.org/solr/LukeRequestHandler#id


> 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: Next
>
>         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.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message