kibana doesn't seem to follow aliases

[jro]

I ended up with a situation around the beginning of the year where logstash logged some data to 2013.01.XX and some to 2014.01.XX because of a bug in an output plugin. I backed up the 2014.01.XX indexes and reimported them as logstash-partial-2014.01.XX. Then I setup aliases for logstash-2014.01.XX to point to both the 2013 and 2014 data sets.

Kibana does not seem to follow the aliases from what I can tell. I can query though them and retrieve counts just fine, however.

curl -XGET 'http://localhost:9200/logstash-2014.01.06/_count/?pretty=true'
{
  "count" : 22298717,
  "_shards" : {
    "total" : 10,
    "successful" : 10,
    "failed" : 0
  }
}

curl -XGET 'localhost:9200/_alias/logstash-2014.01.06?pretty=true'
{
  "logstash-2013.01.06" : {
    "aliases" : {
      "logstash-2014.01.06" : { }
    }
  },
  "logstash-partial-2014.01.06" : {
    "aliases" : {
      "logstash-2014.01.06" : { }
    }
  }
}

[rashidkpc]

Kibana does not know the difference between an index and an alliance. I'm guessing there is some other issue here, we have tested against aliases extensively.