[
https://issues.apache.org/jira/browse/SOLR-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-111.
-------------------------------
Resolution: Fixed
Assignee: Erik Hatcher
Applied, except tweaked autocommit to off by default. Good stuff, Ed!
> new repsonse classes and connection enhancements
> ------------------------------------------------
>
> Key: SOLR-111
> URL: https://issues.apache.org/jira/browse/SOLR-111
> Project: Solr
> Issue Type: Improvement
> Components: clients - ruby - flare
> Environment: Darwin frizz 8.8.1 Darwin Kernel Version 8.8.1: Mon Sep
> 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386 i386 i386
> Reporter: Ed Summers
> Assigned To: Erik Hatcher
> Attachments: response_connection_changes.diff,
> response_connection_changes.diff
>
>
> Similar to Solr::Request::* a Solr::Response::* hierarchy was created as well
> as a Solr::Response::Base which has a factory method for creating the
> appropriate response based on the request type and the raw response.
> Also added delete(), delete_by_query(), add(), update() and query() methods
> to Solr::Connection. This gets a bit closer to a DSL type of syntax which
> doesn't require the user to know the inner workings of solrb. I adjusted
> README accordingly.
> Solr::Connection also operates with autocommit turned *on* so commit()
> messages are not required when doing add(), update(), delete() calls. It can
> be turned off if the user doesn't want they extra http traffic.
> Added the ability to iterate over search results. Although need to add the
> ability to iterate over complete results, fetching data behind the scenes as
> necessary.
> Unit tests have been added and functional tests improved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira