Skip to content

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #56843

### What problem does this PR solve?

We are deprecating LakeSoul external catalog support in the current
Doris release due to several critical issues:

**Design Flaws** – The current driver management design causes conflicts
with other components, leading to instability and increased maintenance
complexity.

**Security Vulnerabilities** – LakeSoul dependencies contain multiple
CVE-reported vulnerabilities, posing security risks.

**Lack of Maintenance** – The LakeSoul catalog integration in Doris
lacks active maintainers and has not received timely updates.

**No User Adoption** – No user feedback or usage requests have been
received, indicating that the feature has not been used in practice.

Given these factors, maintaining this integration introduces unnecessary
security and maintenance burdens without providing tangible value to
users. Therefore, we have decided to **deprecate** LakeSoul catalog
support in this release:

- All LakeSoul-related code has been marked as `@Deprecated` and will be
kept for backward compatibility
- LakeSoul dependencies (including `lakesoul-io-java`, `postgresql`, and
`scala-library`) have been changed to `provided` scope and will not be
packaged in the release
  - Comment `extensions_modules+=("lakesoul-scanner")` in build.sh

Users who still need LakeSoul support can manually enable it by
modifying Maven configurations. However, we strongly recommend migrating
to alternative catalog solutions. Complete removal of LakeSoul support
is planned for a future release.
@github-actions github-actions bot requested a review from yiguolei as a code owner October 17, 2025 23:58
@hello-stephen
Copy link
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Oct 17, 2025
@hello-stephen
Copy link
Contributor

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@yiguolei yiguolei merged commit bb7b562 into branch-4.0 Oct 18, 2025
23 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-56843-branch-4.0 branch October 18, 2025 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants