[docs] Add Session Properties to Hive Connector

[steveburnett]

Add a new Hive Session Properties topic to Hive Connector doc. The new topic should be similar to the existing Hive Configuration Properties topic.

The content of the new topic can be gathered by pulling together the mentions of hive session properties scattered throughout the page Hive Connector into a new topic.

A note about scope:
This issue is intended only as a restructuring of existing documentation, and it should not be expanded to become a comprehensive list of all (currently undocumented) Hive session properties. A hunt for undocumented Hive session properties should be a separate issue.

Expected Behavior or Use Case

New Hive Session Properties topic in the Hive Connector documentation.

Presto Component, Service, or Connector

Documentation.

Context

As part of a discussion in #25021 (comment one and comment two) it was mentioned that the Iceberg Connector doc has separate topics for Configuration Properties and Session Properties.

I opened this issue to allow people to discuss if adding a new Hive Session Properties topic in Hive Connector is a good idea.

[steveburnett]

@agrawalreetika, @imjalpreet, I wanted to ask your thoughts about this new doc issue. What do you think?

[imjalpreet]

@steveburnett Just thinking out loud, do you think it might make more sense to keep session and config properties together in one section? Typically, session properties correspond to config properties, but not all config properties have session equivalents. If we separate them, we might end up duplicating descriptions across both sections. A unified section could make it easier for users to find all related details in one place.

[steveburnett]

@imjalpreet, thanks for your reply and thinking. We could do that. Let me explain some of my thoughts behind this issue.

Typically, session properties correspond to config properties, but not all config properties have session equivalents.

Yes, and that's important! One reason for avoiding duplicated content is if you don't, now you have a "dual maintenance" problem where you have to manually edit both, which means at some point mistakes get made and the docs get out of sync. One way to solve this is use a single source approach of text fragments, another is - like you are describing - structure the doc so there is no duplicate content.

While duplicated content is generally something to avoid in technical documentation, I don't mind so much duplicating the descriptions for a property in config and session because once a property is documented it rarely changes so the dual maintenance problem isn't really a problem here.

This issue was created because we want to add to the doc a session property for the Hive Connector and the Iceberg Connector. The Iceberg Connector has separate topics for Configuration Properties and for Session Properties. The Hive Connector has a topic for Configuration Properties with session properties mentioned in with the config property entries.

In the past, the Properties Reference page in the Presto doc combined config and session properties - I'm linking to the archived 0.289 doc for illustration. One reason I split that page into two pages (Configuration, Session) was because discussing it with @tdcmeehan at the time, he suggested that Presto users are generally interested in config properties or session properties, but less often are interested in using both at the same time.

(Because of this insight into Presto user behavior, I was thinking "Add a Session Properties topic in Hive Connector" instead of "revise Iceberg Connector to combine the Config and Session properties topics", but I'd like to improve the consistency of the doc structure by changing one of these connector pages.)

To help people find or be aware of corresponding entries in the other (session/config) doc we added a sentence to entries like
"The corresponding configuration property is join-distribution-type.". for ones that exist.

I then duplicated that separation of content and created separate pages when I was asked to create doc for Presto C++ Configuration and Session properties.

Because the Hive Connector and Iceberg Connector use a table format for their properties, we could connect the config and session tables in one of two ways:

• Add a column to the Config Properties table "Session Property", and populate that cell with the name of the corresponding session property. Leave the cell blank if the config property has no corresponding session property.

  Also add a column to the Session Properties table "Config Property" and use it the same way.

• Rewrite the tables in the format of the current Presto properties pages (Configuration, Session). This would improve the format consistency for the Presto doc.

Note: I am also interested in potentially separating the content of the connector properties topics out into their own sub-pages like the current Hive Security Configuration page. Both the Hive and Iceberg Connector pages are huge - at 28 and 54 pages respectively they're like book chapters. Moving the properties topics into linked sub-pages could help shorten the page length and help people get to the content they're looking for easier.