Cleanup up defaults + logging.

This resolves the issue of salted indexes. Essentially, HTables have default pools with unbounded
threads, but direct handoff of tasks via the queue. Therefore, the default of 1 thread meant
that batching updates in a multi-threaded environment (or even to multiple RS) would cause
a RejectedExecutionException. We up the value to Integer.MAX_VALUE by default, allowing us
to grow as we need.

This is not an ideal solution - it can quickly burst up to a large number of threads. What we
really want to do is set a max level of parallelization and then queue up any remaining tasks
(similar to what we are doing with the rest of the indexing pools).

Additionally, we support the standard HTable retry values in a "set if not set" style so
the user can override their settings. This means you have increased flexibility in how quickly
you want an index update to fail, making it more resilient to RS (particularly the one holding
-ROOT- and/or .META.) outage.
Merge pull request #472 from samarthjain/master

Tests for row value constructor optimization. Query more test for salted...
Bug fix for altering salted table
Fixes for altering a salted table
Remove unused variable
Disable OR optimizations for mix of RVC and non RVC
Disallow DELETE for table with immutble rows unless all index columns are PK columns
merging m-r bulk loader with phoenix
merging m-r bulk loader with phoenix
Merge pull request #475 from arunsingh16/master

Map-Reduce CSV bulk loader support
Rename CSV bulk loader
1.update bin/readme.txt, 2.remove index table code, 3.remove hardcoded params
Update readme
Merge pull request #477 from arunsingh16/master

1.update bin/readme.txt, 2.remove index table code, 3.remove hardcoded params
Rework row value constructors, handle nested rvc, always coerce rhs to lhs type, handle in list for rvc
Merge branch 'master' of github.com:forcedotcom/phoenix
Fix rvc optimization
Fix potential for endless recursion in PDataType
Combine OR ranges
Comment only change for TODOs