Yes, there is a way to limit the max fetch size of AdaptiveStreamingQueryConfig in Airbyte. This is done dynamically during the data extraction process. The fetch size is adjusted based on the available memory limit and the JDBC buffer size. This is part of Airbyte's adaptive streaming feature which is designed to optimize the data extraction process and prevent memory overflow issues. However, please note that this process is handled internally by Airbyte and may not be directly configurable by the user. If you are experiencing issues with the fetch size or data extraction process, it may be helpful to check the logs for any error messages or warnings related to the AdaptiveStreamingQueryConfig. Here are some references from the knowledge sources that discuss this feature: - [Github Issue (open): Source Mysql: syncing timeout (fetch size may be ignored)](https://github.com/airbytehq/airbyte/issues/9784) - [Github Issue (closed): Destination Weaviate: Postrgres to Weaviate sync failed almost at the end: readFromDestination: exception caught](https://github.com/airbytehq/airbyte/issues/31949) - [Forum Post: Re-build a connector](https://discuss.airbyte.io/t/952) - [Forum Post: Initial Loading a large data set](https://discuss.airbyte.io/t/1563) If you need further assistance, please consider reaching out to the Airbyte community or support team.