@kapa.ai Attempt 0 to call to write discover schema result

The error message "Attempt 0 to call to write discover schema result" indicates that there was an attempt to write the discovered schema result, but it encountered an issue. This is a common problem when dealing with large schemas or network issues. Here are some relevant insights and potential solutions based on the provided knowledge sources: ### Common Issues and Solutions 1. Large Schema Size: - If the schema is too large, you might encounter a

413 - Request Entity Too Large

error. This is because the content length exceeds the maximum allowed content length. - Example from the knowledge source:

plaintext      writeDiscoverCatalogResult call failed with: 413 - {"message":"Request Entity Too Large","_links":{"self":{"href":"/api/v1/sources/write_discover_catalog_result","templated":false}},"_embedded":{"errors":[{"message":"The content length [49287161] exceeds the maximum allowed content length [10485760]"}]}}

- Solution: Consider breaking down the schema into smaller parts or increasing the allowed content length if possible. 2. Network Issues: - Network issues can cause the API call to fail with errors like

java.io.IOException: HTTP/1.1 header parser received no bytes

. - Example from the knowledge source:

plaintext      io.airbyte.api.client.invoker.generated.ApiException: java.io.IOException: HTTP/1.1 header parser received no bytes

- Solution: Ensure that your network connection is stable. You might also want to retry the operation or check if there are any network configurations that need adjustment. 3. Specific Database Issues: - For certain databases like PostgreSQL, the discovery process might fail if there are too many schemas or large tables. - Example from the knowledge source:

plaintext      For context, the Postgres DB I’m connecting to has 9 schemas, 24 tables, with the largest table being 125MB (1.4M rows). Excluding the schema with that table doesn’t seem to have any effect.

- Solution: Try limiting the discovery to specific schemas or tables that are smaller in size. For instance, focusing on the "public" schema only worked for one user:

plaintext      I’ve tried changing the source setup to the “public” schema only, and it works!!!

### Additional Resources - If you continue to face issues, you might want to check the [Airbyte documentation](https://docs.airbyte.com) for more detailed troubleshooting steps or consider reaching out to the Airbyte community for support. By addressing these common issues, you should be able to resolve the problem with writing the discover schema result. If you need further assistance, please provide more details about your specific setup and the errors you are encountering.