[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_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 lst 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:
NamedListNamedListObject lst = new NamedListNamedListObject();
for (ThreadInfo ti : tinfos) {
lst.add( thread, getThreadInfo( ti ) );
}
Outputs this:
lst name=thread
long name=id35/long
str name=nameP1-19/str
str name=stateRUNNABLE/str...
where the name=thread attribute can be used to decide how to present the
contents of the lst element.
Thinking about it, we might want to add a datatype attribute to these lists,
to use when presenting them?
lst datatype=java.lang.Thread
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.
Re: [Solr Wiki] Update of FrontPage by HossMan
On 2/17/07, Apache Wiki [EMAIL PROTECTED] wrote: ...The following page has been changed by HossMan: http://wiki.apache.org/solr/FrontPage.. FYI, I have asked infrastructure@ about using the http://moinmoin.wikiwikiweb.de/AntiSpamGlobalSolution to prevent wiki spam. -Bertrand
[jira] Updated: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-162: --- Attachment: SOLR-162-Admin-XML-luke.patch Thanks for your feedback, here is an updated version that: 1. replaces NamedList with MapString, 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. 2. I added a parameter echoHandler that behaves just like echoParams - it writes the handler name to the responseHeader. 3. I added the default params echoHandler=true and echoParams=explicit to all the /admin/* handlers. This gets a bit verbose and will be helped by 4. I moved the responseHeader writing from SolrCore to RequestBaseHandler. This is good because RequestHandler authors control the header more explicitly if necessary. 5. added a name to each thread in the thread list. I don't see any other lists without names, but i could be missing something. 6. changed the output in PropertiesRequestHandler from properties to system.properties 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-140) single quote in search query will break any sorts
[ https://issues.apache.org/jira/browse/SOLR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473955 ] Yonik Seeley commented on SOLR-140: --- Committed. Perhaps try the next nightly build (2007-02-18 or later) with the app server in /example to verify. single quote in search query will break any sorts - Key: SOLR-140 URL: https://issues.apache.org/jira/browse/SOLR-140 Project: Solr Issue Type: Bug Components: search Affects Versions: 1.1.0 Environment: SOLR nightly build 2007-02-01, but old builds as well. Ubuntu 6.06 LTS server. Tomcat 5.5.20 Reporter: John Kleven Attachments: split_sort.txt Query strings that contain a single quote, properly escaped, break *as soon as you add a sort field*. For example, If I want to search for the word jam's including the single quote, I can. But as soon as I add a sort criteria to the URL, it breaks. Note: %27 is a single quote encoded for URI's Here's the examples http://10.0.101.11:8080/forsale/select/?q=jam%27s-- this works (i get ~20 hits back) http://10.0.101.11:8080/forsale/select/?q=jam%27s;score%20desc --- this doesn't (get 0 hits back) Seems that if the first query works, it shouldn't be breakable just by telling it explicitly to sort on score?? All other sorts break in this scenario as well ( i.e., price, etc). email rsp from Yonik: Hmmm, Solr tries to be smart about splitting the query from the sort specification. If it sees a semicolon inside quotes (single or double), or backslash escaped, then it will treat it as part of the query. An immediate workaround would be to query for jam's or jam\'s It would be helpful if you could open a JIRA issue for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: solr.py patch
Thanks Wade, I committed these changes.
-Yonik
On 2/10/07, Wade Leftwich [EMAIL PROTECTED] wrote:
I'm setting up Solr to work with Zope and Django sites, so was very pleased
to find clients/python/solr.py . I see in the comments that it's a prototype
and subject to change, but here's a small patch.
###
Index: client/python/solr.py
===
--- client/python/solr.py (revision 505818)
+++ client/python/solr.py (working copy)
@@ -158,12 +158,12 @@
if optimize: xstr='optimize'
if not waitSearcher: #just handle deviations from the default
if not waitFlush: xstr +=' waitFlush=false waitSearcher=false'
- else: xstr += 'waitSearcher=false'
+ else: xstr += ' waitSearcher=false'
xstr += '/'
return self.doUpdateXML(xstr)
def search(self, **params):
-request=urllib.urlencode(params)
+request=urllib.urlencode(params, doseq=True)
try:
rsp = self.doPost(self.solrBase+'/select', request, self.formheaders)
data = rsp.read()
###
Fixing a typo in SolrConnection.commit(), and letting
SolrConnection.search() take multi-valued params by providing the doseq=True
arg to urllib.urlencode():
In [54]: urlencode({'pepboys':['Manny','Moe','Jack']})
Out[54]: 'pepboys=%5B%27Manny%27%2C+%27Moe%27%2C+%27Jack%27%5D'
In [55]: urlencode({'pepboys':['Manny','Moe','Jack']}, doseq=True)
Out[55]: 'pepboys=Mannypepboys=Moepepboys=Jack'
-- Wade Leftwich
Ithaca, NY
[jira] Updated: (SOLR-162) lucene index browser / admin helpers (Luke)
[ https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-162: --- Attachment: SOLR-162-Admin-XML-luke.patch using SimpleOrderedMap - this keeps nice ordering for XML and uses map syntax for JSON/ruby. thanks Yonik! 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.
