[PIP-71][SQL]Pulsar SQL migrate SchemaHandle to presto decoder

[hnail]

Fixes #4747
Fixes #7652

Motivation

PIP-71: https://github.com/apache/pulsar/wiki/PIP-71:-Pulsar-SQL-migrate-SchemaHandle-to-presto-decoder

Pip-Doc : [PIP-71][SQL]Migrate SchemaHandle to Presto-decoder

In current version , pulsar-presto deserialize fields rely on SchemaHandler , but this causes the following restrictions :

• Metadata: current nested field is dissociate with presto ParameterizedType , It treated nested field as a separated field , so presto compiler can’t understand the type hierarchy . nested field should be Row type in presto (e.g. Hive struct type support) . In the same way，array \ map type also shoud associate with presto ParameterizedTypes.
• Decoder : SchemaHandler is hard to work with RecordCursor.getObject() to support ROW,MAP,ARRAY .etc

The motivations of this pull request :

• PulsarMetadata take advantage of ParameterizedType to describe row/array/map Type instead of resolve nested columns in pulsar-presto connecter.
• Customize RowDecoder | RowDecoderFactory | ColumnDecoder to work with pulsar interface, and with some our own extensions compare to presto original version , we can support more type for backward compatible (e.g.
  TIMESTAMP\DATE\TIME\Real\ARRAY\MAP\ROW support).
• Decouple avro or schema type with pulsar-presto main module (RecordSet,ConnectorMetadata .etc ), aim to friendly with other schema type ( ProtobufNative 、thrift etc..).

Modifications

Describe in PIP-71: Pulsar SQL migrate SchemaHandle to presto decoder

---

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

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes )
• The public API: (no)
• The schema: ( no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (no)

Documentation

• Does this pull request introduce a new feature? (yes)
  [PIP][SQL]Migrate SchemaHandle to Presto-decoder

[hnail]

/pulsarbot run-failure-checks

[codelipenghui]

@gaoran10 Could you please help review this PR?

[codelipenghui]

move to 2.8.0 first.

[jiazhai]

@gaoran10 to help review this PR

[sijie]

@hnail Can you rebase this pull request to the latest master?

[hnail]

@hnail Great work. Could you rebase the branch with apache/master first?

@gaoran10 Thanks a lot for your review and help with this PR, i fixed as your suggest. can you help re-review it ?

[Anonymitaet]

Confirmed w/ @congbobo184, no need to update doc for this PR.

[hnail]

/pulsarbot run-failure-checks

[gaoran10]

/pulsarbot run-failure-checks

[jiazhai]

/pulsarbot run-failure-checks

[jiazhai]

/pulsarbot run-failure-checks

[hnail]

/pulsarbot run-failure-checks

[gaoran10]

/pulsarbot run-failure-checks

[codelipenghui]

@hnail @gaoran10 Could you please help take a look the failed test?

Error:  Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (default-testCompile) on project pulsar-presto-connector-original: Compilation failure
Error:  /Users/runner/work/pulsar/pulsar/pulsar-sql/presto-pulsar/src/test/java/org/apache/pulsar/sql/presto/TestPulsarRecordCursor.java:[352,40] method asyncReadEntries in class org.apache.bookkeeper.mledger.impl.ManagedCursorImpl cannot be applied to given types;
Error:    required: int,org.apache.bookkeeper.mledger.AsyncCallbacks.ReadEntriesCallback,java.lang.Object,org.apache.bookkeeper.mledger.impl.PositionImpl
Error:    found: int,java.lang.Object,java.lang.Object
Error:    reason: actual and formal argument lists differ in length

The interesting thing this why other tests are passed. Might be related to the other tests only run the install for profile core-modules ?

[hnail]

@hnail @gaoran10 Could you please help take a look the failed test?

Error:  Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (default-testCompile) on project pulsar-presto-connector-original: Compilation failure
Error:  /Users/runner/work/pulsar/pulsar/pulsar-sql/presto-pulsar/src/test/java/org/apache/pulsar/sql/presto/TestPulsarRecordCursor.java:[352,40] method asyncReadEntries in class org.apache.bookkeeper.mledger.impl.ManagedCursorImpl cannot be applied to given types;
Error:    required: int,org.apache.bookkeeper.mledger.AsyncCallbacks.ReadEntriesCallback,java.lang.Object,org.apache.bookkeeper.mledger.impl.PositionImpl
Error:    found: int,java.lang.Object,java.lang.Object
Error:    reason: actual and formal argument lists differ in length

The interesting thing this why other tests are passed. Might be related to the other tests only run the install for profile core-modules ?

@codelipenghui fixed. cc @gaoran10 @jiazhai

[jiazhai]

@hnail Thanks a lot for this great feature.