GitHub user kevinsimard opened a pull request:
https://github.com/apache/hive/pull/164
Use setNull when null value is passed to preparedstatement setter
Not sure if I should open a ticket first but PreparedStatement setters are
failing when a null value is passed (the setString in my case). I changed the
other ones as well so they would have the same behavior.
A workaround solution is to use the setObject instead of setString but the
wrong setter might be used depending on the value's type which I want to avoid.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinsimard/hive master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/164.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #164
----
commit 4a81b3abe5c017a84ddb39708c41e9f0fe3b06e8
Author: Kevin Simard <kev.sim...@gmail.com>
Date: 2017-03-22T17:42:49Z
Use setNull when null value is passed to preparedstatement setter
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
