fix deltalake BYTEA error - #240
Merged
Merged
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.
This addresses a tricky bug in MaterializationEngine.
Periodically, and its not clear when, we are getting a problem in the views, where the schema is givign a 500 error and queries fo the views are not converted the WKB columns in a view into positions.
the schema error.. is something about a BYTEA conversion on the WKB columns.
https://minnie.microns-daf.com/materialize/api/v3/datastack/minnie65_phase3_v1/version/1885/views/schemas
here is an example... although right now this is not returning an error
Also the columns were also not getting converted when querying and were left in WKB format when using the query_view function of caveclient, which hits the query_view endpoint on MaterializationEngine.