Parameter Optimization - enable JDBC to cache parameters in session instead of resultset

Open sfc-gh-mknister opened this issue 2 years ago • 2 comments

Overview

These are the JDBC changes needed to support the HTAP parameter optimization.

Params are now cached in session instead of ResultSet objects. Schema/db/warehouse are only updated when values from server are non-null.

SNOW-XXXXX

External contributors - please answer these questions before submitting a pull request. Thanks!

Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR adressing? Make sure that there is an accompanying issue to your PR.

Fixes #NNNN
Fill out the following pre-review checklist:
- [ ] I am adding a new automated test(s) to verify correctness of my new code
- [ ] I am adding new logging messages
- [ ] I am modyfying authorization mechanisms
- [ ] I am adding new credentials
- [ ] I am modyfying OCSP code
- [ ] I am adding a new dependency
Please describe how your code solves the related issue.

Please write a short description of how your code change solves the related issue.

Pre-review checklist

[ ] This change has passed precommit
[ ] I have reviewed code coverage report for my PR in (Sonarqube)

Oct 13 '22 21:10 sfc-gh-mknister

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

_{You can retrigger this bot by commenting recheck in this Pull Request}