-
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
Migrate execution_date database columns to logical_date #19049
Comments
Is this still pending @uranusjr ? |
Let's not do this in 2.3 |
@uranusjr should we add this task also under AIP-83 project effort? |
Ah I totally forgot this issue exists. Thanks, going to add it. The database level migration is already done, but we still need to rename the attribute on the model (and all references to it, obviously). We also don’t need to emit a deprecation warning since this is only for 3.0. |
This is covered in #43902 |
Now that this PR: #43902 is merged following is covered:
|
To conform with other AIP-39 changes.
execution_date
should still be kept on the class and emit a deprecation warning when accessed (either as a property or a filter). I think there's mechanism in SQLAlchemy for this out of the box.The text was updated successfully, but these errors were encountered: