Extra check that VDB has correctly filtered for existing vectors lookup
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3576572. -->
Reported by: [scott_euser](https://www.drupal.org/user/3267594)
Related to !15 !14
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>If VDB provider fails to filter correctly by Node ID, it can return existing vectors for other content items, making the related content completely irrelevant. Double check that the returned search api results are actually the ones requested.</p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<p>Milvus 1.1.x earlier releases had a bug prior <a href="https://git.drupalcode.org/project/ai_vdb_provider_milvus/-/commit/a944adc96164db41a2e80613485929faf8649926">to this commit</a> which was a backport from that corresponding fix in 2.x</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Check result has matching drupal entity ID</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<p>MR</p>
<h3 id="summary-ui-changes">User interface changes</h3>
<p>N/A</p>
<h3 id="summary-api-changes">API changes</h3>
<p>N/A</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>N/A</p>
issue