You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The SQL in integration tests has the following line : CREATE MATERIALIZED VIEW db1.struct_test_view_materialized as select * from db1.struct_test;
I believe, it doesn't create a materialized view, as the docker-compose file uses the Hive of version 2.x, and according to the Hive documentation, Materialized Views were introduced in Hive 3.0.0.
In Hive 2.x the word "Materialized" is probably ignored. In 3.x or 4.x it will cause the container to fall, as you need to have transactional tables stored in specific format in order to use build the container.
To Reproduce
In 2.x it passed even trough the functionality you test hasn't been introduced yet.
Steps to reproduce the behavior in 3.x:
Run some Hive container with the version 3.x+
Run the integration tests SQL file on that instance.
You'll get an error Automatic rewriting for materialized view cannot be enabled if the materialized view uses non-transactional tables.
Expected behavior
All the SQL statements in version 3.x+ should be completed successfully.
In version 2.x there shouldn't be word "Materialized" as that feature wasn't introduced.
To solve that problem
In 2.x the "Materialized" word should be removed.
For 3.x+ you have two choices:
2.1 Do not check materialized view
2.2 Create a database with transactional tables, create a materialized view based on them.
The text was updated successfully, but these errors were encountered:
Describe the bug
The SQL in integration tests has the following line :
CREATE MATERIALIZED VIEW db1.struct_test_view_materialized as select * from db1.struct_test;
I believe, it doesn't create a materialized view, as the docker-compose file uses the Hive of version 2.x, and according to the Hive documentation, Materialized Views were introduced in Hive 3.0.0.
In Hive 2.x the word "Materialized" is probably ignored. In 3.x or 4.x it will cause the container to fall, as you need to have transactional tables stored in specific format in order to use build the container.
To Reproduce
In 2.x it passed even trough the functionality you test hasn't been introduced yet.
Steps to reproduce the behavior in 3.x:
Automatic rewriting for materialized view cannot be enabled if the materialized view uses non-transactional tables.
Expected behavior
All the SQL statements in version 3.x+ should be completed successfully.
In version 2.x there shouldn't be word "Materialized" as that feature wasn't introduced.
To solve that problem
2.1 Do not check materialized view
2.2 Create a database with transactional tables, create a materialized view based on them.
The text was updated successfully, but these errors were encountered: