qy-liuhuo opened a new pull request, #11423:
URL: https://github.com/apache/inlong/pull/11423

   …Logger
   
   <!-- Prepare a Pull Request
   Change the title of pull request refer to the following example:
     [INLONG-XYZ][Component] Title of the pull request 
   -->
   
   <!-- Specify the issue this pull request going to fix.
   The following *XYZ* should be replaced by the actual [GitHub 
Issue](https://github.com/apache/inlong/issues) number)-->
   
   Fixes #11422 
   
   ### Motivation
   
   
   `OpenTelemetryLogger` adds some opentelemetry-related maven dependency 
packages to the `sort-connector-base` module.
   
   However, these packages have some redundancy and conflicts with inlong's 
original opentelemetry packages.
   
   This results in unit tests failing when integrating some 
connectors(https://github.com/apache/inlong/pull/11351#issuecomment-2425694927)
   
   ### Modifications
   
   Remove some opentelemetry dependencys in inlong-sort/sort-flink/base/pom.xml
   
   ### Verifying this change
   
   *(Please pick either of the following options)*
   
   - [ ] This change is a trivial rework/code cleanup without any test coverage.
   
   - [ ] This change is already covered by existing tests, such as:
     *(please describe tests)*
   
   - [ ] This change added tests and can be verified as follows:
   
     *(example:)*
     - *Added integration tests for end-to-end deployment with large payloads 
(10MB)*
     - *Extended integration test for recovery after broker failure*
   
   ### Documentation
   
     - Does this pull request introduce a new feature? (yes / no)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ not documented)
     - If a feature is not applicable for documentation, explain why?
     - If a feature is not documented yet in this PR, please create a follow-up 
issue for adding the documentation
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to