Add job for running queries

[tseaver]

Uses #1068 as a base.

[tseaver]

@dhermes Rebased after merge of #1068. PTAL.

[dhermes]

1. System test forthcoming?
2. Similarly, have you compared our BigQuery system tests to those in gcloud-node (I keep forgetting to bring this up, sorry if it's out of place here)
3. This all seems very vanilla / identical to existing. Is it worth have something more generic we can use (included generated tests for getters, setters and deleters, or just a generic subclass of property that we can test once)?
4. How close to "done" with BigQuery? (Cut release at that point?)

[dhermes]

Thanks for the tweaks. As for my other questions?

[tseaver]

System test forthcoming?

Yes, shortly.

Similarly, have you compared our BigQuery system tests to those in gcloud-node (I keep forgetting to bring this up, sorry if it's out of place here).

I've looked at them: we have similar coverage, except one missing for #1068.

This all seems very vanilla / identical to existing. Is it worth have something more generic we can use (included generated tests for getters, setters and deleters, or just a generic subclass of property that we can test once)?

We could bag the property/validation stuff, and just rely on docs for the user-settable configuration attributes. Or we could write a 'validating descriptor' helper and use that instead of custom property methods.

How close to "done" with BigQuery? (Cut release at that point?)

We don't have coverage for the /upload APIs (multipart/resumable, just like storage). And we're missing Client.list_jobs. Other than that, I think we're close.

[tseaver]

Rebased on top of #1075.

[dhermes]

Ping me when #1075 is in.

[tseaver]

@dhermes rebased after merge of #1075.

[dhermes]

LGTM