>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3570299. --> Reported by: [scott_euser](https://www.drupal.org/user/3267594) Related to !35 !21 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Its possible to have a mix of Search API processors on the parent query (e.g. solr/database) but also on the child. In the scenario that intent is determined (e.g. <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai_search/issues/3570274" title="Status: Closed (fixed)">#3570274: Boost plugins should allow skipping</a></span>) that intent would be determined at the parent query level, but the intentions may need to be passed to the AI Search query object.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Attempt to pass information between the two queries</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Pass the parent query options down to the child AI Search Query</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>