We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INVALID_ARGUMENT
View the error in GCP Console
"error": { "code": 400, "message": "Invalid JSON payload received. Unexpected token.\n15757751465, \"mag\": NaN, \"magerr\": -0.83\n ^", "errors": [ { "message": "Invalid JSON payload received. Unexpected token.\n15757751465, \"mag\": NaN, \"magerr\": -0.83\n ^", "domain": "global", "reason": "parseError" } ], "status": "INVALID_ARGUMENT" }
It appears that alerts are coming in with mag=NaN. Need to log some things (objectId's) and download alerts with problems.
mag=NaN
This is producing a lot of errors in the bq_sink Dataflow job, and is preventing it from draining properly.
bq_sink
I have tried (without success)
mag
RETRY_NEVER
The text was updated successfully, but these errors were encountered:
NaN is not valid JSON. In the future, we should probably encode these as Null, but see here for several options, and look into what BigQuery allows.
Decat is over, and we don't use Dataflow anymore. Closing the issue.
Sorry, something went wrong.
No branches or pull requests
View the error in GCP Console
It appears that alerts are coming in with
mag=NaN
. Need to log some things (objectId's) and download alerts with problems.This is producing a lot of errors in the
bq_sink
Dataflow job, and is preventing it from draining properly.I have tried (without success)
mag
RETRY_NEVER
The text was updated successfully, but these errors were encountered: