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

ESB Google BigQuery Connector 1.0.9: JSON to String converting issue #2369

Closed
veneerac opened this issue Jan 9, 2024 · 0 comments · Fixed by wso2-extensions/mi-connector-bigquery#35

Comments

@veneerac
Copy link

veneerac commented Jan 9, 2024

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

GDLMadushanka added a commit to GDLMadushanka/esb-connector-bigquery that referenced this issue Jan 10, 2024
Remove the usage of constructDataRow method which introduce unnecessary
escaping to the JSON payloads.
Fixes wso2/api-manager/issues/2369
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant