Phoenix 180

First revision for review.  There are some open points here.  Still no test case added to consume the stats.  Will do the performance test once the system is available with me.
That sounds fine, but then switch region name after cf name so we can get the stats more easily. I think a good pk would be: <table name><cf name><region name>. Then use the stats name as a regular key value column with the correct type (i.e. VARBINARY ARRAY for guideposts). Probably cleaner to store the stats on the PColumnFamily instead of PTable too. You can still pass then through the PTableImpl constructor, but might as well break them up by CF and pass through the constituent parts to the PColumnFamilyImpl constructor.