-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
action.auto_create_index evaluated incorrectly for date_index_name pipeline #50015
Labels
:Data Management/Ingest Node
Execution or management of Ingest Pipelines including GeoIP
:Distributed/CRUD
A catch all label for issues around indexing, updating and getting a doc by id. Not search.
Team:Data Management
Meta label for data/management team
Team:Distributed
Meta label for distributed team
Comments
cbuescher
added
:Data Management/Ingest Node
Execution or management of Ingest Pipelines including GeoIP
:Distributed/CRUD
A catch all label for issues around indexing, updating and getting a doc by id. Not search.
labels
Dec 10, 2019
Pinging @elastic/es-distributed (:Distributed/CRUD) |
Pinging @elastic/es-core-features (:Core/Features/Ingest) |
rjernst
added
Team:Data Management
Meta label for data/management team
Team:Distributed
Meta label for distributed team
labels
May 4, 2020
I'm also observing this behavior with 7.10.2. |
Still happening in 7.13.3. Any plan to fix this? Encountered this while setting up legacy monitoring:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/Ingest Node
Execution or management of Ingest Pipelines including GeoIP
:Distributed/CRUD
A catch all label for issues around indexing, updating and getting a doc by id. Not search.
Team:Data Management
Meta label for data/management team
Team:Distributed
Meta label for distributed team
Elasticsearch version (
bin/elasticsearch --version
):7.5.0 (also observed with 5.6.16 and 6.8.5)
Plugins installed: []
plain OSS install
JVM version (
java -version
):1.8.0_211
OS version (
uname -a
if on a Unix-like system):CentOS6
Description of the problem including expected versus actual behavior:
Automatic index creation whitelist (action.auto_create_index) appears to not get honoured properly when the new index name gets computed / set as part of an ingest pipeline.
Steps to reproduce:
Provide logs (if relevant):
Logs do not show errors, just the cluster settings changes, including
Some References
#20640, #22435
The text was updated successfully, but these errors were encountered: