Lalit Kumar Bhasin

This was discussed in community meeting. To summarize the discussion: 1. It is possible for user to merge the custom resource attributes to the SDK provided and pass it to...

I agree, this can be documented better, with example. Perhaps we can use this issue to track improving it.

old issue, so closing. The CI is successful currently.

Thanks @utpilla. Very good points. Regarding 1 and 2, it's worth testing if the tracing library allows emitting attributes with None (encapsulated within Options) value or values with iterators to...

> Why is there both Value and AnyValue? This is discussed here - https://github.com/open-telemetry/opentelemetry-rust/issues/1253#issuecomment-1717133746

> I also agree with the points in the first message: Null should be fully support and the implementation should better manage its guarantees. Rust doesn't have a built-in `null`...

@ThomsonTan - can we move this as separate processor (say) `BatchLogProcessorWithOwnThread` and keeping existing `BatchLogProcessor`, and then once we validate all the scenarios, we can rename it back - as...

Also, can you please fix the merge conflicts - would be good to review on that :),

Also @ThomsonTan - Can you test it with all OTLP scenarios - OTLP HTTP (hyper, reqwest, reqwest-blocing) and OTLP gRPC, and share the result. Thanks.

Also, adding this to v0.28 milestone.