GET /_alias/foo* returns unrelated aliases

Elastic Search
5

Hello @Richard_Zhang

These are my findings :

GET _alias
This command list all the alias & I am able to find my created alias as well as filebeat alias in this output.

Example output in JSON extracted 3 aliases :

"elastic-cloud-logs-8": {
  "aliases": {
    "filebeat-elastic-cloud-logs-8": {}
  }
	
"kibana_sample_data_logs": {
  "aliases": {
    "kibana_logs_alias": {}
  }
}

"kibana_demo": {
  "aliases": {
    "kib_demo": {
      "is_write_index": true
    }
  }
}

If i add any property like is_write_index => this alias is visible in

GET /_cat/aliases?v

POST /_aliases
{
  "actions": [
    {
      "add": {
        "index": "kibana_demo",
        "alias": "kib_demo",
        "is_write_index": true
      }
    }
  ]
}

GET /_cat/aliases?v

Output :

alias index filter routing.index routing.search is_write_index
kib_demo kibana_demo - - - TRUE

The 1 created before (kibana_logs_alias) is not visible (GET /_cat/aliases?v) as it was set with no properties.

I am not sure if below can be the reason :
The alias appears without additional configurations such as filters, routing or write index settings, which is why it seems "blank" in terms of these additional settings.

Someone from elastic can confirm this behavior.

Thanks!!

1 Like