Repository navigation
Bring the Apache Doris demo up to date - #1
Merged
Merged
Conversation
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.
Bringing this 2023 experiment up to date with Doris 4.0.8, the release labelled Stable by Apache Doris, and Kafka 4.1.2.
The default setup now runs one frontend, one backend and Kafka. A separate Compose configuration keeps the three-frontend, three-backend experiment available with its own persistent volumes and three table replicas.
Validation: GitHub Actions passes Compose validation for both configurations, Bash syntax, ShellCheck, fresh Kafka ingestion, and data persistence plus fresh ingestion after recreating containers. The larger cluster is configuration-checked; its runtime smoke test needs a machine with enough memory.
This creates a fresh demo. It does not migrate existing 2.0-alpha data.