> SearchComponent is the class I was missing. Looks like if I can
provide an
> entirely new implementation of that it will be a lot cleaner than the
hack I
> had been using in 1.2 over top of facets. What I'm doing is implementing
> some aggregation functions like avg() and sum() that SQL has.
I'll shamelessly take this opportunity to plug the long-neglected SOLR-657.
Lars
On Sep 19, 2008, at 3:22 PM, Mark Baird wrote:
SearchComponent is the class I was missing. Looks like if I can
provide an
entirely new implementation of that it will be a lot cleaner than
the hack I
had been using in 1.2 over top of facets.
thats why SearchComponets got added!
It was cr
SearchComponent is the class I was missing. Looks like if I can provide an
entirely new implementation of that it will be a lot cleaner than the hack I
had been using in 1.2 over top of facets. What I'm doing is implementing
some aggregation functions like avg() and sum() that SQL has. This way
Second, I've got some code running in the same JVM as Solr that
does some
stuff like getting the latest timestamp in the index to determine
if we need
to pull an update from our product info database, kicking off an
optimize
every night at 2:00AM, stuff like that. However I take it that
On Sep 19, 2008, at 11:49 AM, Mark Baird wrote:
I was finally given the go-ahead to upgrade from Solr 1.2 to 1.3 in
our
environment here at work now that 1.3 is final. However I'm running
into a
couple problems that I'm having trouble finding solutions to.
First, I've added a class to our
