Implementation tracker:

• Parquet: Support read process for PageIndex (ColumnIndex / OffsetIndex)  #1749
• support write page index #1777

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Suggested by @ParadoxShmaradox ON #1191

In analytics systems, parquet files are passed around between different systems, so the more metadata is written by the rust implementation of parquet, the better other systems may be able to handle it.

One such type of metadata is PageIndex https://github.com/apache/parquet-format/blob/master/PageIndex.md

Specifically, I believe this is called a ColumnIndex and OffsetIndex in parquet-format:

https://github.com/apache/parquet-format/blob/master/src/main/thrift/parquet.thrift#L938-L971

https://github.com/apache/parquet-format/blob/master/src/main/thrift/parquet.thrift#L926-L932

Which is used to speed up queries in certain systems -- for example https://blog.cloudera.com/speeding-up-select-queries-with-parquet-page-indexes/

Describe the solution you'd like

1. Write PageIndex structures into files created by parquet-rs (specif
2. Provide access to reading PageIndex from the parquet metadata structures

Note that if creating the PageIndex structures is too expensive, their creation could be optional and controlled via options.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Original request here #1191 (comment)