Skip to content
New issue

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

Decat BigQuery INVALID_ARGUMENT #61

Closed
troyraen opened this issue May 10, 2021 · 1 comment
Closed

Decat BigQuery INVALID_ARGUMENT #61

troyraen opened this issue May 10, 2021 · 1 comment
Labels
Bug Something isn't working

Comments

@troyraen
Copy link
Collaborator

troyraen commented May 10, 2021

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.

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)

  • changing the schema to allow a null mag
  • changing the BQ upload retry strategy to RETRY_NEVER
@troyraen troyraen added the Bug Something isn't working label May 10, 2021
@troyraen troyraen changed the title Decat mag is NaN -> BigQuery INVALID_ARGUMENT Decat BigQuery INVALID_ARGUMENT May 11, 2021
@troyraen troyraen mentioned this issue May 11, 2021
@troyraen troyraen added this to Backlog in Broker Pipeline Nov 22, 2021
@troyraen
Copy link
Collaborator Author

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.

Broker Pipeline automation moved this from Backlog to Closed Nov 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Development

No branches or pull requests

1 participant