[
https://issues.apache.org/jira/browse/SOLR-17975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050485#comment-18050485
]
Chris M. Hostetter commented on SOLR-17975:
-------------------------------------------
[~abenedetti] - I've got a straw man patch in SOLR-18033 that (when applied to
the branch for SOLR-17975) allows all the existing TestLateInteractionVectors
asserts to pass, and should be flexible enough to enable us to use whatever
(external) representation we want for the (internal) binary values.
Please take a look and let me know what you think
> 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]
