Is this your first time deploying Airbyte?: Yes
OS Version / Instance: Windows
Memory / Disk:
Deployment: Docker
Airbyte Version: 0.42.0
Source name/version: Netsuite 0.1.3
Destination name/version: Snowflake 0.4.63
Step: Fetching schema of data source
Description: I am able to configure the Netsuite connector with my credentials and pass the initial test, but when I try to connect the source to a destination I keep getting the following “Failed to fetch schema: non json response” message with no other detail or logs:
I am wondering if I am experiencing something similar to the github issue outlined here
opened 10:26PM - 14 Apr 23 UTC
type/bug
community
needs-triage
team/use
autoteam
**Description**
I am experiencing an issue with the Airbyte NetSuite connecto… r while trying to fetch the schema without specifying any object types in Airbyte v0.45.8, which is the latest version available via the Helm package, as well as in previous versions. It appears that the connector does not wait long enough for the NetSuite `metadata-catalog` API to respond, causing the fetch schema operation to fail. The API's response time is around 98.437 seconds. This issue occurs when connecting the NetSuite source connector to any destination connector (e.g., e2e, S3, etc.).
**Steps to reproduce the issue**
1. Install Airbyte v0.45.8 or earlier using the Helm package.
2. Set up the NetSuite connector in Airbyte with the required credentials and configurations.
3. Connect the NetSuite source connector to any destination connector (e.g., e2e, S3, etc.) without specifying any object types.
4. Attempt to fetch the schema for the configured NetSuite objects.
5. Observe that the fetch schema operation times out before receiving a response from the NetSuite `metadata-catalog` API, which takes around 98.437 seconds to respond.
**Expected behavior**
The Airbyte NetSuite connector should wait for a sufficient amount of time for the NetSuite `metadata-catalog` API to respond, allowing the fetch schema operation to complete successfully and enabling the proper configuration of the data pipeline between the NetSuite source and destination connectors.
**Additional context**
This issue is causing difficulties in setting up and configuring the NetSuite connector in Airbyte, as the schema information is essential for proper data extraction and syncing with destination connectors, even without specifying any object types. The problem persists across multiple versions of Airbyte, including the latest version available via the Helm package (v0.45.8) and earlier versions.
Follow the Images showing the response time in NetSuite and how airbyte looks after the complete response in NetSuite.
I kindly request the Airbyte maintainers to investigate this issue and provide a solution that allows sufficient time for the NetSuite `metadata-catalog` API to respond during the fetch schema operation, ensuring seamless integration between the NetSuite source connector and various destination connectors without specifying object types, in both the latest version and previous versions of Airbyte.
Thank you for your attention to this matter.
, but I can’t tell for sure. Any help would be much appreciated.
RESOLVED: we fixed this by specifying the objects we want to pull in the source configs.
