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.
PR Checklist
PR Structure
otherwise).
Thoroughness
Release planning
semver, and I've changed the name of the BRANCH to release/* , feature/* or patch/* .
What
The current dbt build is broken and cannot release or build a new docker image because field descriptions violate BigQuery field description limitations:
This PR resolves the violations by shortening the markdown used to generate tables. The change is visually ugly, but gets the fields under the 1024 character limit.
Why
The stellar-dbt repo persists docs to BigQuery and pushes any updates through this configuration: https://github.com/stellar/stellar-dbt/blob/master/dbt_project.yml#L68 The pipeline is broken because dbt is unable to persist the docs.
Known limitations
[TODO or N/A]