On Tue, Jul 27, 2010 at 12:06 PM, Alexander vom Berg wrote:
>> However, this may not be a fair performance test since with 'cp'
>> presumably the IO system may have optimized how the files are
>> allocated to blocks on disk. Ie, you'll get a different allocation
>> than had Lucene directly opened
Hello Mike,
Am 27.07.2010 14:38, schrieb Michael McCandless:
On Tue, Jul 27, 2010 at 7:58 AM, Alexander vom Berg wrote:
Hello Mike,
thanks for your answer!
I am currently working with Lucene 3.0.1 and except the .tii - file all
other descriptions are comprehensible.
The idea behind the ti
On Tue, Jul 27, 2010 at 7:58 AM, Alexander vom Berg wrote:
> Hello Mike,
>
> thanks for your answer!
> I am currently working with Lucene 3.0.1 and except the .tii - file all
> other descriptions are comprehensible.
> The idea behind the tii/tis file structure is for faster retrieving the
> correc
Hello Mike,
thanks for your answer!
I am currently working with Lucene 3.0.1 and except the .tii - file all
other descriptions are comprehensible.
The idea behind the tii/tis file structure is for faster retrieving the
correct terms.
At first I lookup in memory (tii-file) and take the most near
Best explanation is the source code itself -- it should be correct ;)
Look at how SegmentTermsEnum.next is implemented, pre-flex. (If
you're looking @ flex (= trunk), then the format is slightly different
and not yet correctly documented (issue is open)).
Yes vInt/vLong are the same, except vLon
