Ok, finally got some time to dig into this and you were exactly right. I
simply needed to provide the offset of the payload when scoring it in my
custom similarity.
EG: PayloadHelper.decodeFloat(payload.bytes, payload.offset);
Simple! Thanks for the help.
Jim
--
View this message in context:
On Wed, Mar 27, 2013 at 9:04 PM, Paul Bell wrote:
> Thanks Adrien.
>
> I've scraped together a simple program in the Lucene 4.2 idiom (see below).
> Does this illustrate what you meant by your last sentence?
>
> The code adds/indexes 5 documents all of whose content is identical, but
> whose 'id'
Thanks Adrien.
I've scraped together a simple program in the Lucene 4.2 idiom (see below).
Does this illustrate what you meant by your last sentence?
The code adds/indexes 5 documents all of whose content is identical, but
whose 'id' field is unique ("v1" through "v5"). It then queries the 'id'
f
Hi Paul,
On Wed, Mar 27, 2013 at 1:58 PM, Paul Bell wrote:
> As to the ideas raised in the links you pointed me to: the first link shows
> the instantiation of a Term object via
>
>writer.UpdateDocument(new Term("IDField", *id*), doc);
>
> yet in the 4.2.0 docs I see no Term constructor that
Thanks, Sashidar.
In response to your "P.S.", you raise a reasonable point. I agree that it
would probably be a vain undertaking to try to keep the search index in
real-time sync with the database. I suppose this relationship is rooted in
something like the application's SLA, e.g., "query results
Hi Ian,
Thanks once again.
I think the problem is mainly due to index being on NFS.
Currently, there are other process running on the server with heavy
disk IO on NFS.
This has resulted in sharing of disk IO.
Thanks,
Ashwin
On Fri, Mar 22, 2013 at 5:45 AM, Ian Lea wrote:
> I did ask if there wa
Hi Yann-Erwan,
Thank you for the detailed reply. Your idea seems reasonable. I will
give it a try for out environment settings.
Wei
On Tue, Mar 26, 2013 at 5:22 PM, Yann-Erwan Perio wrote:
> On Sun, Mar 24, 2013 at 10:46 AM, Wei Wang wrote:
>
> Hi,
>
>> For example, assume we have fields F1 an
