Hi folks,
I have a DelegatingCollector installed via a PostFilter (kind of like an
AnalyticsQuery) that needs the document score to a) add to a collection of
score-based stats, and b) decide whether to keep the document based on the
score.
If I keep the document, I call super.collect() (where sup
bably not the best answer, but my gut says that even if you
> changed your document to a simple 2 fields and have one as your metric and
> the other as a TrieDateField you would speed up and simplify your date
> range queries.
>
>
> --
> Jared Whiklo
>
>
>
> On 2014-
Hi folks,
My application requires tracking a daily performance metric for all
documents. I start tracking for an 18 month window from the time a doc is
indexed, so each doc will have ~548 of these fields. I have in my schema a
dynamic field to capture this requirement:
Example:
metric_2014_06_
Hi folks,
Using Solr 4.6.0 in a cloud configuration, I'm developing a SearchComponent
that generates a custom score for each document. Its operational flow
looks like this:
1. The score is derived from an analysis of search results coming out of
the QueryComponent. Therefore, the component is i
