[jira] Created: (SOLR-1836) website merge related changes
website merge related changes - Key: SOLR-1836 URL: https://issues.apache.org/jira/browse/SOLR-1836 Project: Solr Issue Type: Improvement Reporter: Yonik Seeley Priority: Minor Website related changes due to the lucene/solr merge. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1836) website merge related changes
[ https://issues.apache.org/jira/browse/SOLR-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847780#action_12847780 ] Yonik Seeley commented on SOLR-1836: At a minimum, we should have a shared committer page. Prob just link the Solr one to the Lucene one. website merge related changes - Key: SOLR-1836 URL: https://issues.apache.org/jira/browse/SOLR-1836 Project: Solr Issue Type: Improvement Reporter: Yonik Seeley Priority: Minor Website related changes due to the lucene/solr merge. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1836) website merge related changes
[ https://issues.apache.org/jira/browse/SOLR-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-1836: --- Attachment: SOLR-1836_lucene.patch SOLR-1836_solr.patch Here's a simple patch that merges the committer pages. I also removed the author tags and moved Mike Klaas to emeritus per his request. website merge related changes - Key: SOLR-1836 URL: https://issues.apache.org/jira/browse/SOLR-1836 Project: Solr Issue Type: Improvement Reporter: Yonik Seeley Priority: Minor Attachments: SOLR-1836_lucene.patch, SOLR-1836_solr.patch Website related changes due to the lucene/solr merge. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-1837) Reconstruct a Document (stored fields, indexed fields, payloads)
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 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.
[jira] Updated: (SOLR-1837) Reconstruct a Document (stored fields, indexed fields, payloads)
[ https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trey Grainger updated SOLR-1837: Remaining Estimate: 168h (was: 120h) Original Estimate: 168h (was: 120h) 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.
[jira] Commented: (SOLR-1837) Reconstruct a Document (stored fields, indexed fields, payloads)
[ https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
