Migrate Elasticsearch example DAGs to new design
See original GitHub issueThere is a new design of system tests that was introduced by the AIP-47.
All current example dags need to be migrated and converted into system tests, so they can be run in the CI process automatically before releases.
This is an aggregated issue for all example DAGs related to Elasticsearch provider. It is created to track progress of their migration.
List of paths to example DAGs:
- airflow/providers/elasticsearch/example_dags/example_elasticsearch_query.py
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Migrate | Elasticsearch Guide [8.5] | Elastic
Elastic Cloud. Maximize value and optimize your experience. Deploy everything Elastic has to offer across any cloud, in minutes.
Read more >Migration guide | Elasticsearch Guide [8.5] | Elastic
This section discusses the changes that you need to be aware of to migrate your application to 8.5.3. For more information about what's...
Read more >Migrating to 8.0 | Elasticsearch Guide [8.5] | Elastic
At startup, Elasticsearch will automatically migrate the data path to the new layout. This automatic migration will not proceed if the data path...
Read more >Migrate to data tiers routing API | Elasticsearch Guide [8.5]
The following example migrates the indices, ILM policies, legacy templates, composable, and component templates away from defining custom allocation filtering ...
Read more >Migrating to 8.4 | Elasticsearch Guide [8.5] | Elastic
This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 8.4. See also What's new...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

It was automated checks - indeed it seems that the original test is not removed yet 😃
Ah … automation was not set in the project - normally when issue is closed, it goes to Done automatically but it was disabled 😃? Re-enabled it back