Initial checkin of a service skeleton
The routing table itself
Set up log4j
Add a package containing wire-models for communicating with the client
Handle uncaught exceptions as internal errors.

Have to do a little dance to ensure that it's done as lazily as possible.
Bring the DatasetDAO and ColumnDAO interfaces in from the old system

At the point where, hopefully, things can start being brought in
piecewise.
Put closely-related services in the same resource objects
Bring in DataCoordinatorClient
Can now create (columnless) datasets
Only send internal error message if the response isn't yet committed
Store columns on create, plus names and descriptions
De-Try the stores

Because if they ever throw an exception it's just going to internal-error
anyway.  Keeping it in Trys left the possibility of silently swallowing
exceptions.
Get dataset schema endpoint
Actually *use* the created liveness checker
Add a timeout for connecting to the data-coordinator
Check that configured durations fit in an int
Query coordinator client
Prepare for multiple data-coordinator instances
Simple querying

At this point the good-path works, as long as the result fits in memory.
You still can't upsert though -- the only way to get data in is to create
a dataset with soda-fountain, then publish-upsert-secondarize by talking
straight to the data-coordinator.  Once it's there in the secondary, though,
it works.

Errors aren't translated.
Temporary hack: hardcode the names and types of system columns