On Mon, Jan 27, 2014 at 7:23 AM, Benson Margulies <[email protected]> wrote: > On Mon, Jan 27, 2014 at 7:12 AM, Michael McCandless > <[email protected]> wrote: >> Hi Benson, >> >> I use the code from luceneutil >> (https://code.google.com/a/apache-extras.org/p/luceneutil/ ), e.g. I >> run those scripts nightly for the nightly benchmarks: >> http://people.apache.org/~mikemccand/lucenebench >> >> But, that's the Wikipedia corpus, and has no "real" queries, and the >> scripts are quite challenging to get working ... if you have access to >> more "realistic" corpus + queries, even if you can't share it, those >> results are also interesting to share. >> >> I think it would be neat if an app could retroactively pick DirectPF >> at search time, or more generally pass search-time parameters when >> initializing codec components (I think there was a discussion about >> this at some point but I can't remember what the use case was). >> Today, any and all choices must be written into the index and cannot >> be changed at search time, which is somewhat silly/restrictive for >> DirectPF since it can wrap any other PF and act as simply a fast >> "cache" on top of the postings. > > Well, that's where I thought I was starting: an API into the reader > that allows DirectPF to be injected as a wrapper around others. I > haven't had time to follow Rob's bread-crumb trail to see if this is > straightforward by customizing Directory -- thought it occurs to me > that we have many directories, and it would useful to be able to do > this regardless.
I'm not sure how a custom Directory applies here ... maybe Rob can clarify? > I may be able to share a data set, I'll check into that today. Cool! Mike McCandless http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
