[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[ https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623517#comment-15623517 ] Thejas M Nair commented on HIVE-15062: -- [~sershe] Thanks for clarifying (offline) that this config is settable from the client because it has been added to HiveConf.metaConfVars. +1 > create backward compat checking for metastore APIs > -- > > Key: HIVE-15062 > URL: https://issues.apache.org/jira/browse/HIVE-15062 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch, > HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.03.nogen.patch, > HIVE-15062.03.patch, HIVE-15062.04.nogen.patch, HIVE-15062.04.patch, > HIVE-15062.nogen.patch, HIVE-15062.patch > > > This is to add client capability checking to Hive metastore. > This could have been used, for example, when introducing ACID tables - a > client trying to get_table on such a table without specifying that it is > aware of ACID tables would get an error by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[ https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623336#comment-15623336 ] Sergey Shelukhin commented on HIVE-15062: - Thanks for the feedback. I have added the usage guidelines in the exception text; the setting is also settable from the client (added that to the error message now), so such tools should be able to set it per session. I don't think there's a way around this for external tools - at worst, they will have to disable this globally, which is no worse than the current situation, or they can disable it per session. However, we would have proper handling for different versions of Hive, such as in heterogeneous clusters and for rolling upgrade. > create backward compat checking for metastore APIs > -- > > Key: HIVE-15062 > URL: https://issues.apache.org/jira/browse/HIVE-15062 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch, > HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.03.nogen.patch, > HIVE-15062.03.patch, HIVE-15062.nogen.patch, HIVE-15062.patch > > > This is to add client capability checking to Hive metastore. > This could have been used, for example, when introducing ACID tables - a > client trying to get_table on such a table without specifying that it is > aware of ACID tables would get an error by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15616849#comment-15616849
]
Sushanth Sowmyan commented on HIVE-15062:
-
I like the fundamental idea, and I think this makes sense. I would suggest a
couple of things, though.
a) checkClient is not really handling "checking" client compatibility. Instead,
it is instead acting as a gating assert for entering sections of code where we
make an assumption that feature exists. I think that an api style that did the
following would be more usable:
{code}
private boolean checkClientCompatible(ClientCapabilities capabilities,
ClientCapability value, String what, String call) {
// return true if compatible, false, if not. Simply test, no more.
...
}
private boolean assertClientCompatible(ClientCapabilities capabilities,
ClientCapability value, String what, String call) throws
MetaException {
if (!checkClientCompatible(capabilities, value, what, call) {
// throw exception similar to existing checkClient
}
}
{code}
Then, this allows us to assert that something should be compatible if it
requires it, and allows us to write backward compatible code if possible by
checking capability.
Also, I would advise cautionary use of the capabilities notion, since the
metastore api is a public api (also, the HCatClient api that sits on top of
this), and thus, all manners of tools use it, not just hive. For eg., in the
example you use, of ACID tables not being visible, or worse, erroring out if a
user has their capabilities as null, this will then break other tools written
against the metastore api, such as tools that do a UI display of the warehouse
(data explorers/etc), or will break existing wh management tools which set
table properties for expiry/cleanup, etc.
Thus, while this is a useful capability, the possibility for accidental misuse
leading to breaking backward compatibility is high. I would still like this to
be introduced, however, but maybe with more documented warnings on usage, about
why one must be careful of implementing this?
> create backward compat checking for metastore APIs
> --
>
> Key: HIVE-15062
> URL: https://issues.apache.org/jira/browse/HIVE-15062
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch,
> HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.03.nogen.patch,
> HIVE-15062.03.patch, HIVE-15062.nogen.patch, HIVE-15062.patch
>
>
> This is to add client capability checking to Hive metastore.
> This could have been used, for example, when introducing ACID tables - a
> client trying to get_table on such a table without specifying that it is
> aware of ACID tables would get an error by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[ https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15616619#comment-15616619 ] Sergey Shelukhin commented on HIVE-15062: - Known flaky tests for Spark, and for explain - https://issues.apache.org/jira/browse/HIVE-15084 The Druid test fails on master for me too - filed https://issues.apache.org/jira/browse/HIVE-15095 [~thejas] does the patch make sense now? > create backward compat checking for metastore APIs > -- > > Key: HIVE-15062 > URL: https://issues.apache.org/jira/browse/HIVE-15062 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch, > HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.03.nogen.patch, > HIVE-15062.03.patch, HIVE-15062.nogen.patch, HIVE-15062.patch > > > This is to add client capability checking to Hive metastore. > This could have been used, for example, when introducing ACID tables - a > client trying to get_table on such a table without specifying that it is > aware of ACID tables would get an error by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15616530#comment-15616530
]
Hive QA commented on HIVE-15062:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835862/HIVE-15062.03.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 10626 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_2]
(batchId=91)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_4]
(batchId=91)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_5]
(batchId=90)
org.apache.hadoop.hive.druid.TestHiveDruidQueryBasedInputFormat.testCreateSplitsIntervals
(batchId=229)
org.apache.hive.spark.client.TestSparkClient.testJobSubmission (batchId=272)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1868/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1868/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-1868/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 5 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12835862 - PreCommit-HIVE-Build
> create backward compat checking for metastore APIs
> --
>
> Key: HIVE-15062
> URL: https://issues.apache.org/jira/browse/HIVE-15062
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch,
> HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.03.nogen.patch,
> HIVE-15062.03.patch, HIVE-15062.nogen.patch, HIVE-15062.patch
>
>
> This is to add client capability checking to Hive metastore.
> This could have been used, for example, when introducing ACID tables - a
> client trying to get_table on such a table without specifying that it is
> aware of ACID tables would get an error by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[ https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15616248#comment-15616248 ] Sergey Shelukhin commented on HIVE-15062: - [~thejas] tested it locally by writing to file, removing the value, rebuilding and reading the file; the unknown value is simply converted to null. It may break in the cases where the enum field is required, but it is ok for lists. > create backward compat checking for metastore APIs > -- > > Key: HIVE-15062 > URL: https://issues.apache.org/jira/browse/HIVE-15062 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch, > HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.nogen.patch, > HIVE-15062.patch > > > This is to add client capability checking to Hive metastore. > This could have been used, for example, when introducing ACID tables - a > client trying to get_table on such a table without specifying that it is > aware of ACID tables would get an error by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[ https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613488#comment-15613488 ] Thejas M Nair commented on HIVE-15062: -- Some notes on the feature after discussion with Sergey * The current api would call the new API will NULL for the capabilities * This give an error only if the table being accessed has additional capabilities that client should have to be able to access the data correctly. [~sershe] * Enum have been causing issues in HiveServer2. See HIVE-6050 * Call the current VERSION capability NULL_VERSION or so ? > create backward compat checking for metastore APIs > -- > > Key: HIVE-15062 > URL: https://issues.apache.org/jira/browse/HIVE-15062 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch, > HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.nogen.patch, > HIVE-15062.patch > > > This is to add client capability checking to Hive metastore. > This could have been used, for example, when introducing ACID tables - a > client trying to get_table on such a table without specifying that it is > aware of ACID tables would get an error by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610226#comment-15610226
]
Siddharth Seth commented on HIVE-15062:
---
[~sershe] - if you're referring to the following
{code}
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver[hbase_bulk]
(batchId=89)
{code}
There's already a flaky test jira for this under
https://issues.apache.org/jira/browse/HIVE-15058. (That's tracking currently
known flaky tests to make it a little easier to analyze ptest reports, cite
jiras, and commit). Of course if you have an idea on how this test can be
fixed, that would be awesome. (Looks like you know more than anyone else on
what is going on with the test :))
This specific failure, I think we should just disable, it fails often enough to
not be useful.
> create backward compat checking for metastore APIs
> --
>
> Key: HIVE-15062
> URL: https://issues.apache.org/jira/browse/HIVE-15062
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch,
> HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.nogen.patch,
> HIVE-15062.patch
>
>
> This is to add client capability checking to Hive metastore.
> This could have been used, for example, when introducing ACID tables - a
> client trying to get_table on such a table without specifying that it is
> aware of ACID tables would get an error by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[ https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610020#comment-15610020 ] Sergey Shelukhin commented on HIVE-15062: - The HBase test seems to have failed due to some issues w/the cluster, there are a lot of ZK ConnectionLoss/transient errors. I will try locally.. [~sseth] what do we do with such failures? > create backward compat checking for metastore APIs > -- > > Key: HIVE-15062 > URL: https://issues.apache.org/jira/browse/HIVE-15062 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch, > HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.nogen.patch, > HIVE-15062.patch > > > This is to add client capability checking to Hive metastore. > This could have been used, for example, when introducing ACID tables - a > client trying to get_table on such a table without specifying that it is > aware of ACID tables would get an error by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610005#comment-15610005
]
Hive QA commented on HIVE-15062:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835406/HIVE-15062.02.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 10621 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver[hbase_bulk]
(batchId=89)
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJarWithoutAddDriverClazz[0]
(batchId=164)
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[0] (batchId=164)
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[1] (batchId=164)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1830/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1830/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-1830/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 4 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12835406 - PreCommit-HIVE-Build
> create backward compat checking for metastore APIs
> --
>
> Key: HIVE-15062
> URL: https://issues.apache.org/jira/browse/HIVE-15062
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-15062.01.nogen.patch, HIVE-15062.01.patch,
> HIVE-15062.02.nogen.patch, HIVE-15062.02.patch, HIVE-15062.nogen.patch,
> HIVE-15062.patch
>
>
> This is to add client capability checking to Hive metastore.
> This could have been used, for example, when introducing ACID tables - a
> client trying to get_table on such a table without specifying that it is
> aware of ACID tables would get an error by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607442#comment-15607442
]
Hive QA commented on HIVE-15062:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835245/HIVE-15062.01.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 141 failed/errored test(s), 10621 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver[hbase_bulk]
(batchId=89)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testAlterPartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testAlterTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testAlterViewParititon
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testColumnStatistics
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testComplexTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testComplexTypeApi
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testConcurrentMetastores
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDBOwner
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDBOwnerChange
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDatabase
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDatabaseLocation
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDatabaseLocationWithPermissionProblems
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDropTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testFilterLastPartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testFilterSinglePartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testFunctionWithResources
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testGetConfigValue
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testGetTableObjects
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testListPartitionNames
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testListPartitions
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testListPartitionsWihtLimitEnabled
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testNameMethods
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testPartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testPartitionFilter
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testRenamePartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSimpleFunction
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSimpleTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSimpleTypeApi
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testStatsFastTrivial
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSynchronized
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testTableDatabase
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testTableFilter
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testTransactionalValidation
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testValidateTableCols
(batchId=193)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testAlterPartition
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testAlterTable
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testAlterViewParititon
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testColumnStatistics
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testComplexTable
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testComplexTypeApi
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testConcurrentMetastores
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testDBOwner
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testDBOwnerChange
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testDatabase
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testDatabaseLocation
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testDatabaseLocationWithPermissionProblems
(batchId=189)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[
https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607111#comment-15607111
]
Hive QA commented on HIVE-15062:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835222/HIVE-15062.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 202 failed/errored test(s), 10466 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.metastore.TestFilterHooks.testDefaultFilter (batchId=188)
org.apache.hadoop.hive.metastore.TestFilterHooks.testDummyFilterForDb
(batchId=188)
org.apache.hadoop.hive.metastore.TestFilterHooks.testDummyFilterForIndex
(batchId=188)
org.apache.hadoop.hive.metastore.TestFilterHooks.testDummyFilterForPartition
(batchId=188)
org.apache.hadoop.hive.metastore.TestFilterHooks.testDummyFilterForTables
(batchId=188)
org.apache.hadoop.hive.metastore.TestHiveMetaTool.testExecuteJDOQL (batchId=200)
org.apache.hadoop.hive.metastore.TestHiveMetaTool.testListFSRoot (batchId=200)
org.apache.hadoop.hive.metastore.TestHiveMetaTool.testUpdateFSRootLocation
(batchId=200)
org.apache.hadoop.hive.metastore.TestMetaStoreEventListener.testListener
(batchId=195)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testAlterPartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testAlterTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testAlterViewParititon
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testColumnStatistics
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testComplexTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testComplexTypeApi
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testConcurrentMetastores
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDBOwner
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDBOwnerChange
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDatabase
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDatabaseLocation
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDatabaseLocationWithPermissionProblems
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testDropTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testFilterLastPartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testFilterSinglePartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testFunctionWithResources
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testGetConfigValue
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testGetTableObjects
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testListPartitionNames
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testListPartitions
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testListPartitionsWihtLimitEnabled
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testNameMethods
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testPartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testPartitionFilter
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testRenamePartition
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSimpleFunction
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSimpleTable
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSimpleTypeApi
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testStatsFastTrivial
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testSynchronized
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testTableDatabase
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testTableFilter
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testTransactionalValidation
(batchId=193)
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testValidateTableCols
(batchId=193)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testAlterPartition
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testAlterTable
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testAlterViewParititon
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testColumnStatistics
(batchId=189)
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testComplexTable
(batchId=189)
[jira] [Commented] (HIVE-15062) create backward compat checking for metastore APIs
[ https://issues.apache.org/jira/browse/HIVE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15606771#comment-15606771 ] Sergey Shelukhin commented on HIVE-15062: - [~sushanth] [~ashutoshc] can you take a look? > create backward compat checking for metastore APIs > -- > > Key: HIVE-15062 > URL: https://issues.apache.org/jira/browse/HIVE-15062 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: HIVE-15062.nogen.patch, HIVE-15062.patch > > > This is to add client capability checking to Hive metastore. > This could be used, for example, when introducing ACID tables - a client > trying to get_table on such a table without specifying that it is aware of > ACID tables would get an error by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
