[
https://issues.apache.org/jira/browse/HIVE-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Flatley updated HIVE-1625:
-------------------------------
Status: Patch Available (was: Open)
Release Note:
We implemented several HivePreparedStatement methods for setting parameters.
The class also builds sql based on the parameters. The classes' setNull
methods have been implemented as well.
Requesting a contribution code review.
Our unit tests check to see if the "built" sql from the parameter values are
correct. We have experienced problems with "where" clauses in prepared
statements that are run against the standalone database used in the unit tests.
We have not experience this problem when running the JDBC driver with our
products against our development Hive server.
I will browse Jira for a case on this. If not found I will create a
reproduction path and create an issue.
> Added implementation to HivePreparedStatement, HiveBaseResultSet and
> HiveQueryResultSet.
> ----------------------------------------------------------------------------------------
>
> Key: HIVE-1625
> URL: https://issues.apache.org/jira/browse/HIVE-1625
> Project: Hadoop Hive
> Issue Type: Improvement
> Reporter: Sean Flatley
> Assignee: Sean Flatley
> Attachments: changelog.txt, HIVE-1625.patch, testJdbcDriver.log
>
>
> We implemented several of the HivePreparedStatement set methods, such as
> setString(int, String) and the means to substitute place holders in the SQL
> with the values set.
> HiveQueryResultSet and HiveBaseResultSet were enhanced so that getStatement()
> could be implemented.
> See attached change log for details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
