Very nice. One thing that might also help boost performance and reduce the complexity of your query process is to look into using the database’s partitioning facilities. We decided to do our own based on time in order to offer some performance gain that would work for any db- but pretty much all of the big db systems offer some sort of partitioning mechanisms built in.
For example, you could set Ignitions partition size to 1 year (or longer, I don’t think there’s currently a way to say “off, everything in one table”), and then modify the table using the db’s syntax to have it partition into smaller segments. Doing this, it always looks like one table to you, but the db stores and searches it separately.