This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
Remove VARCHAR and CHAR precision when loading from temporary table #54
Milestone
Comments
rzats
added a commit
that referenced
this issue
Nov 28, 2018
rzats
added a commit
that referenced
this issue
Dec 10, 2018
rzats
added a commit
that referenced
this issue
Dec 11, 2018
rzats
added a commit
that referenced
this issue
Dec 17, 2018
rzats
added a commit
that referenced
this issue
Dec 17, 2018
chuwy
changed the title
Remove VARCHAR-precision when loading from temporary table
Remove VARCHAR and CHAR precision when loading from temporary table
Dec 21, 2018
rzats
added a commit
that referenced
this issue
Dec 21, 2018
rzats
added a commit
that referenced
this issue
Dec 21, 2018
rzats
added a commit
that referenced
this issue
Dec 24, 2018
rzats
added a commit
that referenced
this issue
Jan 7, 2019
rzats
added a commit
that referenced
this issue
Jan 7, 2019
rzats
added a commit
that referenced
this issue
Jan 8, 2019
rzats
added a commit
that referenced
this issue
Jan 9, 2019
rzats
added a commit
that referenced
this issue
Jan 14, 2019
rzats
added a commit
that referenced
this issue
Jan 14, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Loader loads data in two steps:
OBJECT
-column tableatomic.events
During second step, it also performs extraction and casting to get the right property (e.g.
enriched_data:event_version::VARCHAR(128)
). But precision in unnecessary in this step, it adds another point of failure in a case where user mutated table manually.Leaving aside a point that we should avoid mutating table manually, sometimes it can be necessary and in future version we're planning to provide a fine-grained approach with processing manifest.
The text was updated successfully, but these errors were encountered: