PIP-64: [REST] Rest API Produce message.

[MarvinCai]

Motivation

PIP 64: https://github.com/apache/pulsar/wiki/PIP-64%3A-Introduce-REST-endpoints-for-producing%2C-consuming-and-reading-messages

Tested with Postman

Modifications

Add produce message rest api.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

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 / no)
• The public API: (yes / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

[MarvinCai]

@codelipenghui @sijie I'm still refining the implementation and will work on unit test, but can you take a initial look to see if I'm on the right track? Thanks.

[MarvinCai]

@codelipenghui Produce logic is working now, I've tested with postman. Can you help take a look on the PR?

[MarvinCai]

/pulsarbot run-failure-checks

[MarvinCai]

talked with @sijie and we think the produce message request/response here share many common attributes with WebSocket produce request/response, so instead of creating new class here we should try update the class there and add necessary attributes. This will also help on adding schema support for WebSocket API.
So I'll make the change for updating message request/response first.

[MarvinCai]

/pulsarbot run-failure-checks

[MarvinCai]

/pulsarbot run-failure-checks

[codelipenghui]

move to 2.8.0 first.

[MarvinCai]

@codelipenghui I've update the url to /topics/[persistent/non-persistent]/tenant/namespace/topic
I think we still need to domain prefix as all other topics related rest endpoint to know if it's a persistent or non-persistent topic, else the code have to make assumption about topics domain which might be different than what user expect

[codelipenghui]

Looks like an unrelated change.

[MarvinCai]

https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/StickyKeyConsumerSelector.java#L28
Just fixing an inconsistent doc when I saw it, probably doesn't worth a separate for such one line change.

[315157973]

Overall looks good

[MarvinCai]

/pulsarbot run-failure-checks

[MarvinCai]

@eolivelli please help take a look

[Anonymitaet]

Discussed with @MarvinCai, he will provide tech inputs for “produce msgs” (we’ll create “REST API” chapter under “Client libraries” this weekend.

[Anonymitaet]

Doc is added #12918

[billowqiu]

Is there a plan to support consume messages with rest api？@MarvinCai @jiazhai