docs: BI docs twins — publish the structural gaps, retire the Custom SQL workaround - #278
Draft
fupelaqu wants to merge 1 commit into
Draft
docs: BI docs twins — publish the structural gaps, retire the Custom SQL workaround#278fupelaqu wants to merge 1 commit into
fupelaqu wants to merge 1 commit into
Conversation
…SQL workaround Story 20.6, the dual-docs half of the website's BI connection-guide corrections (SOFTNETWORK-APP/softclient4es-web#43). - `client/bi_tools.md`: Power BI and Metabase lose the "Compatible … JDBC" tier — there is no JDBC path to be compatible with. Both, plus Looker and dbt, move to an explicit "no supported connection path" row carrying its mechanism: no generic JDBC database type (Metabase), no JDBC connector in Power Query, Looker-maintained drivers with a per-dialect parameter allowlist, a mandatory adapter plugin (dbt). Looker's gap is structural, not commercial — a licence would not close it. The intro no longer promises a full connect/browse/JOIN guide for tools that cannot connect. - `sql/known_limitations.md`: the Tableau "use Extract mode, or write Custom SQL" workaround is removed. Tableau documents that it "must wrap the custom SQL statement within a select statement", producing a derived table — which this same file lists as not in this release. Looker stops being handed a subquery workaround for a tool that cannot connect at all. Claims stay in lockstep with the website. No tier moves: Tableau stays Compatible, Looker gets none. Closed Issue #273
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.
Story 20.6 of Epic 20 (BI Venue Enablement) — the
documentation/half. Dual-docs twin of SOFTNETWORK-APP/softclient4es-web#49.Closes #273What changes
documentation/sql/known_limitations.md— the BI section. Metabase, Power BI, Looker and dbt are now published as structural gaps with their mechanism, not as "not yet supported". Three of the four cannot be closed by us at all: Metabase takes only official drivers or a community plugin you build; Power Query has no JDBC connector; Looker takes only Looker-maintained drivers and allowlists JDBC parameters per dialect; dbt requires a dedicated adapter plugin. Saying "coming soon" about any of them would imply our backlog closes it.documentation/client/bi_tools.md— the tier table. Power BI and Metabase stop being tiered "Compatible … via JDBC", because there is no JDBC path to be compatible with; they move to an explicit "no supported connection path" row.The correction that matters most
Both files carried "or write Custom SQL with explicit JOINs instead of letting Tableau compose the query" as the recommended Tableau workaround.
Tableau wraps every Custom SQL statement in a derived table — its own documentation, verbatim: "Tableau must wrap the custom SQL statement within a select statement." Our own captured statements agree, at both connect and worksheet time. Derived tables are on our own "not in this release" list, so the workaround failed on exactly the construct it claimed to avoid. It has never worked, and it is removed from both files.
Tiers
No tier moves. Tableau stays Compatible; Superset, DBeaver, Grafana and DataGrip are untouched; Looker gets no tier at all. Story 20.8 owns any promotion, on evidence from its live run.
Verification
Every vendor claim carries its fetch date in the page, and every claim traces to a row in the story's Sources table. No private-repo references, no epic or issue numbers in customer copy, no patch-level ES versions. The BI sections stay byte-identical to their web twins apart from link-form conversion.
Reviewed over two rounds (fixed-15) alongside the web half.