HIVE-28037: Run multiple Qtests with Postgres

[zratkai]

Running multiple qtests with Postgre will not fail with "Database does not exist: default". It keeps docker up and running between tests.

What changes were proposed in this pull request?

Changes to be able to run multiple Qtests with Postgre.

Why are the changes needed?

Without this change only one Qtest can be run with Postgre.

Does this PR introduce any user-facing change?

No

Is the change a dependency upgrade?

No

How was this patch tested?

Locally.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[InvisibleProgrammer]

Could you please add some explanation about the change?
That description is a little bit confusing:
Change-Id: I2c37973af59f69d17de733d69f184fe83bcc3091

[InvisibleProgrammer]

Short version: LGTM.

Long version: I checked it out with a PR that uses postgresql driver as a default one to check what happens if we want to run all the qtestst with postgres.
Test run: http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-5122/2/tests/
PR: #5122
Diff for the failing tests with only output diff (details below): master...InvisibleProgrammer:hive:HIVE-28037

The PR itself reached it's goal: it had no problem with running multiple qtests with postgres.

Different type of groups of test result

Minor output differences

There were tests that failed but with minor output diff differences. Typically, with having columns in an output in different order or with whitespace differences. I would consider them as a pass. We cannot address those issues as the difference comes from the differences between derby and postgres engine.
Some examples:

• default_constraint - unique constraints are shown in different order
• create_with_constraints - key columns in different order
• drop_partitions_filter.q - Some columns in different order, duplicate key error has different output

Cannot run the tests with explicitly defined postgres driver as the tests are designed to run with postgres:

There are some tests with a comment like --!qt:database:postgres:q_test_country_table.sql
Those tests are failing with unable to start docker container if we add the postgres db parameter to the test execution. I don't think it worth investigating as they are designed to run with postgres and no other driver.
Some examples:

• qt_database_postgres.q
• jdbc_partition_table_pruned_pcolumn.q

Failed test cases that worth to fix:

• https://issues.apache.org/jira/browse/HIVE-28150: Fix: cannot run Kudu and Blobstorage qtests with postgres driver as driver not found
• https://issues.apache.org/jira/browse/HIVE-28151: Fix escape1.q and escape2.q tests with postgres driver
• https://issues.apache.org/jira/browse/HIVE-28152: Fix partition_column_names_with_leading_and_trailing_spaces.q with postgres driver

[deniskuzZ]

LGTM +1

[deniskuzZ]

@zratkai, @InvisibleProgrammer could we please update instructions in https://cwiki.apache.org/confluence/display/Hive/HiveDeveloperFAQ#HiveDeveloperFAQ-HowdoIruntheclientpositive/clientnegativeunittests?