when enabling errors to bigquery I do not receive the bad record number <p>I'm using <a href="https://cloud.google.com/bigquery/bq-command-line-tool" rel="nofollow">bigquery command line tool</a> to upload these records:</p> <pre><code>{name: "a"} {name1: "b"} {name: "c"} </code></pre> <p>.</p> <pre><code>➜ ~ bq load --source_format=NEWLINE_DELIMITED_JSON my_dataset.my_table ./names.json </code></pre> <p>this is the result I get: </p> <pre><code>Upload complete. Waiting on bqjob_r7fc5650eb01d5fd4_000001560878b74e_1 ... (2s) Current status: DONE BigQuery error in load operation: Error processing job 'my_dataset:bqjob...4e_1': JSON table encountered too many errors, giving up. Rows: 2; errors: 1. Failure details: - JSON parsing error in row starting at position 5819 at file: file-00000000. No such field: name1. </code></pre> <p>when I use <code>bq --format=prettyjson show -j &lt;jobId&gt;</code> I get:</p> <pre><code> { "status": { "errorResult": { "location": "file-00000000", "message": "JSON table encountered too many errors, giving up. Rows: 2; errors: 1.", "reason": "invalid" }, "errors": [ { "location": "file-00000000", "message": "JSON table encountered too many errors, giving up. Rows: 2; errors: 1.", "reason": "invalid" }, { "message": "JSON parsing error in row starting at position 5819 at file: file-00000000. No such field: name1.", "reason": "invalid" } ], "state": "DONE" } } </code></pre> <p>As you can see I receive an error which tells me in what line I had an error. : <strong>Rows: 2; errors: 1</strong> </p> <p>Now I'm trying to enable errors by using <a href="https://cloud.google.com/bigquery/docs/reference/v2/jobs#configuration.load.maxBadRecords" rel="nofollow">max_bad_errors</a></p> <pre><code> ➜ ~ bq load --source_format=NEWLINE_DELIMITED_JSON --max_bad_records=3 my_dataset.my_table ./names.json </code></pre> <p>here is what I receive:</p> <pre><code>Upload complete. Waiting on bqjob_...ce1_1 ... (4s) Current status: DONE Warning encountered during job execution: JSON parsing error in row starting at position 5819 at file: file-00000000. No such field: name1. </code></pre> <p>when I use <code>bq --format=prettyjson show -j &lt;jobId&gt;</code> I get:</p> <pre><code>{ . . . "status": { "errors": [ { "message": "JSON parsing error in row starting at position 5819 at file: file-00000000. No such field: name1.", "reason": "invalid" } ], "state": "DONE" }, } </code></pre> <p>when I check - it actually uploads the good records to the table and ignores the bad record, </p> <p>but now I do not know in what record the error was.</p> <p>Is this a big query bug? can it be fixed so I receive record number also when enabling bad records?</p>