Hi Michael,
The use case is to handle index updates along with its vector field
without resending the vector in change data every time. The change data will
consist of only “updated_field(s):value(s)” wherein I will read the vector
value from Index to update the document.
Thanks,
Uthra
Hello,
This recent issue is exactly referring to what you need - you may want to
continue the discussion there, perhaps
ask the commenter to make the code public on github for experiments?
https://github.com/apache/lucene/issues/13065
Dawid
On Sun, Feb 11, 2024 at 8:42 AM _ SATNAM wrote:
>
thanks for explainig, Uthra!
IIUC the text / data for which the vector was originally generated was
not changed, only some other data (e.g. meta data) which is also part of
the Lucene document, right?
So, if you want to update the other data within the Lucene document, you
first retrieve the
Hi,
> Using LeafReader’s API to read vector. Here the Random accessing of
documents is very slow.
Is it possible that you are creating a new VectorValues instance for every
doc whose value you want to look up?
Ideally, you should sort your docids and then advance to them one by one,
or call
