Metadata long term solution #32
Draft
Conversation
This file contains 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
updating from dotz
added Table class and is_metadata to table field
…cific - using GoogleCloudLakeHouseService to handle parsing from internal to bq specific
…le_schema_without_metadata_columns
|
hey folks @lawrencestfs @mayconcad, any update on this draft? |
|
I think that the most important methods are the ones from GoogleCloudLakeHouseService tha returns a dict structure. Maybe we can get rid of the bigquery entities and parse the internal table into the dict representation for google's APIs |
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.
Draft PR for the long term solution of the metadata schema issue
This PR aims to add a is_metadata field to the generic table schema, this PR also decouple the generic internal representation from the bigquery representation