bharath v created IMPALA-7615:
---------------------------------
Summary: Partition metadata mismatch should be handled gracefully
in local catalog mode.
Key: IMPALA-7615
URL: https://issues.apache.org/jira/browse/IMPALA-7615
Project: IMPALA
Issue Type: Improvement
Components: Frontend
Affects Versions: Impala 3.1.0
Reporter: bharath v
*This is a Catalog v2 only improvement*
An RPC to fetch partition metadata for a partition ID that does not exist on
the Catalog server currently throws IAE.
{noformat}
@Override
public TGetPartialCatalogObjectResponse getPartialInfo(
TGetPartialCatalogObjectRequest req) throws TableLoadingException {
for (long partId : partIds) {
HdfsPartition part = partitionMap_.get(partId);
Preconditions.checkArgument(part != null, "Partition id %s does not
exist", <------
partId);
TPartialPartitionInfo partInfo = new TPartialPartitionInfo(partId);
if (req.table_info_selector.want_partition_names) {
partInfo.setName(part.getPartitionName());
}
if (req.table_info_selector.want_partition_metadata) {
partInfo.hms_partition = part.toHmsPartition();
{noformat}
This is undesirable since such exceptions are not transparently retried in the
frontend. Instead we should fix this code path to throw
InconsistentMetadataException, similar to what we do for other code paths that
handle such inconsistent metadata like version changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
