Uh oh!
There was an error while loading. Please reload this page.
[SPARK-27690][SQL] Remove materialized views first in HiveClientImpl.reset - #24592
[SPARK-27690][SQL] Remove materialized views first in HiveClientImpl.reset#24592wangyum wants to merge 2 commits into
HiveClientImpl.reset#24592Conversation
Uh oh!
There was an error while loading. Please reload this page.
SparkQA
commented
May 13, 2019
Test build #105361 has finished for PR 24592 at commit
|
HiveClientImpl.resetHiveClientImpl.resetHiveClientImpl.resetdongjoon-hyun
commented
May 13, 2019
Thank you for updating, @wangyum ! |
SparkQA
commented
May 13, 2019
Test build #105368 has finished for PR 24592 at commit
|
There was a problem hiding this comment.
+1, LGTM. Merged to master. Thank you, @wangyum .
cc @gatorsmile .
| val (mvs, others) = allTables.asScala.map(t => client.getTable("default", t)) | ||
| .partition(_.getTableType.toString.equals("MATERIALIZED_VIEW")) | ||
| // Remove materialized view first, otherwise caused a violation of foreign key constraint. |
There was a problem hiding this comment.
Do we have the same issue for Hive indexes? Also, we normally also added a test case in the Version Suite. You can do it by using the method runSqlHive(sql: String) to create materialized views.
There was a problem hiding this comment.
This issue only occurs with materialized views in Hive 3.1.
I have tested the index and the view.
What changes were proposed in this pull request?
We should remove materialized view first otherwise(note that Hive 3.1 could reproduce this issue):
How was this patch tested?
Existing test