Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are a few questions here:</p> <ul> <li><p><strong>Why did my load job fail?</strong> Just to check, was that the entire request you sent? If so, it looks like there's no data to be loaded, i.e. <code>sourceUris</code> is empty. If so, that's the problem, and we're apparently returning the world's worst error message.</p></li> <li><p><strong>Why the numeric project ID?</strong> BigQuery uses the project name and the associated numeric ID interchangeably, so all you're seeing is that we tend to convert project names to IDs on the way in. Just to confirm, if you visit the <a href="https://code.google.com/apis/console/" rel="nofollow">Google APIs Console</a> and look up your project, do you see that same numeric ID in the url?</p></li> <li><p><strong>Why does the project ID get specified in multiple places?</strong> First, it seems that you specified the project ID as a top-level attribute in the job; that shouldn't be necessary. (I suspect that it simply overrides whatever project ID you specify in the job reference itself.) That leaves two locations -- once as part of the job reference and the other as part of the table reference. These actually signify two different things -- the one in the job specifies what project you're inserting a job into, i.e. who's paying for the job, and the one in the table specifies what project the resulting table lives in, i.e. who owns the resulting data. In general, these will be the same, but the API allows them to be distinct. (This could be useful if, for example, you built a service that needed to insert data into tables ultimately owned by customers.)</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload