[ 
https://issues.apache.org/jira/browse/HIVE-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prafulla T updated HIVE-6992:
-----------------------------
    Status: Patch Available  (was: Open)

Description of changes in attached patch HIVE-6992.1.patch
HIVE-6992 - Support for PreparedStatement.getMetadata in hive-jdbc and server

This patch
1. Changes HiveSession/ICliService.executeStatement prototype to include two 
paramters.
   a. Boolean variable - prepareOnly to indicate if this execution request is 
only for preparing.
   b. existingOpHandle -  to execute prepared operation.
2. Changes TExecuteStatementReq to support above two parameters.
3. Changes SQLOperation.java to support separate preparation step.
4. Adds new OperationState called PREPARED to indicate prepared operation.
5. Refactors HiveStatement.java/HiveQueryResult to support retrieving of schema
   from HiveStatement.java.
6. Changes HiveJdbc class to support PreparedStatement.getMetadata

Also includes new (basic) unit-test for PreapredStatement.getMetadata
Test for executeStatement will be added later after initial code-review
I would like to know if my approach looks ok OR reviewers would like seperate
PreapreStatement API like ExecuteStatement


> Implement PreparedStatement.getMetaData(), getParmeterMetaData()
> ----------------------------------------------------------------
>
>                 Key: HIVE-6992
>                 URL: https://issues.apache.org/jira/browse/HIVE-6992
>             Project: Hive
>          Issue Type: Bug
>          Components: JDBC
>            Reporter: Bill Oliver
>
> It would be very helpful to have methods PreparedStatement.getMetaData() and 
> also PreparedStatement.getParameterMetaData() implemented.
> I especially would like PreparedStatmeent.getMetaData() implemented, as I 
> could prepare a SQL statement, and then get information about the result set, 
> as well as information that the query is valid.
> I am pretty sure this information is available in some form. When you do an 
> "EXPLAIN query", the explain operation shows information about the result set 
> including the column name/aliases and the column types.
> thanks you
> -bill



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to