[
https://issues.apache.org/jira/browse/HIVE-26123?focusedWorklogId=755138&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-755138
]
ASF GitHub Bot logged work on HIVE-26123:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Apr/22 09:09
Start Date: 11/Apr/22 09:09
Worklog Time Spent: 10m
Work Description: kgyrtkirk commented on PR #3196:
URL: https://github.com/apache/hive/pull/3196#issuecomment-1094773625
I really don't like to grow the number of core cli test drivers; why do we
need separate for oracle/etc?
can't we use a qoption instead of a whole set of new drivers?
I wonder if we really need to have mile long q.out results for these kind of
things.
I think these kind of things should be run as part of some automated smoke
tests for the release - with a real installation undernteath
Issue Time Tracking
-------------------
Worklog Id: (was: 755138)
Time Spent: 40m (was: 0.5h)
> Introduce test coverage for sysdb for the different metastores
> --------------------------------------------------------------
>
> Key: HIVE-26123
> URL: https://issues.apache.org/jira/browse/HIVE-26123
> Project: Hive
> Issue Type: Test
> Components: Testing Infrastructure
> Affects Versions: 4.0.0-alpha-2
> Reporter: Alessandro Solimando
> Assignee: Alessandro Solimando
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> _sydb_ exposes (some of) the metastore tables from Hive via JDBC queries.
> Existing tests are running only against Derby, meaning that any change
> against sysdb query mapping is not covered by CI.
> The present ticket aims at bridging this gap by introducing test coverage for
> the different supported metastore for sydb.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
