After upgrading to the 2.0 driver branch, I received a lot of warnings about
re-preparing previously prepared statements. I read about this issue, and my
work around was to cache my prepared statements in a MapString,
PreparedStatement internally in my app via a common prepare method, where
Well, it may seem like I'm talking to myself now with this response, but I
cracked open the source and found the answer in fairly short order so I figured
I would share what I found. Datastax folks, please do verify that I'm correct
if you don't mind.
Long story short, BoundStatement