Comment 3 for bug 1942467

Hi Mike,

Thanks for looking at this! Your suggestion did work on my concerto test system.

After increasing the weight on the virtual mapping for ISBN, and restarting services, my searches worked as expected. Keyword searches on 749998216 and 0307913163 (examples from the original but report) retrieved the record as I would expect given the virtual mappings.

Here's what I did on my concerto system:

Baseline weight of the sync field:

SELECT weight
FROM config.metabib_field
where name = 'blob'

weight: 1

ISBN virtual mapping id and weight:

SELECT map.id, map.weight
FROM config.metabib_field_virtual_map map
JOIN config.metabib_field field ON map.real = field.id
WHERE field.name = 'isbn'

id: 13
weight: 1

Confirm that a keyword search on 0307913163 gets no hits

Change the weight on the virtual map to 2:

UPDATE config.metabib_field_virtual_map
SET weight = 2
WHERE id = 13

Restart services

Perform a keyword search on 0307913163 using cache killer, for example:

0307913163 -lmlsflk;ijfs

The search retrieves the record as expected.

This is great news, and likely gives us a workaround, but can the optimization be tweaked to allow the virtual indexes to work without adjusting weights?