Hudson build is back to normal: Solr-Nightly #171
See http://lucene.zones.apache.org:8080/hudson/job/Solr-Nightly/171/changes
[jira] Commented: (SOLR-216) Improvements to solr.py
[
https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519688
]
Yonik Seeley commented on SOLR-216:
---
I quickly tried the example in comments, and ran into some issues:
The examples should be made to work with the example Solr install... so instead
of
c = SolrConnection('http://localhost:8983')
c.add(id='500', name='python test doc', active=True)
It should be
c = SolrConnection('http://localhost:8983/solr')#need to specify
full path to solr
c.add(id='500', name='python test doc')#active field
doesn't exist
After that, a document is added, but I get an exception on the python side.
I guess it's probably related to response parsing? It should probably be
updated to check the HTTP response and not parse the response.
Improvements to solr.py
---
Key: SOLR-216
URL: https://issues.apache.org/jira/browse/SOLR-216
Project: Solr
Issue Type: Improvement
Components: clients - python
Affects Versions: 1.2
Reporter: Jason Cater
Assignee: Mike Klaas
Priority: Trivial
Attachments: solr.py
I've taken the original solr.py code and extended it to include higher-level
functions.
* Requires python 2.3+
* Supports SSL (https://) schema
* Conforms (mostly) to PEP 8 -- the Python Style Guide
* Provides a high-level results object with implicit data type conversion
* Supports batching of update commands
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-216) Improvements to solr.py
[ https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-216: -- Attachment: solr.py Uploading a slightly patched version that works with the new update response format, and fixes some exception related issues (http reason is now grabbed, exception trace prints httpcode and reason) Improvements to solr.py --- Key: SOLR-216 URL: https://issues.apache.org/jira/browse/SOLR-216 Project: Solr Issue Type: Improvement Components: clients - python Affects Versions: 1.2 Reporter: Jason Cater Assignee: Mike Klaas Priority: Trivial Attachments: solr.py, solr.py I've taken the original solr.py code and extended it to include higher-level functions. * Requires python 2.3+ * Supports SSL (https://) schema * Conforms (mostly) to PEP 8 -- the Python Style Guide * Provides a high-level results object with implicit data type conversion * Supports batching of update commands -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
SOLR-139 - updateable documents
I have a need for updateable documents and starting to tinker with SOLR-139, but having issues with the latest patches applying: $ curl https://issues.apache.org/jira/secure/attachment/12362787/ getStoredFields.patch | patch -p0 --dry-run % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total Spent Left Speed 100 25385 100 253850 0 29876 0 --:--:-- --:--:-- --:--:-- 91312 patching file src/test/org/apache/solr/update/TestUpdateStress.java patching file src/java/org/apache/solr/update/UpdateHandler.java patching file src/java/org/apache/solr/update/DirectUpdateHandler.java patching file src/java/org/apache/solr/update/DirectUpdateHandler2.java Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 15 out of 15 hunks ignored -- saving rejects to file src/java/org/ apache/solr/update/DirectUpdateHandler2.java.rej What's the step-by-step way to get these patches applied successfully to trunk? Thanks, Erik
[jira] Updated: (SOLR-139) Support updateable/modifiable documents
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-139: --- Attachment: SOLR-139-ModifyInputDocuments.patch applies with trunk Support updateable/modifiable documents --- Key: SOLR-139 URL: https://issues.apache.org/jira/browse/SOLR-139 Project: Solr Issue Type: Improvement Components: update Reporter: Ryan McKinley Assignee: Ryan McKinley Attachments: getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139-XmlUpdater.patch, SOLR-269+139-ModifiableDocumentUpdateProcessor.patch It would be nice to be able to update some fields on a document without having to insert the entire document. Given the way lucene is structured, (for now) one can only modify stored fields. While we are at it, we can support incrementing an existing value - I think this only makes sense for numbers. for background, see: http://www.nabble.com/loading-many-documents-by-ID-tf3145666.html#a8722293 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (SOLR-139) Support updateable/modifiable documents
that was quick! thanks ryan! On Aug 14, 2007, at 2:15 PM, Ryan McKinley (JIRA) wrote: [ https://issues.apache.org/jira/browse/SOLR-139? page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-139: --- Attachment: SOLR-139-ModifyInputDocuments.patch applies with trunk Support updateable/modifiable documents --- Key: SOLR-139 URL: https://issues.apache.org/jira/browse/SOLR-139 Project: Solr Issue Type: Improvement Components: update Reporter: Ryan McKinley Assignee: Ryan McKinley Attachments: getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139- IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139- IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139- IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch, SOLR-139- ModifyInputDocuments.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139-ModifyInputDocuments.patch, SOLR-139- ModifyInputDocuments.patch, SOLR-139-XmlUpdater.patch, SOLR-269 +139-ModifiableDocumentUpdateProcessor.patch It would be nice to be able to update some fields on a document without having to insert the entire document. Given the way lucene is structured, (for now) one can only modify stored fields. While we are at it, we can support incrementing an existing value - I think this only makes sense for numbers. for background, see: http://www.nabble.com/loading-many-documents-by-ID- tf3145666.html#a8722293 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-333) distributiondump.jsp gets the path to logs wrong
[ https://issues.apache.org/jira/browse/SOLR-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Au updated SOLR-333: - Attachment: solr-333.patch It turns out to be a very simple change in the JSP as it already has obtained solr home from solr.core.Config. Attached in the patch. I will apply it tomorrow if no one objects. distributiondump.jsp gets the path to logs wrong Key: SOLR-333 URL: https://issues.apache.org/jira/browse/SOLR-333 Project: Solr Issue Type: Bug Environment: Tomcat 5.5 Reporter: Ken Prows Assignee: Bill Au Fix For: 1.2 Attachments: solr-333.patch I can't seem to get the Distribution Info page to work. I think it is because I have a custom path to solr. My path to the logs directory looks like this: /apps/search/solr/catalog/logs (The base url to solr ends up being http://domain.com/catalog) I have to create my path like this in order to have multiple instances of solr running in the same container. distributiondump.jsp is creating the path to the status file using: cwd + /solr/logs/snapshot.current, which ends up being wrong. Would it be possible to make it use a rootdir variable like: rootdir + /logs/snapshot.current? If there is no way to determine the rootdir, perhaps it could be added to solrconfig.xml (or at least let it be overridden there.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
