Adding new TableQueryConfig object for setting multiple table info in the InputFormatBase
The original single-table setters/getters now populate a "default" TableQueryConfig object under the hood. This should make the switch over much easier. Deprecated single table methods in light of the API changes for the new configuration object. ACCUMULO-391
The legacy mapred InputFormatBase now verifies (and fixes the scanner for) a possible change in table name that could happen between the configuration of the map/reduce job and the actual processing of the scanner for a specific split. In that case, the most recent table name associated with the id is always used for the scanner (though the table name that was expected during job setup is still used in the RangeInputSplit). ACCUMULO-391
Removing deprecation for now until we have some discussions. Updating/adding comments. ACCUMULO-391
ACCUMULO-1732 Using table id in RangeInputSplit so that it can be resolved back to "working" table name in mappers. Scanner uses the "working" table name while everything else can still safely use the original configured table name.
Fixing some formatting. Adding some comments. ACCUMULO-391
Cleaning up tests. Adding test for legacy input for base + new multi-table methods. ACCUMULO-391
Fixing some more formatting. Adding license headers. ACCUMULO-391
Adding the following:
- Deprecation to InputConfigurator, mapred.InputFormatBase, mapreduce.InputFormatBase
- Comments to TableQueryConfig
- Multi-table support to mapred.InputFormatBase

ACCUMULO-391