Repository navigation
docs: describe downstream Spark consumers generically - #302
Open
dimitri-yatsenko wants to merge 1 commit into
Open
dimitri-yatsenko wants to merge 1 commit into
dimitri-yatsenko wants to merge 1 commit into
Conversation
Five places pointed readers at material outside these docs that they cannot open: a repository, a decisions file, an issue tracker, and two internal names. Describe the downstream consumer as a Databricks silver layer instead. Every technical statement stays.
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
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.
Five places pointed readers at material outside these docs that they cannot open: a repository, a decisions file, an issue tracker, and two internal names. This describes the downstream consumer as a Databricks silver layer instead, and keeps every technical statement.
about/whats-new-23.md,reference/specs/spark-adapter.md: the motivating case is a Databricks silver layer.explanation/spark-adapters.md: drops the "strategic background" bullet, which linked a file readers can't open.reference/specs/spark-adapter.md: the publish-loop example compares itself with "a production consumer".reference/specs/trace.md: per-row upstream projections are described by what they do.assets/stylesheets/extra.css: the link-color comment says the value is provisional until the brand palette is ratified.Text only; no page structure or code changes.