[
https://issues.apache.org/jira/browse/HIVE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771659#comment-13771659
]
Phabricator commented on HIVE-5209:
-----------------------------------
thejas has commented on the revision "HIVE-5209 [jira] JDBC support for
varchar".
INLINE COMMENTS
jdbc/src/java/org/apache/hive/jdbc/HiveQueryResultSet.java:32 TableSchema was
used prior to this patch, but since the classes it uses have changed, it is
possible that there is a new dependency.
But if this patch isn't changing the situation, we can fix that separately.
I think the best next step would be to test what are the hive client
dependencies with and without the patch.
In a separate jira, I think we should start looking at creating a
service-core module that jdbc classes use, instead of having the whole service
module which includes the server pieces as a dependency.
REVISION DETAIL
https://reviews.facebook.net/D12999
To: JIRA, jdere
Cc: cwsteinbach, thejas
> JDBC support for varchar
> ------------------------
>
> Key: HIVE-5209
> URL: https://issues.apache.org/jira/browse/HIVE-5209
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2, JDBC, Types
> Reporter: Jason Dere
> Assignee: Jason Dere
> Attachments: D12999.1.patch, HIVE-5209.1.patch, HIVE-5209.2.patch,
> HIVE-5209.4.patch, HIVE-5209.D12705.1.patch
>
>
> Support returning varchar length in result set metadata
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
