From bug #722359: Ricky points out aliases: http://www.elasticsearch.org/guide/reference/api/admin-indices-aliases.html http://elasticsearch-users.115913.n3.nabble.com/Just-Pushed-Index-Aliases-td487342.html My cursory look is that there are a bunch of complexities: 1. elasticutils has an internal get_es() that looks at ES_INDEXES---have to work around this possibly by storing the live alias in settings. 2. there are a bunch of edge cases especially in development environments involving half-built indexes, indexes that failed to build, ... when starting up, the system needs to know which index to use. we probably need an invariant along the lines of "at any given time index/alias named 'xyz' needs to be valid and good". 3. admin interface needs to be spruced up to be able to query indexes out there, aliases out there, and manipulate them. I think this warrants a design spec to make sure we've covered all the bases.
If we get this working, we can do reindexing without downtime. Given that, I think it's worth bumping this up in the priorities. So I'm putting it in next week's sprint.
Bumping important ES bugs up to P1.
I meant to take this earlier. Already working on it.
Bumping this out of 2012.3 sprint. It's being replaced by bug #723511 for now.
I'm going to nix this. We have read/write index support now and I think that's all we really need. Aliases add another level of complexity that I'm not wildly excited about and I don't think we get anything more out of them than we already have with read/write indexes. Marking as WONTFIX.