Yes, that is correct.
Martijn
On 21 May 2014 02:34, Mark Dodwell wrote:
> Many thanks, that is a super clear answer.
>
> So, until that issue is addressed, am I correct in thinking I should do
> this when percolating an existing document:
>
> ```
> curl http://0.0.0.0:9200/idx-1/docs/123/_perc
Many thanks, that is a super clear answer.
So, until that issue is addressed, am I correct in thinking I should do
this when percolating an existing document:
```
curl http://0.0.0.0:9200/idx-1/docs/123/_percolate -d '{
"filter": {
"term": {
"account_id": 1
}
}
}'
```
Thanks a
1. Yes, the routing will be taken into during adding the percolator query.
2. At the moment only the routing will be taken into account, the filter
will not be taken into account.
I opened issue percolator against an alias with a filter:
https://github.com/elasticsearch/elasticsearch/issues/6241
Consider an index `idx`, with a mapping for a single type `docs`. Consider
aliases of the format `idx-{ACCOUNT-ID}`, with a term filter and a routing
value set to the account id, like so:
```
$ curl http://0.0.0.0:9200/idx/_aliases?pretty=1
{
"idx" : {
"aliases" : {
"idx-1" : {
Consider an index `idx`, with a mapping for a single type `docs`. Consider
aliases of the format `idx-{ACCOUNT-ID}`, with a term filter and a routing
value set to the account id, like so:
```
$ curl http://0.0.0.0:9200/idx/_aliases?pretty=1
{
"idx" : {
"aliases" : {
"idx-1" : {
