[fix](fe) Keep CDC end offset consistent with current progress (#65688)

### What problem does this PR solve?

Streaming CDC jobs periodically fetch the source end offset, while a
successful task commits its current offset independently. A task can
advance beyond the previously fetched end offset. The FE previously
converted the offset comparison into a boolean, so it could stop
scheduling but could not distinguish equality from the current offset
being ahead, leaving CurrentOffset greater than EndOffset in job output.

This change preserves the three-way comparison result and advances
EndOffset to CurrentOffset when the fetched end is behind. End-offset
publication is synchronized so an obsolete comparison result cannot
overwrite a newer fetched end. The PostgreSQL latest-offset credential
regression case now waits for the first task to commit the resolved
latest offset before inserting new rows.
4 files changed
tree: 9ced049f1ba5027aadf548a800f323667f386f2d
  1. .claude/
  2. .github/
  3. .idea/
  4. be/
  5. bin/
  6. build-support/
  7. cloud/
  8. common/
  9. conf/
  10. contrib/
  11. dist/
  12. docker/
  13. docs/
  14. extension/
  15. fe/
  16. fe_plugins/
  17. fs_brokers/
  18. gensrc/
  19. hooks/
  20. minidump/
  21. pytest/
  22. regression-test/
  23. samples/
  24. task_executor_simulator/
  25. thirdparty/
  26. tools/
  27. ui/
  28. webroot/
  29. .asf.yaml
  30. .clang-format
  31. .clang-format-ignore
  32. .clang-tidy
  33. .clangd
  34. .dockerignore
  35. .editorconfig
  36. .gitattributes
  37. .gitignore
  38. .gitleaks.toml
  39. .gitmodules
  40. .licenserc.yaml
  41. .rat-excludes
  42. .shellcheckrc
  43. AGENTS.md
  44. build-for-release.sh
  45. build-plugin.sh
  46. build.sh
  47. build_profile.sh
  48. CODE_OF_CONDUCT.md
  49. CONTRIBUTING.md
  50. CONTRIBUTING_CN.md
  51. doap_Doris.rdf
  52. env.sh
  53. generated-source.sh
  54. LICENSE.txt
  55. NOTICE.txt
  56. post-build.sh
  57. README.md
  58. run-be-ut.sh
  59. run-cloud-ut.sh
  60. run-fe-ut.sh
  61. run-fs-env-test.sh
  62. run-regression-test.sh
  63. SECURITY.md
  64. sonar-project.properties
  65. threat-model.md
README.md

🌍 Read this in other language

English • العربية • বাংলা • Deutsch • Español • فارسی • Français • हिन्दी • Bahasa Indonesia • Italiano • 日本語 • 한국어 • Polski • Português • Română • Русский • Slovenščina • ไทย • Türkçe • Українська • Tiếng Việt • 简体中文 • 繁體中文

Apache Doris

License GitHub release Slack EN doc CN doc

Official Website Quick Download


Apache Doris is an open-source, real-time analytics and search database built on MPP architecture. It provides fast SQL analytics, lakehouse query acceleration, and hybrid search across structured, text, and vector data.

Explore the official website for the latest product overview, use cases, ecosystem updates, blogs, and user stories. For version updates, see all release notes.

📈 Use Cases

Use CaseWhat it provides
Customer-Facing AnalyticsShip sub-second interactive analytics to external users.
Data WarehousingBuild one real-time warehouse across business domains.
ObservabilityAnalyze high-throughput logs, events, and metrics with SQL.
Doris for AIUse vector, text, JSON, and structured search in one SQL engine.

🚀 Core Capabilities

Apache Doris is built around three core capabilities. The website is the source of truth for detailed product descriptions and examples.

CapabilityWhat it provides
Real-Time AnalyticsStreaming ingestion, incremental transformation, and sub-second queries under high concurrency.
Lakehouse AnalyticsFast SQL analytics over open table formats such as Iceberg, Delta Lake, and Hudi.
Hybrid SearchSQL-native analytics across JSON, full-text, and vector data for AI and search workloads.

🔌 Ecosystem

Doris sits at the center of the modern data stack. It connects upstream databases, streaming systems, and lakehouse storage with downstream BI, AI, analytics, and observability tools.

For the latest ecosystem coverage, visit the official website and the connection and integration documentation.

👣 Get Started

🧱 Architecture

Apache Doris supports both compute-storage coupled and compute-storage decoupled deployments. In decoupled mode, stateless compute groups run over shared object storage, so you can scale compute on demand and isolate workloads.

Learn more in the deployment guide and deployment mode guide.

📣 Project Updates

ResourceWhat it provides
Community ReportWeekly updates on community activity, merged PRs, contributors, and feature progress.
Roadmap 2026The 2026 planning discussion for AI and hybrid search, query engine, storage, and data lake work.

🧩 Components

Doris provides connectors and tools for common data engineering workflows.

👨‍👩‍👧‍👦 Users

Apache Doris is used in production by thousands of companies worldwide across internet services, finance, retail, logistics, manufacturing, energy, telecommunications, AI, and other industries.

🙌 Contributors

Apache Doris graduated from the Apache Incubator and became an Apache Top-Level Project in June 2022. Thanks to all community contributors who help build Doris.

contrib graph

🌈 Community and Support

💬 Contact Us

🧰 Links

📜 License

Apache License, Version 2.0

Note Some licenses of the third-party dependencies are not compatible with Apache 2.0 License. So you need to disable some Doris features to comply with Apache 2.0 License. For details, refer to the thirdparty/LICENSE.txt