[DOP-15764] Remove fetchsize from JDBCWriteOptions #288
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
Currently
JDBC.WriteOptions
havefetchsize
option. This should not be the case.Instead of inheriting
JDBC.ReadOptions
,JDBC.SQLOptions
andJDBC.WriteOptions from legacy
JDBC.JDBCOptions, inherit them from
GenericOptions. Copy
query_timeout` to both of these classes, as Spark can accept this option in both read and write operations.Related issue number
Checklist
docs/changelog/next_release/<pull request or issue id>.<change type>.rst
file added describing change(see CONTRIBUTING.rst for details.)