Update hybrid search pipeline.

[mathewjordan]

I'm unsure if I am doing this correctly. The NEXT_PUBLIC_OPENSEARCH_PIPELINE was always undefined and I'm not sure what it should have been leaning on for me so I have rewritten this a bit.

if (!!body?.query?.hybrid) {
  requestUrl.searchParams.append(
    "search_pipeline",
    "dc-v2-work-pipeline"
  );
}

Seems to do the trick... is there a reason we would want this to be an environmental variable?

[mbklein]

👍🏻 The pipeline will fail (with an error) if applied to a non-hybrid query, so this is the correct and necessary way to do it. I thought of something else last night, but it's an improvement for another day.

[adamjarling]

@mathewjordan @mbklein The pipeline variable NEXT_PUBLIC_OPENSEARCH_PIPELINE should be pulling through ok. I updated this a few weeks back in https://github.com/nulib/miscellany, and I thought I posted in Slack for folks to pull the latest miscellany (but apparently I just messaged Karen for some reason). Sorry 😀

https://github.com/nulib/miscellany/blob/479111a2f17ed45fe2e975e256a0d61a0c28ebee/secrets/dev_environment.sh#L36

[mbklein]

@adamjarling Yeah, configuring it using a variable is a good plan, but it's also important only to use it for hybrid queries. It'll break regular ones.

[adamjarling]

@mbklein Yep, that should be how's it wired up, to only send ?search_pipeline if doing hybrid (AI) querying.

[mathewjordan]

Oh, well, we need to revert things. Ahhh.