little faceting speedup
FYI, anyone using faceting should get a little bump in speed after tonight's build. Doing facet.field queries where the number of terms in the field is very large can still be slow though (unless you have enough memory to actually cache a DocSet for every term). -Yonik On 9/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: --- incubator/solr/trunk/CHANGES.txt (original) +++ incubator/solr/trunk/CHANGES.txt Wed Sep 13 13:55:46 2006 + 5. Optimized getDocSet() for term queries resulting in a 36% speedup of facet.field +queries where DocSets aren't cached (for example, if the number of terms in the field +is larger than the filter cache.) (yonik) (I accidentally sent this first to solr-commits: it looks like gmail is ignoring the reply-to field)
Re: [jira] Commented: (SOLR-30) Java client code for performing searches against a Solr instance
: Perhaps we should add support for the sort param to the standard : request handler. +1 -Hoss
Re: micro-patch: add description to test-reports build target
: Since I was already there, I went ahead and committed a description : for test-reports, and javadoc. But the "junit" target doesn't need a : description since "test" is the main testing entry point. actually, something i've been thinking would be nice is if there was a way to run the tests and generate the test reports with one target -- even if the tests fail. (not currenlty possible because of the fast fail behavior of ant) Since "test" is currently just a shell arround "junit" what if we replace the dependency on the "junit" target with an , preserve the property of tests.failed, then "test-reports" and fail based on tests.failed ? people who don't wnat test reports can just run "ant junit" (which we would want to add a description to in this case) That should all work fairly well right? : : Erik : : : On Sep 13, 2006, at 9:24 AM, Bertrand Delacretaz wrote: : : > On 9/13/06, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: : > : >> ...I think the test-reports target is worth a description... : > : > Just found out that the junit target also has no description, so it : > might be on purpose. : > : > Still, I think making people aware of automated tests is a Good Thing, : > so I'd add descriptions to both. : > : > -Bertrand : -Hoss
Re: Re: micro-patch: add description to test-reports build target
On 9/13/06, Erik Hatcher <[EMAIL PROTECTED]> wrote: ... ant -p -verbose.. Didin't know that, thanks. And thanks for the patch as well. -Bertrand
Re: micro-patch: add description to test-reports build target
p.s. You can see all targets, even ones without descriptions by doing this: ant -p -verbose On Sep 13, 2006, at 9:21 AM, Bertrand Delacretaz wrote: Hi Solr gang, Currently, build.xml says: I think the test-reports target is worth a description: (I found out when starting to write a patch for these reports ;-) -Bertrand
Re: micro-patch: add description to test-reports build target
Bertrand, Since I was already there, I went ahead and committed a description for test-reports, and javadoc. But the "junit" target doesn't need a description since "test" is the main testing entry point. Erik On Sep 13, 2006, at 9:24 AM, Bertrand Delacretaz wrote: On 9/13/06, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: ...I think the test-reports target is worth a description... Just found out that the junit target also has no description, so it might be on purpose. Still, I think making people aware of automated tests is a Good Thing, so I'd add descriptions to both. -Bertrand
Re: micro-patch: add description to test-reports build target
On 9/13/06, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: ...I think the test-reports target is worth a description... Just found out that the junit target also has no description, so it might be on purpose. Still, I think making people aware of automated tests is a Good Thing, so I'd add descriptions to both. -Bertrand
micro-patch: add description to test-reports build target
Hi Solr gang, Currently, build.xml says: I think the test-reports target is worth a description: (I found out when starting to write a patch for these reports ;-) -Bertrand
