Jaeger Exporter : Mapping OTel Resource into Jaeger Process

[lalitb]

Current Jaeger Thrift exporter implementation maps service_name from resource attributes into Jaeger process. The rest of the resource attributes also need to be mapped to the Jaeger Process as mentioned in specs:
https://github.com/open-telemetry/opentelemetry-specification/blob/v1.0.0/specification/trace/sdk_exporters/jaeger.md#resource

This is how it is handled by otel-go implementation: https://github.com/open-telemetry/opentelemetry-go/blob/d3b1280863f421bba9656543296b71c133f1ba13/exporters/trace/jaeger/jaeger.go#L346

[anshulkumar19]

@lalitb Can you assign this to me?

[lalitb]

@anshulkumar19 - Do you want me to pick this up, as we need to fix this for GA.

[anshulkumar19]

@anshulkumar19 - Do you want me to pick this up, as we need to fix this for GA.

Sorry @lalitb for coming late on this, please pick this up as needed for GA and I am little bit occupied with other things.

[ThomsonTan]

@anshulkumar19 no problem. I'll take it.