[jira] [Commented] (SOLR-16807) DenseVectorField breaks catch-all copyFields

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on SOLR-16807:
--------------------------------------------------------

Commit 3f734ab8a5200af4cb8a7d104b1329b81e83c8b9 in solr's branch refs/heads/main from Joel Bernstein
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=3f734ab8a52 ]

SOLR-16807: Update CHANGES.txt


> DenseVectorField breaks catch-all copyFields
> --------------------------------------------
>
>                 Key: SOLR-16807
>                 URL: https://issues.apache.org/jira/browse/SOLR-16807
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 9.0, 9.1, 9.1.1, 9.2.1
>            Reporter: Joel Bernstein
>            Assignee: Joel Bernstein
>            Priority: Major
>              Labels: hybrid-search, vector-based-search
>             Fix For: 9.2.2
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Currently if you setup a copy field with a  * source and a DenseVectorField is present in the schema indexing will fail unless the destination is a DenseVectorField. I think the better behavior is to skip the DenseVectorField during the copy. If we don't do this the * copyfield is simply broken with a DenseVectorField in the index.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org