[
https://issues.apache.org/jira/browse/SOLR-17975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-17975:
--------------------------------------
Attachment: SOLR-17975.patch
Assignee: Chris M. Hostetter
Status: Open (was: Open)
{quote}Since the query time logic will likely (almost certainly?) need a pure
string format for the float[][] input that it can parse – one option is ... let
the rest of Solr/SolrJ deal with the field values of some new
o.a.s.schema.LateInteractionFieldType as "specially formatted Strings"
{quote}
I'm attaching an initial patch that goes this route.
We can always revisit the question of how clients send/recieve the
{{float[][]}} in the documents, but this shows what the "query function"
could/would look like (and currently uses the same representation for indexing).
As with any new FieldType impl that doesn't "fit the mold "of existing
string/number field types, there may be bugs I haven't found – but 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, SolrDocumentFetcher isn't consistently using those methods in all
useDocValuesAsStored situations ... it's got it's own special case statement
with specialized conditionals that would need to be rethought/refactored to
ensure the BINARY DocValues for this new field type (and any other similar
field types) can be reconstituted back into _whatever_ external representation
we want for the {{float[][]}} values.
> Add support for Lucene's LateInteractionField
> ---------------------------------------------
>
> Key: SOLR-17975
> URL: https://issues.apache.org/jira/browse/SOLR-17975
> Project: Solr
> Issue Type: New Feature
> 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]
