ingestr v1.0.53 - StarRocks URI Notes

ingestr v1.0.53 was published on June 30, 2026, with a focused StarRocks documentation update for URI catalog and database handling. The release clarifies how path defaults interact with source-table settings, and it also moves the integration test timeout to 20m. It is not marked as a prerelease.

The full release notes and downloads are on the GitHub release page.

The main user visible change is documentation for StarRocks URI examples where catalog and database live in the path. For teams that generate ingestr commands or config from templates, that detail matters because the same connection string can now carry more of the target shape without relying on memory or local notes.

The release notes do not claim a runtime parser change. They say the docs now show URI examples for catalog and database in the path. Treat that as guidance for how the project wants StarRocks destination strings to be read, not as a new feature that changes execution semantics.

The second StarRocks docs change is the precedence rule. The notes say source-table fields override URI catalog and database defaults, and then spell out which fields do that. That is the part data engineers should check before changing generated jobs.

This kind of rule is easy to miss during connector rollout. A URI can describe a default catalog and database, but a per table mapping can still move the target. That is useful for mixed StarRocks layouts, but it also means a shared URI is not the whole routing story. Review any template that emits both a URI path and source-table metadata.

The other change is internal maintenance: the integration test timeout is increased to 20m. That does not describe a production runtime change for ingestr jobs. It does say something about the release process around connectors that can be slower under CI load or remote service variance.

For platform teams, the useful signal is not that every run should now take twenty minutes. The signal is that upstream CI now tolerates longer integration paths. If you mirror ingestr tests in your own pipeline, compare that value with your job timeout, service startup budget, and any network calls used by connector tests.

There is no breaking change called out in the release notes, and the release is not a prerelease. The practical check is configuration review. Search StarRocks jobs for URI paths that include catalog or database values, then compare them with any source-table fields emitted by job generation.

If both are present, document which value should win in your own repo. That prevents a later cleanup from removing what looks like duplicate routing data. It also gives reviewers a concrete rule when they see StarRocks connection strings and table metadata in the same diff.