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
percolator registered on an alias is never triggered #3147
Comments
This is a very heavy issue for me, cause im relying on percolator and aliases.
|
The percolate api just doesn't support resolving aliases. The redesigned percolate api does support resolving aliases to concrete indices. |
Now fully supported via #3420 |
martijnvg
pushed a commit
that referenced
this issue
Apr 25, 2018
This commit adds a bulk action for apply translog operations in bulk to an index. This action is then used in the persistent task for CCR to apply shard changes from a leader shard. Relates #3147
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this issue
May 11, 2018
This commit adds a bulk action for apply translog operations in bulk to an index. This action is then used in the persistent task for CCR to apply shard changes from a leader shard. Relates elastic#3147
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actually, adding a percolator is always successful, regardless whether the targeted index exists or not. Currently, the targeted index should be a real index, and cannot be an alias. I don't know if this is the wanted behavior, but it's confused me; the percolate documentation is silent about this use case.
To reproduce:
The text was updated successfully, but these errors were encountered: