Skip to content

Conversation

@yaooqinn
Copy link
Member

What changes were proposed in this pull request?

This PR enabled the assertion in HiveMetastoreLazyInitializationSuite

Why are the changes needed?

fix test intenton

Does this PR introduce any user-facing change?

no

How was this patch tested?

pass HiveMetastoreLazyInitializationSuite

Was this patch authored or co-authored using generative AI tooling?

no

@github-actions github-actions bot added the SQL label Dec 26, 2023
@yaooqinn
Copy link
Member Author

cc @LuciferYang @dongjoon-hyun thanks.

.enableHiveSupport()
.config("spark.hadoop.hive.metastore.uris", "thrift://127.0.0.1:11111")
.config("spark.ui.enabled", "false")
.config("hive.metastore.connect.retries", "1")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you clarify why do you need this, please. Won't it lead to test flakiness?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for @MaxGekk 's comment.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MaxGekk @dongjoon-hyun, as thrift://127.0.0.1:11111 is an unreachable HMS endpoint, it's better to fail at once w/o unnecessary retries to reduce the test time. It will not increase the flakiness.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another thing is that this SparkSession instance is not for sharing and will be closed in the final block.

Copy link
Contributor

@LuciferYang LuciferYang Dec 27, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the purpose of this configuration is to allow for fast failure in order to save some test time, right? Even without this change, the test can still succeed, correct?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the purpose here is the same as ui.enabled for lightweight testing. There is no increase in risk of flakiness here. It's just a piggybacking change. I did this regarding to low possibility of future changes against this file. It's also OK to remove them and leave it as-is if you insist.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fail-fast is not a bug fix. To be clear, please proceed that first before this PR, @yaooqinn .

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dongjoon-hyun, removed

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is restored, the PR is only one line change, I will merge it now

@yaooqinn yaooqinn closed this in d0245d3 Dec 28, 2023
yaooqinn added a commit that referenced this pull request Dec 28, 2023
### What changes were proposed in this pull request?

This PR enabled the assertion in HiveMetastoreLazyInitializationSuite

### Why are the changes needed?

fix test intenton

### Does this PR introduce _any_ user-facing change?

no

### How was this patch tested?

pass HiveMetastoreLazyInitializationSuite

### Was this patch authored or co-authored using generative AI tooling?

no

Closes #44500 from yaooqinn/SPARK-46514.

Authored-by: Kent Yao <[email protected]>
Signed-off-by: Kent Yao <[email protected]>
(cherry picked from commit d0245d3)
Signed-off-by: Kent Yao <[email protected]>
yaooqinn added a commit that referenced this pull request Dec 28, 2023
### What changes were proposed in this pull request?

This PR enabled the assertion in HiveMetastoreLazyInitializationSuite

### Why are the changes needed?

fix test intenton

### Does this PR introduce _any_ user-facing change?

no

### How was this patch tested?

pass HiveMetastoreLazyInitializationSuite

### Was this patch authored or co-authored using generative AI tooling?

no

Closes #44500 from yaooqinn/SPARK-46514.

Authored-by: Kent Yao <[email protected]>
Signed-off-by: Kent Yao <[email protected]>
(cherry picked from commit d0245d3)
Signed-off-by: Kent Yao <[email protected]>
@yaooqinn
Copy link
Member Author

Thank you all. Merged to master/3.5/3.4

szehon-ho pushed a commit to szehon-ho/spark that referenced this pull request Feb 7, 2024
### What changes were proposed in this pull request?

This PR enabled the assertion in HiveMetastoreLazyInitializationSuite

### Why are the changes needed?

fix test intenton

### Does this PR introduce _any_ user-facing change?

no

### How was this patch tested?

pass HiveMetastoreLazyInitializationSuite

### Was this patch authored or co-authored using generative AI tooling?

no

Closes apache#44500 from yaooqinn/SPARK-46514.

Authored-by: Kent Yao <[email protected]>
Signed-off-by: Kent Yao <[email protected]>
(cherry picked from commit d0245d3)
Signed-off-by: Kent Yao <[email protected]>
turboFei pushed a commit to turboFei/spark that referenced this pull request Nov 6, 2025
### What changes were proposed in this pull request?

This PR enabled the assertion in HiveMetastoreLazyInitializationSuite

### Why are the changes needed?

fix test intenton

### Does this PR introduce _any_ user-facing change?

no

### How was this patch tested?

pass HiveMetastoreLazyInitializationSuite

### Was this patch authored or co-authored using generative AI tooling?

no

Closes apache#44500 from yaooqinn/SPARK-46514.

Authored-by: Kent Yao <[email protected]>
Signed-off-by: Kent Yao <[email protected]>
(cherry picked from commit d0245d3)
Signed-off-by: Kent Yao <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants