David Smiley

Yep I'm confident in it. It's all merged.

I so want this; let's just require Java! But we actually also require "npm" as well, albeit it'll get auto-downloaded. Any way, one thing at a time.

I wish we brainstormed this a bit on the dev list or something prior to you showing up with a PR where there is maybe inertia to continue with it...

I'm sorry for challenging your due diligence on soliciting input. > In short, my thought process was that the more broadly applicable the limit is, the more effective it will...

I've been on vacation lately. I suggested a limit based on the query parser. This suggestion isn't limited to edismax; it'd include some others that users are likely to use....

"user" query parsers: complexphrase, dismax, edismax. All others seem internal to me. We could have an abstract method on QParserPlugin (or QParser) that compels plugin authors to indicate what the...

I love the clear issue report; looks so ready to turn into a test. I confess I am lacking time to debug this but will be a reviewer.

When I run the agent, I provide an Otel properties file with: (an excerpt) ``` otel.metrics.exporter=none otel.logs.exporter=none otel.instrumentation.common.default-enabled=false otel.instrumentation.opentelemetry-api.enabled=true otel.instrumentation.opentelemetry-instrumentation-annotations.enabled=true otel.instrumentation.aws-sdk.enabled=true otel.instrumentation.java-http-client.enabled=true ``` Notice I disable auto-instrumentation by default and...

I'm a little unhappy with keeping TracerConfigurator named this while having it return an OpenTelemetry. Really; we're embracing OpenTelemetry here. I would love to use OpenTelemetry for metrics eventually, to...

I very much want to get back to this for Solr 10... need to maybe reformulate what's happening into multiple things. CC @mlbiscoc