I'm guessing that manipulating the client end, acts_as_solr, is an
easier approach then backporting server side functionality.
Especially as you will have to forward migrate at some point.
Out of curiosity, which version of acts_as_solr are you using? The
plugin has moved homes a couple of times, and I have heard and found
that the version by Mathias Meyer at http://github.com/mattmatt/acts_as_solr/tree/master
is the best. I've used it with 1.4 trunk with no issues, and
Mathias has been very responsive.
Eric
On May 7, 2009, at 10:25 PM, David Shettler wrote:
Foreword: I'm not a java developer :)
OSVDB.org and datalossdb.org make use of solr pretty extensively via
acts_as_solr.
I found myself with a real need for some of the StatsComponent stuff
(mainly the sum feature), so I pulled down a nightly build and played
with it. StatsComponent proved perfect, but... the nightly build
output seems to be different, and thus incompatible with acts_as_solr.
Now, I realize this is more or less an acts_as_solr issue, but...
Is it possible, with some degree of effort (obviously) for me to
essentially port some of the functionality of StatsComponent to 1.3
myself? It's that, or waiting for 1.4 to come out and someone
developing support for it into acts_as_solr, or myself fixing what I
have for acts_as_solr to work with the output. I'm just trying to
gauge the easiest solution :)
Any feedback or suggestions would be grand.
Thanks,
Dave
Open Security Foundation
-----------------------------------------------------
Eric Pugh | Principal | OpenSource Connections, LLC | 434.466.1467 |
http://www.opensourceconnections.com
Free/Busy: http://tinyurl.com/eric-cal
