You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set up a Google BigQuery account and console as outlined in the documentation [2]. Please note that when following the API, use the access token and refresh token with the free-tier account. note that there are limitations in inserting data, but we can replicate the issue. Therefore, you can use the provided API and token for testing purposes.
Steps to Reproduce
Step [01]:
Upload the BigQuery connector to the EI UI console and deploy the following API.
Invoke the API using the Nested JASON array payload
Enable the wire logs, and you'll observe that after the connector processes the payload, it is sent as a string. Google BigQuery schema should accept the JSON payload for BigQuery.
Description
Set up a Google BigQuery account and console as outlined in the documentation [2]. Please note that when following the API, use the access token and refresh token with the free-tier account. note that there are limitations in inserting data, but we can replicate the issue. Therefore, you can use the provided API and token for testing purposes.
Steps to Reproduce
Step [01]:
Upload the BigQuery connector to the EI UI console and deploy the following API.
bigquery-testAPI.zip
Step [02]
Invoke the API using the Nested JASON array payload
Enable the wire logs, and you'll observe that after the connector processes the payload, it is sent as a string. Google BigQuery schema should accept the JSON payload for BigQuery.
[1] https://store.wso2.com/store/assets/esbconnector/list?q=%22_default%22%3A%22bigquery%22
[2] https://ei.docs.wso2.com/en/latest/micro-integrator/references/connectors/bigquery-connector/bigquery-connector-example/
Affected Component
MI
Version
BigQuery connector
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: