I am indexing persons that has the usual fields name, address etc.
I need to keep track of which name and addresses are active now and
which ones are old.
I do that by having a two sets of fields e.g.: current_name and old_name
When I search for a person and I search in just the current fields
ran
I forgot to mention that I never have to search in the old_name alone.
I either search in current_name alone or current_name OR old_name.
Realizing that, lead me to the simple solution of duplicating whatever
I put into a current field into the old fields too. So the info in the
fields with old_ p
Hi,
I can see that this has been up before, but I still hope to get some
advice based on my specific environment.
I index some documents with 26 fields in them. The size 1 indexed
documents is 4mb, so it shouldn't be overwhelming amounts of data
compared to what I have heard lucene can do.
N
dk
> 1.3 is pretty ancient - can you use 1.5?
>
> I'd try it with a larger heap size, and then look for leaks in your
> code. Maybe run the load program without the lucene calls and see if
> it still fails.
>
>
> --
> Ian.
>
>
> On 13/07/05, Lasse L <[
I am using the queryparser to search for names.
If I search for: john j*
I'd expect to get everybody called john j-something. john johnson,
john joe doe ect.
Instead I just all john and joes. In many of the hits there is not
second j-word.
Is there a way to get lucene to get "satisfied" after mat
However leaving the name as a single term would make me miss a hit
like "john doe johnson" -- which is unacceptable.
Is there a way I could boost the queryresults that match better?
Will the score rise if a query is matched more than once? "j*" in
"john johnson"?
It wouldn't matter that much that
