The whole sharded schema sat in one tablet, so no number of tablet
servers, scan servers or compactors made any difference to a query.
Splits now come from a checked-in file, the deployment moves to three
shards per day, and verifySplits.sh guards that in CI.
Also fixes the num shards cache, which scanned a metadata table name no
deployment that renames its tables actually uses. The missing table was
swallowed, so a day expanded into no shards and the query silently
returned nothing.
---------
Co-authored-by: Claude Opus 5 <[email protected]>
…s from NationalSecurityAgency/datawave-stack-docker-images
---------
Co-authored-by: Moriarty <[email protected]>
Co-authored-by: Claude Opus 5 <[email protected]>
Compose derived its project name from the directory, so concurrent jobs
shared one stack and nothing tore it down; a blanket prune stood in for
teardown and deleted images other jobs were still using.
Co-authored-by: Claude Opus 5 <[email protected]>
- Upload raw surefire/failsafe XML as build artifacts (always run).
- Publish a JUnit check run + job summary that surfaces tests which only
passed after a rerun (flakes), which the rerunFailingTestsCount flags
otherwise hide.
- Copy mikepenz/action-junit-report (v6, 3a81627) as a local action at
.github/actions/junit-report to satisfy the verified-actions-only
policy.
- Add the checks/pull-requests permissions the reporter needs.
Non-blocking: fail_on_failure:false + continue-on-error, so flakes
become visible without changing what fails the build.
## Summary
- `actions/github-script@v7` and `actions/cache@v4` both still target
the deprecated Node.js 20 runtime, which GitHub now force-runs on Node
24 and flags with a warning annotation on every workflow run (seen
recently on PR #3683's checks).
- Bump both to their minimum Node 24-native releases:
`actions/github-script@v8` and `actions/cache@v5`. Neither introduces
breaking changes relevant to our usage (v8/v5 changelogs are Node
runtime bumps only; v9 of github-script would add breaking API changes
we don't need).
## Test plan
- [x] Confirm the `require-labels.yml` and `compose-tests.yml` workflows
run green on this PR
- [x] Confirm the Node.js 20 deprecation warning annotation no longer
appears on the check runs
Co-authored-by: Claude Sonnet 5 <[email protected]>
addresses HTTP 429 Too Many Requests errors seen in CI jobs recently
`actions/setup-java` will skip creating settings.xml
`Skipping generation /home/ec2-user/.m2/settings.xml because file
already exists and overwriting is not required`
---------
Co-authored-by: Joe Alphonso <[email protected]>
The label 'no-downstream-affects' was deleted in favor of the more
grammatically correctly and aesthetically pleasing label
'no-downstream-effects'.
This commit updates our required-labels.yml to reflect this change.
This PR aims to add a cascading release pipeline that will update each
project to release the entire tree (or part of it) starting from one
given repo.
bumps the microservice parent versions on the related modules that
reference them
re-enables formatting in CI now that all modules have the same plugin
configuration
verified there are no other commits in the microservice-parent and
microservice-service-parent besides the spotless plugin changes since
the last release
Co-authored-by: Joe Alphonso <[email protected]>
bumps the microservice parent versions on the related modules that
reference them
re-enables formatting in CI now that all modules have the same plugin
configuration
verified there are no other commits in the microservice-parent and
microservice-service-parent besides the spotless plugin change since the
last release
Co-authored-by: Joe Alphonso <[email protected]>
Here's what changed and why:
Root cause: When a reusable workflow is called via workflow_call, the
caller sees the overall workflow result as failure if any job in it
fails — even if the gate job (compose-check-jobs) succeeds. So when one
compose test fails but the other passes, the coordinator's gate
correctly succeeds, but required-checks.yml sees
needs.call-compose-tests.result == 'failure'.
Fix (two files):
1. compose-coordinator.yml — Added a workflow_call output
(compose-check-result) that exposes the gate job's explicit status. The
gate job now sets a status output to success when at least one test
passed (before potentially exiting with failure when neither passed).
Also replaced the actions/github-script step with a bash conditional for
consistency.
2. required-checks.yml — Changed compose-check-jobs to check
needs.call-compose-tests.outputs.compose-check-result instead of
needs.call-compose-tests.result, so it reads the gate's actual
determination rather than the overall workflow result.
Co-authored-by: Joe Alphonso <[email protected]>
replace impsort with spotless maven plugin to automatically cleanup
unused imports
formatting is fast and occurs early in the maven lifecycle
prevents checkstyle from failing later for unused imports
---------
Co-authored-by: Joe Alphonso <[email protected]>
Co-authored-by: alerman <[email protected]>
Use a coordinator pattern to call workflows and process the results.
Tested README.md change in a few places.
Tested code change in main.
Tested code change in microservices.
Tested .github changes.
---------
Co-authored-by: Joe Alphonso <[email protected]>
added zookeeper and tserver exposed ports
added efficient accumulo and zookeeper healthcheck for quickstart
container in compose file
added quickstart as a dependent service to the metrics service and
adjusted its healthcheck configuration
updated CI compose-tests: simplified logic for faster more reliable
startup
fixed issue with quickstart image builds when using maven build cache
---------
Co-authored-by: Joe Alphonso <[email protected]>
Added system environment requirements for RHEL and Docker versions.
Also fixed the github workflow checks to bypass `**/*.md`
---------
Co-authored-by: Joe Alphonso <[email protected]>
Drew Farris