Allow creating tables with avro.schema.literal

[weijiii]

Description

This PR aims to address the following

• Add support for creating Avro-backed Hive table with avro.schema.literal.
• Add product tests to cover following cases
  1. Creating table by Hive with avro.schema.literal and querying from Trino (TestAvroSchemaLiteral)
  2. Creating table by Trino with avro.schema.literal and querying from Trino (TestAvroSchemaLiteral)
  3. Schema evolution on partitioned/non-partitioned tables with avro.schema.literal (Captured in BaseTestAvroSchemaEvolution)

Update also needed in https://github.com/trinodb/trino/blob/master/docs/src/main/sphinx/connector/hive.rst

Non-technical explanation

With this change, Trino users will be able to create Hive table using avro.schema.literal to define the schema.

Release notes

( ) This is not user-visible or docs only and no release notes are required.
(x) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: weijiii.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[weijiii]

Signed CLA sent via email.

[findepi]

Support avro schema literal

I thought we support avro schema literals for years. cc @anusudarsan
what does this PR do?

[weijiii]

Related: #5101
cc: @phd3

[findepi]

@weijiii can you suggest a more descriptive PR title?

[weijiii]

@weijiii can you suggest a more descriptive PR title?

@findepi
I should break this patch down to separate PRs.

The first commit is to make MetastoreUtil::getHiveSchema to also check the table-level storage descriptor for avro tables like Hive does.

The second commit is to allow Trino to use avro.schema.literal for avro tables.
The third commit is to use field schemas when the table/partition's SerDes does not use metastore for schema

I'd like to keep this PR for adding support for avro.schema.literal so I changed the title to such. I will also see if I can separate the logic of the latter 2 commits.

[weijiii]

The first commit is to make MetastoreUtil::getHiveSchema to also check the table-level storage descriptor for avro tables like Hive does.

#14463

[weijiii]

Previously failed test case TestHivePartitionSchemaEvolution#testOrc with config config-hdp3 is successful as I tested locally. I believe it is not related to this patch as the failure stems from a Hive execution.

[weijiii]

Failed test:

TestKuduConnectoKerberosSmokeTest > kerberosAuthTicketExpiryTest [groups: profile_specific_tests, kudu]

java.sql.SQLException: Query failed (#20221011_024428_00002_v7zfj): Couldn't find a valid master in (kudu-master:7051). Exceptions received: [org.apache.kudu.client.NonRecoverableException: server requires authentication, but client Kerberos credentials (TGT) have expired. Authentication tokens were not used because no token is available]

Test detail:

2022-10-11T02:50:31.3721551Z | a7ef095e33264d12b34dc25a14bdb3cd | suite-7-non-generic | multinode-kerberos-kudu | config-default |      {} |  FAILED |   7.06m | Tests exited with code 1 |

Re-run succeeds locally with:

testing/bin/ptl test run --environment multinode-kerberos-kudu --config=config-default -- -t TestKuduConnectoKerberosSmokeTest.kerberosAuthTicketExpiryTest

I think it is unrelated to this patch. The error message indicates credential expiration, possibly due to test running overtime?

[electrum]

@phd3 do you want to take a look?

[findepi]

(just squashed, the build was green https://github.com/trinodb/trino/actions/runs/3293963286)

[phd3]

thanks @weijiii @findepi