[ 
https://issues.apache.org/jira/browse/SOLR-17975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044394#comment-18044394
 ] 

Alessandro Benedetti commented on SOLR-17975:
---------------------------------------------

Also, whenever adding a JiraIssue that relates with Vector Search, please add 
the related component, this makes the issue visible on the vector search board: 
[https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=633]
That's used for the vector search development group (a meetup happens monthly) 

> 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]

Reply via email to