github-actions[bot] commented on PR #5379:
URL: https://github.com/apache/solr/pull/5379#issuecomment-7077869992

   **Automated PR readiness judgements** (LLM-generated; may be wrong; not 
updated on later pushes).
   
   Maintainer edits are unavailable for organisation-owned forks.
   
   - ✅ [Jira issue in 
title](https://github.com/apache/solr/blob/main/CONTRIBUTING.md): already 
present
   - ⚠️ 
[Changelog](https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc#_changelog_types_reference)
 **— missing** (suggest type: fixed): The PR fixes a bug where atomic updates 
(set, add, remove, add-distinct) on multivalued dense 
vector fields produced incorrect results, which is a user-visible data 
integrity issue.​
   - ⚠️ [Reference Guide 
update](https://github.com/apache/solr/tree/main/solr/solr-ref-guide) **— 
probably not needed**: The change fixes the behavior of existing atomic update 
operations on dense vectors to work correctly&#59; it does not introduce new 
parameters, configuration options, or API endpoints that require 
documentation.​
   - ✅ [Upgrade 
notes](https://github.com/apache/solr/tree/main/solr/solr-ref-guide/modules/upgrade-notes/pages):
 not needed <!-- This is a bug fix that corrects incorrect behavior&#59; it 
does not remove or rename any APIs&#44; parameters&#44; or configuration 
elements&#44; nor does it change defaults in a way that requires user 
action&#46;​ -->
   - ✅ Tests: included <!-- The PR modifies complex production logic in 
AtomicUpdateDocumentMerger and NestedUpdateProcessorFactory to handle 
multivalued dense vectors&#44; which warrants new or updated tests to verify 
the fix&#46;​ -->
   
   <!-- Assessed commit b48a6caf2e9274ca21e1822224da0001d86126c1 -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to