Add SQLExecuteQueryOperator operator #10011
Conversation
|
Nice consolidation! I was also thinking about the same thing. On the naming, what do you think about just |
| # specific language governing permissions and limitations | ||
| # under the License. | ||
| """This module is deprecated. Please use `airflow.providers.vertica.operators.vertica`.""" | ||
| """This module is deprecated. Please use `airflow.providers.sqlite.operators.sqlite`.""" |
There was a problem hiding this comment.
sqlite?
| """This module is deprecated. Please use `airflow.providers.sqlite.operators.sqlite`.""" | |
| """This module is deprecated. Please use `airflow.providers.sql.operators.sql`.""" |
| conn_id='sqlite_default', | ||
| dag=self.dag, | ||
| ) | ||
| op.run(start_date=DEFAULT_DATE, end_date=DEFAULT_DATE, ignore_ti_state=True) |
There was a problem hiding this comment.
Does this create side effect on db level? Should we clear database after tests?
Now we are trying to give more ambiguous names to make it easier to add new operators and to understand the operator's behavior without reading its description. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Hey @mik-laj -> is it something we will managed add before 2.0.0rc1? If not, can you please change the milestone? |
|
It is unlikely that I will find time for this. |
|
closed in favor of #25717 |
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.