-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature: Teach the combiner to keep track of a running inferred schema and log whenever it changes. #1128
Conversation
04eba63
to
c895a0e
Compare
e6eb307
to
483f11e
Compare
713009d
to
f185673
Compare
218b8af
to
aa55bfa
Compare
ec9aec8
to
25b6025
Compare
I'm also done force-pushing here too, sorry 🤦 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two major notes:
-
We want to selectively enable this widening / logging. Capture tasks definitely should do it, but materializations don't need to and also don't want to pay the overhead. How about a new boolean to enable the behavior in the protobuf config API?
-
The logs must include the collection name, which also needs to be plumbed through.
Other than that and comments below LGTM 👍
Ok, I added |
73e1103
to
9b2066c
Compare
|
…a and log whenever it changes.
…ew Combiner, otherwise keep the schema around to reduce spurious logging
… `Config` message, and plumb through the appropriate values.
9b2066c
to
0f50e31
Compare
…n `enable_schema_inference`
0f50e31
to
f536e96
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is the second step of #1115.
This change is