[FLINK-17782] Add array,map,row types support for parquet row writer

[meetjunsu]

What is the purpose of the change

In order to support complex types, three new writers will be added to ParquetRowDataWriter, namely ArrayWriter, MapWriter, RowWriter.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (docs)

[flinkbot]

CI report:

• 1b1e007 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit 9b11c30 (Fri Oct 22 01:29:38 UTC 2021)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[meetjunsu]

@JingsongLi could you help to review this PR ？

[meetjunsu]

@snuyanzin updated in latest commit

[snuyanzin]

LGTM

[meetjunsu]

@JingsongLi Would you like to take a look?

[meetjunsu]

rebase onto latest master branch to fix python tests error

[JingsongLi]

Sorry for the late response, I will take a review in the next few days, hope you are still active.

[JingsongLi]

@meetjunsu Thanks for the contribution. Left some comments.

[JingsongLi]

Thanks for your update. @meetjunsu

[JingsongLi]

@flinkbot run azure

[meetjunsu]

@flinkbot run azure

[JingsongLi]

Thanks @meetjunsu for the update, looks good to me!

[JingsongLi]

@meetjunsu Can you create PR for modifying this page: https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/formats/parquet/#data-type-mapping

[JingsongLi]

I create https://issues.apache.org/jira/browse/FLINK-25179 for documentation, comment it if you want to take it.

[uce]

@JingsongLi @meetjunsu https://issues.apache.org/jira/browse/FLINK-31197 was filed end of last year and notes that we can't write nested Array, Row, Map types, because the respective write methods have not been implemented. I understand that the PR is a few years old by now, but do you remember if there was a reason to skip the implementation of those methods?