Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement]support object storage that not compatible with s3 (backport #41123) #41612

Merged
merged 2 commits into from Feb 26, 2024

Conversation

zombee0
Copy link
Contributor

@zombee0 zombee0 commented Feb 26, 2024

Why I'm doing:

What I'm doing:

cp #41123
Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.2
    • 3.1
    • 3.0
    • 2.5

Signed-off-by: zombee0 <ewang2027@gmail.com>
Signed-off-by: zombee0 <ewang2027@gmail.com>
@zombee0 zombee0 changed the title [WIP] be s3 compatibility [Enhancement]support object storage that not compatible with s3 (backport #41123) Feb 26, 2024
@Youngwb Youngwb merged commit 284ba30 into StarRocks:branch-3.1 Feb 26, 2024
49 of 55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants