[
https://issues.apache.org/jira/browse/HIVE-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652550#comment-13652550
]
Carl Steinbach commented on HIVE-4498:
--------------------------------------
bq. Since we've disabled BeeLine tests I guess we can disable this one too?
No, I think it would be better to fix TestBeeLineWithArgs (which isn't actually
broken), and re-enable a comprehensive subset of the other HiveServer2 tests,
unless of course the plan is to let HiveServer2 rot until it's completely
broken.
TestBeeLineWithArgs was committed in HIVE-4268, but it wasn't enabled until I
committed HIVE-4497 the other day. HIVE-4356 was committed in between, and
that's the actual source of the bug.
Gunther, can you please take a look at this? Thanks.
> TestBeeLineWithArgs.testPositiveScriptFile fails
> ------------------------------------------------
>
> Key: HIVE-4498
> URL: https://issues.apache.org/jira/browse/HIVE-4498
> Project: Hive
> Issue Type: Bug
> Components: CLI, HiveServer2, JDBC
> Reporter: Thejas M Nair
>
> TestBeeLineWithArgs.testPositiveScriptFile fails -
> {code}
> [junit] 0: jdbc:hive2://localhost:10000> >>> STARTED
> testBreakOnErrorScriptFile
> [junit] Output: Connecting to jdbc:hive2://localhost:10000
> [junit] Connected to: Hive (version 0.12.0-SNAPSHOT)
> [junit] Driver: Hive (version 0.12.0-SNAPSHOT)
> [junit] Transaction isolation: TRANSACTION_REPEATABLE_READ
> [junit] Beeline version 0.12.0-SNAPSHOT by Apache Hive
> [junit] +----------------+
> [junit] | database_name |
> [junit] +----------------+
> [junit] +----------------+
> [junit] No rows selected (0.899 seconds)
> [junit] Closing: org.apache.hive.jdbc.HiveConnection
> [junit]
> [junit] >>> FAILED testPositiveScriptFile (ERROR) (2s)
> {code}
--
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
