Add a temporary checkin for my current work on DISTINCT with GROUP BY
fix the distinct with AVG optimization, decide to adds DISTINCT at the top level of the plan to simplify all the work; Still need to optimize the EE to have the consistent order as the input for special GROUP BY without aggregations
Disable the DISTINCT push down optimizations; Add test cases first
Add code to have inserted order preserved HASH aggregations for certain interesting cases
remove the DISTINCT related plan node and executors, both EE and Java
Merge branch 'master' of github.com:VoltDB/voltdb into ENG-6436-distinct-reroute
Add more QUERY pattern tests for DISTINCT with GROUP BY
Fix the OrderBy/Limit pushdown problem with DISTINCT
Resolve Paul's comments and code cleanup
Merge branch 'master' of github.com:VoltDB/voltdb into ENG-6436-distinct-reroute
Factor json plan -> executor vector into a stand alone method
Create static factory method for ExecutorVector, build executor vector
for tables with limit delete statement.
Deserialize plan fragment for LIMIT EXECUTE DELETE during catalog
load, store pointer to it in PersistentTable, and run it when
triggered by an INSERT statement.
Clean up new JNI method.  Still need correponding IPC stuff.  And
testing.
Add IPC support for decodeBase64AndDecompress
More testing for LIMIT EXECUTE DELETE
Beginning of a test for ALTER TABLE ... ADD LIMIT ... DELETE
Add to LIMIT DELETE to white list for add and modify
Misc comment updates
Add VoltCompiler tests for LIMIT DELETE statement
More testing for VoltCompiler and regression suites for ALTER TABLE ... ADD LIMIT
Make sure to remove the purge fragment from persistent table in EE if the
statement goes away in the catalog
Misc cleanup in preparation for push