[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474335 ] Ryan McKinley commented on SOLR-162: yes, that is a problem! I'll wait till SOLR-142 gets checked in, then post an update that puts the header stuff back in SolrCore > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch, > SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474333 ] Hoss Man commented on SOLR-162: --- i barely started to scratch the surface looking at this patch while checking something for SOLR-142, but before i forget i wanted to raise one red flag... this patch removes the call to setResponseHeaderValues from SolrCore and moves it to RequestHandlerBase with the assumption that RequestHandlers can take care of it ... this is a bad idea since there is no requirement that RequestHandler extend that class -- any solr1.1 users who have written their own request handlers will be screwed. > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch, > SOLR-162-Admin-XML-luke.patch, SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473975 ] Yonik Seeley commented on SOLR-162: --- > 1. replaces NamedList<> with Map wherever possible. This makes the > direct XML output look funny (the stack > trace is displayed before the > thread name), but it is probably a good idea so clients can easily access > stuff by name. If you want map output semantics (important distinction for other formats like JSON), but the ability to control order w/o the overhead of LinkedHashMap, see SimpleOrderedMap. It subclasses NamedList, so it's easy to convert code that previously used NamedList. > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch, > SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473950 ] Ryan McKinley commented on SOLR-162: 3. ... will be helped by SOLR-112 > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch, > SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[
https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473932
]
Bertrand Delacretaz commented on SOLR-162:
--
I briefly tested this, it looks very useful, and the different RequestHandlers
make the code very modular, way to go!
One nitpick: I'd use "system.properties" instead of "properties", it's more
precise.
And two suggestions related to XSLT transformations for presentation:
1) It'd be good to systematically include in the output XML the class name of
the SolrRequestHandler used. XSLT transforms can then use this info to adapt
themselves to the information being output.
2) It'd be good to name elements, as much as possible, also to allow XSLT
transforms to adapt themselves to the content.
For example, using a NamedList instead of an ArralyList in the "Now show all
the threads" loop in ThreadDumpRequestHandler:
NamedList> lst = new NamedList>();
for (ThreadInfo ti : tinfos) {
lst.add( "thread", getThreadInfo( ti ) );
}
Outputs this:
35
P1-19
RUNNABLE...
where the name="thread" attribute can be used to decide how to present the
contents of the element.
Thinking about it, we might want to add a "datatype" attribute to these lists,
to use when presenting them?
would help present all Thread info in a consistent way, no matter where it
comes from.
> lucene index browser / admin helpers (Luke)
> ---
>
> Key: SOLR-162
> URL: https://issues.apache.org/jira/browse/SOLR-162
> Project: Solr
> Issue Type: New Feature
> Components: web gui
>Reporter: Ryan McKinley
>Priority: Minor
> Attachments: SOLR-162-Admin-XML-luke.patch
>
>
> Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand
> / debug lucene indexes.
> Solr already does a lot of what luke does... but it could do a bit more.
> Specifically:
> * browse top terms across all fields (similar to faceting)
> * browse lucene documents / properties directly
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473920 ] Erik Hatcher commented on SOLR-162: --- Ryan - I would like to see the Maps used instead of NamedLists for things that truly don't need to be lists. For example, /admin/file?wt=ruby returns this: 'files'=>[ 'admin-extra.html',[ 'size',1094, 'modified','2006-12-05T02:30:56Z'],... 'size' and 'modified' should be keys in a hash instead of in a list. Should be no big deal to switch over things where order doesn't matter to maps though. Likewise for /admin/threads and /admin/registry, and maybe others. > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473874 ] Ryan McKinley commented on SOLR-162: check SOLR-149. it adds the path to a request and prints it out with the log. > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473865 ] Erik Hatcher commented on SOLR-162: --- This is truly great stuff, Ryan! *whew* I can't keep up. I did however become really intrigued by this particular patch and tried it out. I like all these details and Flare will certainly leverage this stuff deeply. One comment. for this request http://localhost:/solr/admin/ping?wt=ruby&indent=on all that was logged was this: Feb 16, 2007 8:59:22 PM org.apache.solr.core.SolrCore execute INFO: wt=ruby&indent=on 0 8 I realize this is tangentially related to this issue, and nothing introduced with this patch, but I'd like to see the path (admin/ping, in this case) in the log as well so that requests could be recreated easily. I'm used to the solr/select? stuff and tacking on what I get in the log file, but with the newly revamped mega flexible paths, it'd be handy to see the path here. > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
Wow indeed! Go Ryan. On Feb 16, 2007, at 6:07 PM, Yonik Seeley (JIRA) wrote: [ https://issues.apache.org/jira/browse/SOLR-162? page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#action_12473849 ] Yonik Seeley commented on SOLR-162: --- Wow, what can I say... you continue to out pace us committers, Ryan. I'll try and look at at least *one* of the open issues this weekend. lucene index browser / admin helpers (Luke) --- Key: SOLR-162 URL: https://issues.apache.org/jira/browse/SOLR-162 Project: Solr Issue Type: New Feature Components: web gui Reporter: Ryan McKinley Priority: Minor Attachments: SOLR-162-Admin-XML-luke.patch Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand / debug lucene indexes. Solr already does a lot of what luke does... but it could do a bit more. Specifically: * browse top terms across all fields (similar to faceting) * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473849 ] Yonik Seeley commented on SOLR-162: --- Wow, what can I say... you continue to out pace us committers, Ryan. I'll try and look at at least *one* of the open issues this weekend. > lucene index browser / admin helpers (Luke) > --- > > Key: SOLR-162 > URL: https://issues.apache.org/jira/browse/SOLR-162 > Project: Solr > Issue Type: New Feature > Components: web gui >Reporter: Ryan McKinley >Priority: Minor > Attachments: SOLR-162-Admin-XML-luke.patch > > > Luke (http://www.getopt.org/luke/) is a great tool to help learn / understand > / debug lucene indexes. > Solr already does a lot of what luke does... but it could do a bit more. > Specifically: > * browse top terms across all fields (similar to faceting) > * browse lucene documents / properties directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
