1. Is there a aout of the box JDBC Cache loader and if so is this a better approach than using a Lucene JDBC directory?
I'm likely not undersanding the question, as in the other thread you seem well aware of the JdbcStringBasedCacheStore. Do you mean a different kind of "out of the box" ? In that case I think the answer is no, but please clarify what you would have liked to have so we might consider making it.
2. What is the advantage or disadvantages of using Cassandra as cache store vs JDBC.
I'm not an expert on Cassandra. In my opinion they are both a good fit for this purpose, as usually the indexes are order of magnitude smaller than the database they're related to.
Cassandra might scale better/be a better fit if you're having an extreme high load or huge index, still it requires you to configure and setup Cassandra, and likely you'll need some experience with it as it's not really a small toy, while if you have Hibernate around I'm going to assume you have a rock stable and simple JDBC database already so it should be easier to setup and backup, and you'll have one less service to monitor and keep alive.
Thanks Sanne, I'm giving a go to JdbcStringBasedCacheStore. I posted this question before that other one where you had already helped me with it.