one concept i think we can remove from next gen solr-ruby's....
autocommit. the solr side can handle that configuration, and it's
often not really even a good idea to commit until your job is done, as
we now have rollback features and solr really should be able to handle
lots of uncommitted docs.
thoughts? maybe i'm wrong and having a client api sending commits
periodically in a big batch is warranted.
Erik
On Dec 16, 2008, at 11:52 PM, Matt Mitchell wrote:
I've been re-writing/factoring the solr ruby gem -- and the source
code can
be found here:
http://github.com/mwmitchell/solr/tree/master
The current version is 0.5.1 and can be installed by running:
gem sources -a http://gems.github.com
sudo gem install mwmitchell-solr
More docs coming, but for the nitty gritty, have a look at some of
the tests
if needed.
If you use solr-ruby at all, please have a look. I would love to
hear from
some of the ruby folks out there!
Cheers,
Matt
