doris-flink-connector
Flink Connector for Apache Doris
Runssource: GitHubhomepageJavaApache-2.0commit b5f65fb98efb
Java, Apache-2.0 licensed. The project labels itself: apache, connector, data warehousing, dbms, doris, flink, mpp and olap.
doris-flink-connector runs. An Argusic agent installed it in 11 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
JDK 17 is installed, Maven wrapper works, the Flink Doris Connector builds successfully, and all 442 unit tests across the base and flink2 modules pass with 0 failures.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96.7 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No JDK 17 installed in container1 minute
- flink2 module could not resolve flink-doris-connector-base as sibling dependency1 minute
- No standalone Maven installed
- Install time
- 11 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- mvnw test -Pflink2 -DfailIfNoTests=false on flink-doris-connector/pom.xml returned BUILD SUCCESS with 442 tests run (422 + 20), 0 failures, 0 errors
- Model tokens used
- 72,491
- Exact commit tested
- b5f65fb98efb
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
1. Installed **JDK 17** (Temurin 17.0.20.1) — no JDK was present initially. 2. Used the bundled `mvnw` Maven wrapper — no standalone Maven was installed. 3. Built the Flink 2.2 connector with `./mvnw clean package -Pflink2` → **BUILD SUCCESS**. 4. Ran tests across all modules with `./mvnw test -Pflink2 -DfailIfNoTests=false` → **BUILD SUCCESS… **Test results:** - **flink-doris-connector-base**: 422 tests, 0 failures, 0 errors, 1 skipped - **flink-doris-connector-flink2**: 20 tests, 0 failures, 0 errors, 0 skipped - **flink-doris-connector-it**: 0 tests (container-based IT tests that require a live Doris cluster… **Errors encountered and fixed:** 1. No JDK found → downloaded and installed Temurin JDK 17 (0 fix time). 2. No standalone Maven → used project's bundled `mvnw` wrapper (0 fix time). 3. flink2 sibling dependency resolution → used `-am` (also-make) flag and installed parent/base POM…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 11 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/doris-flink-connector)Questions
- Does doris-flink-connector run?
- Yes. doris-flink-connector runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test doris-flink-connector?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b5f65fb98efb. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test doris-flink-connector?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does doris-flink-connector take to install?
- 11 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does doris-flink-connector need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing doris-flink-connector?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for doris-flink-connector?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.