Allow running airflow against sqlite in-memory DB for tests #37144
+31
−14
Conversation
This file contains 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
potiuk
approved these changes
Feb 2, 2024
This makes no sense for production workloads, but it is useful for writing tests of Airflow operators etc. I also moved the warning from configure_vars to convigure_orm so that it is checked after local settings have been applied in case that changes anything.
ashb
force-pushed
the
allow-sqlite-temp-db
branch
from
f3c91ef
to
1c3b9e4
Compare
jedcunningham
added
the
type:misc/internal
jedcunningham
pushed a commit
that referenced
this pull request
Feb 9, 2024
This makes no sense for production workloads, but it is useful for writing tests of Airflow operators etc. I also moved the warning from configure_vars to convigure_orm so that it is checked after local settings have been applied in case that changes anything. (cherry picked from commit 7324400)
potiuk
pushed a commit
that referenced
this pull request
Feb 13, 2024
This makes no sense for production workloads, but it is useful for writing tests of Airflow operators etc. I also moved the warning from configure_vars to convigure_orm so that it is checked after local settings have been applied in case that changes anything. (cherry picked from commit 7324400)
ephraimbuddy
pushed a commit
that referenced
this pull request
Feb 22, 2024
This makes no sense for production workloads, but it is useful for writing tests of Airflow operators etc. I also moved the warning from configure_vars to convigure_orm so that it is checked after local settings have been applied in case that changes anything. (cherry picked from commit 7324400)
68 tasks
abhishekbhakat
pushed a commit
to abhishekbhakat/my_airflow
that referenced
this pull request
Mar 5, 2024
…7144) This makes no sense for production workloads, but it is useful for writing tests of Airflow operators etc. I also moved the warning from configure_vars to convigure_orm so that it is checked after local settings have been applied in case that changes anything.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 makes no sense for production workloads, but it is useful for
writing tests of Airflow operators etc.
I also moved the warning from configure_vars to convigure_orm so that it
is checked after local settings have been applied in case that changes
anything.
Related to #36774 which was released in 2.8.1 -- prior to that this worked without problem