Restored proper whitespace
Disabled AntiCacheManager debug statements
The EE's TableIterator now supports nested iterators. This will allow us to combine iteration of a PersistantTable + EvictedTable in a single iterator
Removed more unncessary debug statements. Never use System.out. People are abusing my baby...
Minor tweaks to the logic for the nested TableIterator. It turns out that this is actually not what we want to do for SeqScanExecutor...
When we throw an EvictedTupleAccessException down in the EE we no longer need to provide the partitionId. It is not set automatically in the PartitionExecutor
Lots of good stuff here. I'm committing this while sitting at the gate in Chicago waiting to take off...

I reorganized SeqScanExecutor so that it will always scan the EvictedTable after the regular scan. We have to create two different iterators because the schemas of the two tables will be different.

I also think I fixed the random crashing problem in the EE when we throw the EvictedTupleAccessException. I switched our internal access tracker to use an std::vector instead of std::list

Expanded tests to make sure that we check all the different access paths with evicted tuples. I will continue to expand this on the flight right now.
Expanded test cases in TestAntiCacheManagerTPCC
Fix for the failing test. It's commented out for now but it might be enough to get going...
Minor cleanups to remove debug statements...
Simple test for evicting data from multiple tables...
Fixed HStoreConf's site.anticache_eviction_distribution to use an enum option. Moved embedded enum out of AntiCacheManager and into separate AntiCacheEvictionPolicyType
Turned down some of the debug levels for the anti-caching stuff. Way too much information...
Converting more INFO messages to DEBUG in the EE
More turning down the level debug statements... Kids these days...
Removed the confusing and unimplemented 'site.anticache_threshold_ratio' HStoreConf parameter
Make sure that we don't mark deleted tuples from the regular table as evicted. This causes all sorts of problems... #164
There are a couple of things going on in here related to #164

First, the EE no longer tries to set a dummy partitionId in the EvictedTupleAccessException. I actually think that this is unnecessary because there is another problem with serializing the exception.
I think that we are trying to do something in the EE in a non-thread safe manner. I'm not sure what, but I think we are blowing away the EE's shared result buffer, which causes the deserialization of the EvictedTupleAccessException to get messed up.
I also commented out AntiCacheEvictionManager::readBlocks(). This method does not appear to be called by anything. It is probably safe to remove entirely.

This also has the new check to make sure that we don't try to access an evicted tuple that is marked as deleted.
Only debug output tweaks...
Commented out a method in the ExecutionEngine Java API that's not used anymore...