Re: parsing debug output for readability

2013-01-10 Thread Yonik Seeley
On Thu, Jan 10, 2013 at 6:16 PM, Petersen, Robert wrote: > Thanks, debug.explain.structured=true helps a lot! Could you also tell me > what these `#8;#0;#0;#0;#1; strings represent in the debug output? That's internally how a number is encoded into a string (5 bytes, the first being binary 8, t

RE: parsing debug output for readability

2013-01-10 Thread Petersen, Robert
PS the wt=ruby param is even better! Great tips. -Original Message- From: Petersen, Robert [mailto:rober...@buy.com] Sent: Thursday, January 10, 2013 3:17 PM To: solr-user@lucene.apache.org Subject: RE: parsing debug output for readability Hi Erik, Thanks, debug.explain.structured

RE: parsing debug output for readability

2013-01-10 Thread Petersen, Robert
debug output for readability Robert - Two options here: - Use debug.explain.structured <http://wiki.apache.org/solr/CommonQueryParameters#debug.explain.structured> - Use wt=ruby&indent=on and it'll come out in an indented fashion browser friendly manner, but even in XML it

Re: parsing debug output for readability

2013-01-10 Thread Erik Hatcher
Robert - Two options here: - Use debug.explain.structured - Use wt=ruby&indent=on and it'll come out in an indented fashion browser friendly manner, but even in XML it should come out with whitespace and newlines