Skip to content

Conversation

@msrathore-db
Copy link
Contributor

Description

Added support for the connection param of maxBytesPerFetchRequest. The parameter is used for direct results as well.
PECO-2734

@github-actions github-actions bot added this to the ADBC Libraries 21 milestone Sep 24, 2025
@msrathore-db msrathore-db changed the title Added support for connection param of maxBytesPerFetchRequest feat(csharp/src/drivers/Databricks): Added support for connection param of maxBytesPerFetchRequest Sep 24, 2025
@msrathore-db msrathore-db marked this pull request as draft September 24, 2025 05:06
@CurtHagenlocher CurtHagenlocher changed the title feat(csharp/src/drivers/Databricks): Added support for connection param of maxBytesPerFetchRequest feat(csharp/src/Drivers/Databricks): Added support for connection param of maxBytesPerFetchRequest Sep 24, 2025
Copy link
Contributor

@CurtHagenlocher CurtHagenlocher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! In addition to the two specific comments I left, there's also the need to mollify the linter by cleaning up some whitespace and the desire to keep readme.md up-to-date with added options. (And again, the latter could be done as a separate PR.)

@CurtHagenlocher
Copy link
Contributor

If this is done, can you click "Ready for review"?

@msrathore-db msrathore-db marked this pull request as ready for review September 26, 2025 03:51
MaxBytes = 404857600
};

private const int DefaultMaxRowsPerFetchRequest = 1000;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why we set this to 1000? That is too small.
The OSS JDBC driver set to 2million for max rows and 404857600 for max bytes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was the default value being used earlier.
We'll hold this PR until we find the optimal default value based on perf analysis.

@msrathore-db msrathore-db marked this pull request as draft September 26, 2025 05:21
@msrathore-db msrathore-db marked this pull request as ready for review October 3, 2025 13:05
@eric-wang-1990
Copy link
Contributor

Change CloudFetch path as well?

TFetchResultsReq request = new TFetchResultsReq(_response.OperationHandle!, TFetchOrientation.FETCH_NEXT, _batchSize);

Copy link
Contributor

@CurtHagenlocher CurtHagenlocher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Changes look good. Let me know if you want to check-in as-is or if you want to follow up on Eric's comment and/or mine.

…e default value for maxBytesPerFetchRequest to 400MB. CloudFetch fetch request now uses maxBytesPerFetchRequest
@msrathore-db
Copy link
Contributor Author

Now that the changes are finalised, we can merge this PR.

@CurtHagenlocher CurtHagenlocher merged commit 0a84392 into apache:main Oct 6, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants