docs: propose native JSON columns for metric and consent tables - #2916
Open
constantine2nd wants to merge 1 commit into
Open
constantine2nd wants to merge 1 commit into
constantine2nd wants to merge 1 commit into
Conversation
|
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
1 participant
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.
Adds
ideas/NATIVE_JSON_COLUMNS.md— a short proposal, no code changes.Why
Several of our largest columns hold JSON (
metric.responsebody,mappedconsent.mjsonwebtokenpayload,consentrequest.payload) but are declared as plain text, so the database cannot read them. We capture, store and pay for that data, then cannot query it without exporting it./management/metricsoffers ~20 filters, every one a dedicated column added by hand in its own migration and release.What the doc says
Extend PostgreSQL's native JSON type (
jsonb) to those tables, so the cost of a new question drops from a release to a query. The doc frames the benefit as user journeys (support, compliance, fraud, product, engineering) rather than implementation.It inherits the principle already settled in
ideas/dynamic_entity_indexing.md— DB-native JSON is an optional accelerator behind capability detection, never a requirement — and reuses the vendor detection that already ships asIndexingCapabilities, rather than introducing a parallel mechanism.Scope
Documentation only. No API contract change, no schema change, no code. The ask is agreement to pilot on
metric.responsebody.