Daniel Widdis

The 3 solutions really boil down to two use cases: 1. Process tokens on the Extension node(s) - This is a great candidate for a serverless (Lambda, Azure Function, etc.)...

Spent a little bit of time trying to see if anyone had done any Analyzer benchmarking. The [Lucene Nightly Benchmarks](https://home.apache.org/~mikemccand/lucenebench/) give some insight: [Analyzer throughput](https://home.apache.org/~mikemccand/lucenebench/analyzers.html) varies per analyzer, but the...

max/min for numerics - send min and max values. string regex (handles contains, startswith, endswith, all sorts of strings stuff) send the regex string default to other setting (send the...

> I am a big fan of deferring client responsibilities to opensearch-java and taking a runtime dependency on it. Can you be a little more specific what this means, @dblock...

Inevitable question: "Should this be posted on OpenSearch repo to get more eyes on it?" Answer: Yes, I plan to post a more detailed proposal there eventually. This is an...

> 1. Is there a category of fast lived extensions that can be satisfied with a version in which all required state is sent as an opening request, and all...

> @dbwiddis can we close this one out? Nope, I only addressed a portion of the 1st point (and 3 is also a work in progress) but part 2 hasn't...

Key point here is this class of requests are intended to query information on multiple OpenSearch nodes. In the Extension enviornment we don't have all those nodes present so we...

Looks like we can accomplish this by implementing the `replacedRoutes()` extension point: https://github.com/opensearch-project/anomaly-detection/blob/main/src/main/java/org/opensearch/ad/rest/RestAnomalyDetectorJobAction.java#L104 So we should revise rest handler registration to have the full path(s) generated on the SDK side.

> Why would one want to run a plugin and an extension side-by-side on the same REST path? They wouldn't. A single REST path goes to exactly one handler. They...