Repository navigation
Add optional Blob and secure-document modules with governed views - #274
Draft
philipgreat wants to merge 35 commits into
Draft
philipgreat wants to merge 35 commits into
philipgreat wants to merge 35 commits into
Conversation
added 30 commits
October 25, 2026 17:32
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Add an optional explicit Tika verifier and current-context upload orchestration with immutable request replay, bounded streaming and catalog promotion only after actual byte verification. Cover all ten real formats and seven shared cases through PostgreSQL, file storage and native SQL binding. Signed-off-by: Philip Z <hello@teaql.io>
Fence server-stream publication with the upload row lock and add scoped bounded maintenance with current authorization, committed claims, version-conditional deletion and retryable acknowledgements. Verify real PostgreSQL/file lifecycle, concurrent writers/collectors, host scheduling and separate JVM halt recovery. Signed-off-by: Philip Z <hello@teaql.io>
Add a core-only optional private staging helper with per-job OS leases and separately authorized host collection. Fence file/Tika request scratch through process failure, place bounded PDF spill in the lease, and require actual image/audio parser facts. Verify forced process termination through public upload/confirmation, native SQL binding and collection. Signed-off-by: Philip Z <hello@teaql.io>
Use a dedicated versioned namespace for immutable uploads, exact-version ranges and complete signed read URLs. Seal committed GC claims with conditional persistent retirement objects before deleting only the pinned payload version, preventing delayed remote publishers from resurrecting absent uploads. Validate with 722 clean/package tests, 59 actual S3/PostgreSQL integration methods, 13 High SpotBugs reports and eight packaged dependency boundaries. Track #272; full module assembly and R3 exit remain pending. Signed-off-by: Philip Z <hello@teaql.io>
Add optional core completion SPI and SQL delegation. Notify only after the owning transaction resolves and cleans up; preserve committed/rolled-back/unknown outcomes, rollback-only nested failures, callback ordering/draining and safe auto-commit restoration. Validate 733 clean/package tests, 63 real integration methods, 13 High SpotBugs reports and six artifact boundaries. Runtime ledger/audit wiring remains pending; track #272. Signed-off-by: Philip Z <hello@teaql.io>
Retain submitted ledger batches under the physical owner while later edits form a new batch. Use provisional readback for repeated saves, restore versions and intent on rollback, freeze deferred audits, and preserve committed state after delivery failures. Unknown outcomes block blind same-object retries. Validate 767 clean/package tests, 76 real integration methods, 15 High SpotBugs reports and eight artifact boundaries. Cross-pending-root journal transfer, full Blob assembly and remaining R3-R8 gates stay pending; track #272. Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
Signed-off-by: Philip Z <hello@teaql.io>
added 5 commits
October 27, 2026 04:49
This branch has not been deployed
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.
Blob fields need a stable persisted key while upload, binding, retention, and read URLs follow current authorization and the owning database transaction. This branch adds optional Blob and secure-document modules, versioned file selection and database-backed document operations, file/S3 transports, and runtime-owned view preparation. The Spring MVC bridge is optional; terminal consumers can call the same services directly.
The new schema is explicit. Existing text values are not inferred to be Blob keys, and the existing
tqr1/tqd1document protocol remains compatible. Generated consumers must use matching runtime artifacts. Direct PostgreSQL JDBC references use 42.7.14 to address the advisories found by the PR security gate.Validation: on the merged-source revision
15580c0e, Java Blob/S3/PostgreSQL integration suites passed 137/137 and document/selection/protocol suites passed 38/38, with zero failures or skips. A newly generated Java library and application-owned host passed real PostgreSQL/file/loopback HTTP, governed document selection, view parity, and same-commit receipt checks; its owned schema and process were cleaned. After the JDBC update, the related Maven reactor passed locally with zero failures or errors and four existing skips. All eight public PR CI checks passed on8236833a, including Build and Test, OWASP, SpotBugs, examples, live dialects and cross-platform HTTP. Exact commands, source revisions and logs are in the conformance R6 evidence.Tracks #272; primary coordination is teaql/teaql-conformance#237, with teaql/teaql-rs#312 and teaql/teaql-code-gen#311. This remains a draft: an external machine has not yet validated a complete signed S3 URL; R7 registry-only candidate and R8 public delivery are pending. The private conformance/codegen GitHub Actions runner is blocked by an account payment or spending-limit issue, so the planned external S3 probe has not run. No release, signed tag, or deployment is included.