[INLONG-7459][Sort] Fix dirty data can't be archived to s3 for hbase - #7462
Merged
Conversation
gong
approved these changes
Feb 28, 2023
dockerzhang
approved these changes
Feb 28, 2023
Yizhou-Yang
pushed a commit
to Yizhou-Yang/inlong-yyz
that referenced
this pull request
May 30, 2023
…pache#7462) (cherry picked from commit efe5bf2)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare a Pull Request
(Change the title refer to the following example)
(The following XYZ should be replaced by the actual GitHub Issue number)
Motivation
Fix dirty data can't be archived to s3 for hbase
Modifications
Change the third-party dependencies package from commons-lang to commons-lang3 for class 'org.apache.commons.lang3.StringEscapeUtils'
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:)
Documentation