Skip to content

chore: bump appVersion to 0.2.2 (arrow 0.2.2 / core 0.20.1), chart 0.3.2 - #15

Merged
fupelaqu merged 1 commit into
mainfrom
chore/bump-arrow-0.2.2
Jul 29, 2026
Merged

chore: bump appVersion to 0.2.2 (arrow 0.2.2 / core 0.20.1), chart 0.3.2#15
fupelaqu merged 1 commit into
mainfrom
chore/bump-arrow-0.2.2

Conversation

@fupelaqu

Copy link
Copy Markdown
Contributor

Rolls the softclient4es-arrow 0.2.2 release into the federation and sidecar images.

From To
chart version 0.3.1 0.3.2
appVersion (image tag) 0.2.1 0.2.2

What the new images carry

arrow 0.2.2 was built against elasticsql core 0.20.1 and extensions 0.2.1:

  • elasticsql#157 — a cross-index JOIN now fails loudly when no join-capable extension is installed. Previously it silently executed as a single-index search over the left table (joined columns NULL, orphan rows kept), and INSERT … SELECT / CTAS wrote that wrong data.
  • elasticsql#158FieldSort preserves the table-alias qualifier on the AST → SQL round-trip. This is the one that mattered most for federation: the JOIN planner re-parses the re-rendered SQL, so a dropped qualifier surfaced as 400 "Ambiguous column" on any federated JOIN with ORDER BY.
  • elasticsql#159ORDER BY on a bare table alias is rejected instead of rendering a dangling qualifier.

Image availability verified before bumping

Every template derives its tag from .Chart.AppVersion — the federation deployment directly, and each sidecar through softclient4es-federation.sidecarImage in _helpers.tpl. So a bump is only safe once all five images publish the tag. Confirmed on DockerHub:

  • softnetwork/softclient4es-federation:0.2.2
  • softnetwork/softclient4es{6,7,8,9}-arrow-flight-sql:0.2.2

Goldens

All 7 goldens regenerated (4 base + 3 example). The diff is limited to version labels (helm.sh/chart, app.kubernetes.io/version), image tags, and checksum/config annotations — the ConfigMap embeds the chart/version labels, so its hash necessarily moves with them. There was no pre-existing drift before this change, so nothing unrelated is mixed in.

Verification — full CI gate run locally

  • helm lint on the chart and on every tests/values/*.yaml and examples/*/values.yaml — 0 failures
  • helm template + kubeconform -strict -kubernetes-version 1.29.0 on base and all 6 value sets — 3–11 resources per render, 0 invalid, 0 errors
  • golden diff on all 7 renders — all match
  • zero-kind: Secret contract (Story 16.3) — 0
  • heterogeneous-ready / three-region discriminator (16.4 A2b) — 3 vs 0 commented duckdb-attach previews

🤖 Generated with Claude Code

Rolls the softclient4es-arrow 0.2.2 release into the federation + sidecar
images. That release carries elasticsql core 0.20.1 and extensions 0.2.1:

- #157 cross-index JOIN now fails loudly when no join-capable extension is
  installed (was: silent single-index search with NULL joined columns)
- #158 FieldSort preserves the table-alias qualifier on the AST -> SQL
  round-trip, fixing 'Ambiguous column' on federated JOIN + ORDER BY
- #159 ORDER BY on a bare table alias is rejected

Image availability verified on DockerHub before bumping: the federation
image AND all four softclient4es{6,7,8,9}-arrow-flight-sql sidecar images
publish a 0.2.2 tag (every template derives its tag from .Chart.AppVersion).

All 7 goldens regenerated. The diff is version labels, image tags and the
checksum/config annotations only -- the ConfigMap embeds the chart/version
labels, so its hash necessarily moves with them.

Verified locally against the full CI gate: helm lint (chart + every values
file and example), helm template + kubeconform -strict (k8s 1.29, 3-11
resources per render, 0 invalid), golden diff on all 7 renders, the
zero-kind:Secret contract, and the heterogeneous-ready/three-region
discriminator (3 vs 0 duckdb-attach previews).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@fupelaqu
fupelaqu merged commit a5f03e8 into main Jul 29, 2026
13 checks passed
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.

1 participant