Add support for ANALYZE FOR QUERY statement

[tangjiangling]

Description

Is this change a fix, improvement, new feature, refactoring, or other?

New sql syntax.

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Core query engine.

How would you describe this change to a non-technical end user or system administrator?

Allow user to execute the ANALYZE FOR QUERY statement to collect statistics on the granularity of the query.

Related issues, pull requests, and links

Fixes #11517

Documentation

( ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

[findepi]

cc @sopel39 @martint @kokosing @losipiuk

[tangjiangling]

cc @wubiaoi

[tangjiangling]

Once the code has been reviewed, I'll file a PR for the documentation.

[tangjiangling]

Run the following command (to check if I need to add additional tests)

git --no-pager grep -n '"ANALYZE ' | awk '{print $1}' | awk -F':' '{print $1}' | sort | uniq

Results:

core/trino-main/src/test/java/io/trino/sql/analyzer/TestAnalyzer.java
core/trino-main/src/test/java/io/trino/sql/planner/TestLogicalPlanner.java
core/trino-parser/src/main/java/io/trino/sql/SqlFormatter.java
core/trino-parser/src/test/java/io/trino/sql/parser/TestSqlParser.java
plugin/trino-delta-lake/src/main/java/io/trino/plugin/deltalake/DeltaLakeMetadata.java
plugin/trino-delta-lake/src/test/java/io/trino/plugin/deltalake/BaseDeltaLakeConnectorSmokeTest.java
plugin/trino-delta-lake/src/test/java/io/trino/plugin/deltalake/TestDeltaLakeAnalyze.java
plugin/trino-hive/src/test/java/io/trino/plugin/hive/BaseHiveConnectorTest.java
plugin/trino-hive/src/test/java/io/trino/plugin/hive/TestAnalyzeForQuery.java
plugin/trino-mysql/src/test/java/io/trino/plugin/mysql/BaseMySqlTableStatisticsIndexStatisticsTest.java
plugin/trino-mysql/src/test/java/io/trino/plugin/mysql/TestMySqlAutomaticJoinPushdown.java
plugin/trino-mysql/src/test/java/io/trino/plugin/mysql/TestMySqlTableStatisticsMySql8Histograms.java
plugin/trino-postgresql/src/test/java/io/trino/plugin/postgresql/TestJoinReorderingWithJoinPushdown.java
plugin/trino-postgresql/src/test/java/io/trino/plugin/postgresql/TestPostgreSqlAutomaticJoinPushdown.java
plugin/trino-postgresql/src/test/java/io/trino/plugin/postgresql/TestPostgreSqlTableStatistics.java
testing/trino-product-tests/src/main/java/io/trino/tests/product/TestTwoHives.java
testing/trino-product-tests/src/main/java/io/trino/tests/product/hive/TestExternalHiveTable.java
testing/trino-product-tests/src/main/java/io/trino/tests/product/hive/TestHiveBasicTableStatistics.java
testing/trino-product-tests/src/main/java/io/trino/tests/product/hive/TestHiveTableStatistics.java
testing/trino-testing/src/main/java/io/trino/testing/BaseFailureRecoveryTest.java
testing/trino-tests/src/test/java/io/trino/security/TestAccessControl.java
testing/trino-tests/src/test/java/io/trino/tests/tpch/TestTpchConnectorTest.java

So it looks like I still need to add PTs about Hive/Deltalake (I'm not sure if Deltalake needs to support this at the moment, see

trino/plugin/trino-delta-lake/src/main/java/io/trino/plugin/deltalake/DeltaLakeMetadata.java

Line 1749 in 070debd

public ConnectorTableHandle getTableHandleForStatisticsCollection(ConnectorSession session, SchemaTableName tableName, Map<String, Object> analyzeProperties)

)

[tangjiangling]

(Rebased from master to resolve conflicts)

[tangjiangling]

(Rebased from master to resolve conflicts)

[tangjiangling]

@findepi If you are available, please take a look at this PR.

[findepi]

Marked this as a draft until #11517 (comment) is addressed.

[electrum]

I think this situation also occurs if you run a query like

ANALYZE FOR SELECT 123

So this error should probably be something like "No tables to analyze"

[electrum]

Why do we need this logic? A TableScanNode will contain a TableHandle which is for the underlying table of a view. It should never itself be a view.

[electrum]

I have a PR #12388 that changes the analyze API to return ConnectorAnalyzeMetadata. We should make this new method use the new return type. cc @findepi

[colebow]

👋 @tangjiangling - this PR is inactive and doesn't seem to be under development. If you'd like to continue work on this at any point in the future, feel free to re-open.