[
https://issues.apache.org/jira/browse/HIVE-28498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907806#comment-17907806
]
Ayush Saxena edited comment on HIVE-28498 at 12/23/24 9:34 AM:
---------------------------------------------------------------
JDO is usually a fallback after DirectSql. Maybe the DirectSql would have
failed for that query for whatever reason & Hive doesn't fail if DirectSql
fails, it fallbacks to JDO
Whatever though this behaviour doesn't look correct, both JDO & DirectSql
should throw exception, rather than one throwing the exception & other
returning the wrong result, the JDO behaviour seems correct, something messy at
the DirectSql layer I believe
was (Author: ayushtkn):
JDO is usually a fallback after DirectSql. Maybe the DirectSql would have
failed for that query for whatever reason & Hive doesn't fail if DirectSql
fails, it fallbacks to JDO
> Missing column handling of get_table_statistics_req is inconsistent
> -------------------------------------------------------------------
>
> Key: HIVE-28498
> URL: https://issues.apache.org/jira/browse/HIVE-28498
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Csaba Ringhofer
> Priority: Major
> Labels: hive-4.1.0-must
>
> When get_table_statistics_req is asked for a column that doesn't exist in HMS:
> if hive.metastore.try.direct.sql=false: exception is thrown
> if hive.metastore.try.direct.sql=true: most of the time the RPC succeeds and
> returns stats for the columns that exist
> This was found when investigating some flaky test in Apache Impala
> (IMPALA-11431). hive.metastore.try.direct.sql=true in the Impala test env,
> so most of the time these RPCs succeeded, but in some cases HMS uses JDO
> during the RPC and an exception is thrown. I don't know the reason behind
> sporadically using JDO instead of direct SQL.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
