We could do another CL now with the 0.94.14-SNAPSHOT version. It was just a bunch of code that was orthogonal to this, so figured it could be done later (by someone else even?).

> no other option 

We could just do one method that takes a KeyValue.Type, but that leaks a bit more of the KeyValue implementation than I'd like to the rest of phoenix.

> any way of ensuring that we do?

We'd just have to watch KeyValue and make sure one-one messes with it. We can -1 the release candidates (or I can :) to ensure that we maintain compatibility.