-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Prevent large objects from being stored in the RTIF #38094
Prevent large objects from being stored in the RTIF #38094
Conversation
bdd600e
to
6a10c94
Compare
678cb87
to
ffc67d1
Compare
There's something wrong with MySQL around templated fields. cc @uranusjr . Oh, seen another test failure that's not mysql |
ffc67d1
to
6937000
Compare
I will like to include this in the next beta/rc, please review @uranusjr @jedcunningham @potiuk |
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. with one nit - but up to you to address it.
36485f8
to
c7c2a24
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.
Nice. The prefix is cool.
There is one worry with that U just wanted to mention it.
I understand that we are masking secreates before serialization ? Just wanted to amke sure sure of it - it looks like from the code , but I wanted to make sure we are not showing half-unmasked secrets accidentally when we truncate the secrets.
c7c2a24
to
a4c824d
Compare
The secrets are masked after serialization see: airflow/airflow/models/renderedtifields.py Line 127 in 6a225cc
|
|
150aec6
to
548164b
Compare
11843f5
to
987d980
Compare
There's no control over the size of objects stored in the rendered taskinstance field. This PR adds control and enable users to be able to customize the size of data that can be stored in this field closes: apache#28199
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
a110375
to
8aa3962
Compare
When a field gets truncated, is that only for the purpose of rendering it the UI? Or will it also get truncated when it gets executed? The release notes on this topic are not clear and I'm seeing the truncation occur in both |
There's no control over the size of objects stored in the rendered taskinstance field. This PR adds control and enable users to be able to customize the size of data that can be stored in this field
closes: #28199