[Question] SessionIdRatioBasedSampler defined but not used in the SDK

Currently, the SDK does not use the defined SessionIdRatioBasedSampler.

I also came across a different implementation of this sampler in splunk-otel-android code - UInt32QuadXorTraceIdRatioSampler - where it converts the hex session id to long in a specific way so it aligns with the computation in JS RUM SDK.

Looks like opentelemetry-java SDK implementation which the SessionIdRatioBasedSampler depends on also converts hex to long but in a different way (not the same as JS RUM SDK).

Was wondering if this is a blocker for not yet using the defined SessionIdRatioBasedSampler in this SDK? Do we need to propose an issue in the opentelemetry-java SDK to get a JS like calculation added, perhaps that is used in an alternate new sampler that we can then depend on instead of TraceIdRatioBasedSampler?

Another blocker could be Logs don't provide an options to add Sampler like how the Trace does.

Start with core/src/main/java/io/opentelemetry/android/SessionIdRatioBasedSampler.java and compare its conversion with the linked Java, Splunk, and JS sampler implementations. Check whether the SDK's Logs API exposes sampler options. Done means establishing and testing a decided path for using the sampler, or documenting the confirmed blocker.