It seems that the async code path is implemented by simply executing synchronous version on the thread pool.
Is it possible to make this really async (i.e. using non-blocking socket stack like, for example, what netty does)?
I'm not familiar enough with Thrift, it may not be even fundamentally possible..
We tried implementing the non-blocking async code but it ended up being very complicated to deal with retries and maintaining state when switching keyspace. A lot of the plumbing is there so it should be possible to take another stab at it.
Will not be implemented
DataStax/@PatrickMcFadin recommends executeAsync calls instead of multi-get... slide 14 here: http://www.slideshare.net/patrickmcfadin/cassandra-at-scale
Can you revisit/elaborate the 'wontfix' associated with this?