[
https://issues.apache.org/jira/browse/SOLR-17975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046029#comment-18046029
]
Chris M. Hostetter commented on SOLR-17975:
-------------------------------------------
{quote}what about opening a pull request (even a draft is ok).
{quote}
I personally find the Github specific workflow of PRs incredibly limiting in
how people can collaborate, but i'll go ahead and make a {{jira/SOLR-17975}}
branch.
you're welcome to commit there and/or make a PR from that branch if you find it
useful to you.
----
{quote}... the main issue i *HAVE* found is that even though FieldType has
method(s) for converting internal BytesRef's into something type specific that
can be returned to the client, ...
{quote}
I tried to tackle this in SOLR-18033 , which includes a fix for the
{{useDocValuesAsStored=true}} situation (just for {{BINARY}} docValues), but
exposed a similar (inverse) issue with the {{stored=true}} when dealing with
stored binaryValue fields.
See that issue for full context, but ultimately the "safest" thing (from a
backcompat standpoint) for dealing with a new LateInteractionVectorField that
we intend to include in solr-core is probably going to just be more hardcoded
special case logic of in the affected code paths.
> Add support for Lucene's LateInteractionField
> ---------------------------------------------
>
> Key: SOLR-17975
> URL: https://issues.apache.org/jira/browse/SOLR-17975
> Project: Solr
> Issue Type: New Feature
> Components: vector-search
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-17975.patch
>
>
> Lucene 10.3 added a
> [LateInteractionField.|https://lucene.apache.org/core/10_3_1/core/org/apache/lucene/document/LateInteractionField.html].
> Basic support for this in Solr would be a new {{FieldType}} and some
> associated {{QParser}} support to be able to use tose fields in conjunction
> iwth Lucene's {{TestRescoreTopNQuery}} and/or {{LateInteractionRescorer}}
> (and/or {{LateInteractionFloatValuesSource}} + {{DoubleValuesSourceRescorer}}
> -- see SOLR-17951)
> BUT! ... the most complex part of figuring out ow to support
> {{LateInteractionField}} in Solr is going to come down to what the field
> values should look like when adding/updating docs containing this field --
> and what the query input should look like -- given that the field values are
> "multi-dimensional array of floats"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
