[
https://issues.apache.org/jira/browse/HIVE-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376509#comment-16376509
]
Vihang Karajgaonkar commented on HIVE-17580:
--------------------------------------------
I tried to run TestTablesCreateDropAlterTruncate locally and it seems to be
working fine. Is it
{code}
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running
org.apache.hadoop.hive.metastore.client.TestTablesCreateDropAlterTruncate
[INFO] Tests run: 114, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 136.29
s - in org.apache.hadoop.hive.metastore.client.TestTablesCreateDropAlterTruncate
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 114, Failures: 0, Errors: 0, Skipped: 0
{code}
Same with TestTablesList
{code}
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.hive.metastore.client.TestTablesList
[INFO] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.267
s - in org.apache.hadoop.hive.metastore.client.TestTablesList
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0
{code}
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[avro_decimal]
(batchId=95) is failing with a different error message now because metastore
validation does not do a strict range check for decimal precision and scale as
designed. The execution engine (hive) does the strict range check [1,38] and
since the precision is evaluated as 0 it fails. I don't fully understand the
test case though. I will update the q.out after checking with [~aihuaxu] who
wrote that test.
> Remove dependency of get_fields_with_environment_context API to serde
> ---------------------------------------------------------------------
>
> Key: HIVE-17580
> URL: https://issues.apache.org/jira/browse/HIVE-17580
> Project: Hive
> Issue Type: Sub-task
> Components: Standalone Metastore
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-17580.003-standalone-metastore.patch,
> HIVE-17580.04-standalone-metastore.patch,
> HIVE-17580.05-standalone-metastore.patch,
> HIVE-17580.06-standalone-metastore.patch,
> HIVE-17580.07-standalone-metastore.patch,
> HIVE-17580.08-standalone-metastore.patch,
> HIVE-17580.09-standalone-metastore.patch
>
>
> {{get_fields_with_environment_context}} metastore API uses {{Deserializer}}
> class to access the fields metadata for the cases where it is stored along
> with the data files (avro tables). The problem is Deserializer classes is
> defined in hive-serde module and in order to make metastore independent of
> Hive we will have to remove this dependency (atleast we should change it to
> runtime dependency instead of compile time).
> The other option is investigate if we can use SearchArgument to provide this
> functionality.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
