Matteo Bertozzi I think what I'm doing with making the payload rpc controller pluggable actually makes the following:
because once you give the setPriority() to the client, all the client requests will be HI priority and that will impact the META requests.
less of an issue as it allows the client to plug in their own implementation, which could be a one smarter about which table gets which priority (so meta, root keep their high priority and other tables can be ordered on priority).
Clearly, this is well short of what you are proposing, but maybe its a good intermediate step? Maybe it might save you some small amount of work?
For phoenix, we are creating an HTable on the server side to write between RS for the mutable secondary indexes. So the priority is somewhat surfaced to client (ala config values), but not actually changing the API.
I'm not sure how Andrew Purtell feels about your work going into 0.98, so this issue might be the way forward for that until you finish up the work for trunk? Just trying to figure out how we can all eat our cake