[SPARK-30827][DOCS] Document direct relationship among configurations in "spark.history.*" namespace

[HeartSaVioR]

What changes were proposed in this pull request?

This patch adds direct relationship among configurations under "spark.history" namespace.

Why are the changes needed?

Refer the discussion thread: https://lists.apache.org/thread.html/r43c4e57cace116aca1f0f099e8a577cf202859e3671a04077867b84a%40%3Cdev.spark.apache.org%3E

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Locally ran jekyll and confirmed. Screenshots for the modified spots:

[HeartSaVioR]

cc. @HyukjinKwon

[SparkQA]

Test build #118398 has finished for PR 27575 at commit 23aef36.

• This patch fails build dependency tests.
• This patch merges cleanly.
• This patch adds no public classes.

[HeartSaVioR]

retest this, please

[HyukjinKwon]

@HeartSaVioR, seems Precondition: is new style. Can we follow one prevailing style we use in the current code base? Or I actually think it's just better to say "it's effective when spark.xx.xx is enabled." at the end of each description. Current one seems catching too much attention.

[HeartSaVioR]

I'm seeing different styles in current codebase - I've sought three cases and styles are all different:

spark.dynamicAllocation

if dynamic allocation is enabled (either placed on the first or the last)

spark.task.reaper.*

When spark.task.reaper.enabled = true

spark.sql.adaptive.shuffle.reducePostShufflePartitions.enabled

When true and '${ADAPTIVE_EXECUTION_ENABLED.key}' is enabled,

Common part across these finding is that we prefer putting it to the first part so that end user can indicate it earlier instead of reading all description and realized it later.

Looks like second and third style look similar, I'll take these style and update here.

[SparkQA]

Test build #118406 has finished for PR 27575 at commit 23aef36.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[HeartSaVioR]

Update the doc as well as PR description. Thanks!

[SparkQA]

Test build #118475 has finished for PR 27575 at commit f187060.

• This patch fails PySpark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[HeartSaVioR]

retest this, please

[SparkQA]

Test build #118478 has finished for PR 27575 at commit f187060.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[HyukjinKwon]

I am merging it. @HeartSaVioR, do you plan to go through all documentations for such instances? If you plan to do so, I think it's just better to go and fix as we discussed in the mailing list:

• Check and fix all such configurations to be structured
• Just document somewhere what the structure implies

[HyukjinKwon]

Merged to master and branch-3.0.

[HeartSaVioR]

Thanks for reviewing and merging!

@HeartSaVioR, do you plan to go through all documentations for such instances?

No. I just fixed them as we are aware of them. Definitely better to fix the structure instead.