Oh, drat, I left out an 's'. I got it now.
On Tue, Oct 8, 2013 at 7:40 PM, Benson Margulies wrote:
> Mike, where do I find DirectPostingFormat?
>
>
> On Tue, Oct 8, 2013 at 5:50 PM, Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> DirectPostingsFormat?
>>
>> It stores all terms + po
Mike, where do I find DirectPostingFormat?
On Tue, Oct 8, 2013 at 5:50 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> DirectPostingsFormat?
>
> It stores all terms + postings as simple java arrays, uncompressed.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, O
DirectPostingsFormat?
It stores all terms + postings as simple java arrays, uncompressed.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Oct 8, 2013 at 5:45 PM, Benson Margulies wrote:
> Consider a Lucene index consisting of 10m documents with a total disk
> footprint of 3G. Consider
Consider a Lucene index consisting of 10m documents with a total disk
footprint of 3G. Consider an application that treats this index as
read-only, and runs very complex queries over it. Queries with many terms,
some of them 'fuzzy' and 'should' terms and a dismax. And, finally,
consider doing all
There are some Analyzer methods you might want to override (initReader
for inserting a CharFilter, stuff about gaps), but if you don't need
that, it seems to be mostly about packaging neatly, as you say.
-Mike
On 10/8/13 10:30 AM, Benson Margulies wrote:
Is there some advice around about when
Hi James,
The spatial module in v4 is completely different than the one in v3. It
would be good for you to review the new API rather then looking for a 1-1
equivalent to a class that existed in v3. Take a look at the top level
javadocs for the spatial module, and in particular look at
SpatialExa
Is there some advice around about when it's appropriate to create an
Analyzer class, as opposed to just Tokenizer and TokenFilter classes?
The advantage of the constituent elements is that they allow the
consuming application to add more filters. The only disadvantage I see
is that the following i
When you open this index for searching, how much heap do you give it?
In general, you should give IndexWriter the same heap size, since
during merge it will need to open N readers at once, and if you have
RAM resident doc values fields, those need enough heap space.
Also, the default DocValuesForm
Hi,
On Mon, Oct 7, 2013 at 9:31 PM, Rose, Stuart J wrote:
> Is there an optimal way to access many document TermVectors (in the same
> chunk) consecutively when using the LZ4 termvector compression?
>
> I'm curious to know whether all TermVectors in a single compressed chunk are
> decompressed
