[INLONG-4987][Agent] Support CloudEvents Source

[iamsee123]

Prepare a Pull Request

• Fixes #4987

Motivation

CloudEvents is a specification for describing event data in common formats to provide interoperability across services, platforms and systems.

Modifications

• add an util class to convert data with cloudevent format into default message

Verifying this change

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

• [ ] This change is already covered by existing tests, such as: (please describe tests)

• [x] This change added tests and can be verified as follows:

• TestCloudEventsConverterUtil: to test convert util with kafka

[GanfengTan]

Thanks your PR @iamsee123 . Is it more appropriate as an SDK？

[iamsee123]

Thanks your PR @iamsee123 . Is it more appropriate as an SDK？

I think using util class is enough, because it just use to convert data from cloudEvent format into defaultMessage format.

[xuesongxs]

1、The implementation of this PR is a little different from my imagination. My goal is that Inlong starts an HTTP service, receives CloudEvents data, writes it to the Pulsar Topic, and the structure stored in the Topic is CloudEvents. 2、If you want to use the InlongMsg structure uniformly, use cloudevents as the body of InlongMsg inside Inlong. 3、CloudEvents can be transmitted based on HTTP, TCP and gPRC protocols.

[iamsee123]

1、The implementation of this PR is a little different from my imagination. My goal is that Inlong starts an HTTP service, receives CloudEvents data, writes it to the Pulsar Topic, and the structure stored in the Topic is CloudEvents. 2、If you want to use the InlongMsg structure uniformly, use cloudevents as the body of InlongMsg inside Inlong. 3、CloudEvents can be transmitted based on HTTP, TCP and gPRC protocols.

I got it. I will reconstruct the code later.

[xuesongxs]

The inlong full link must support CloudEvents protocol. You can join the WeChat group to discuss.

From: iamsee123 Date: 2022-10-15 22:46 To: apache/inlong CC: xuesongxs; Comment Subject: Re: [apache/inlong] [INLONG-4987][Agent] Support CloudEvents Source (PR #5783) 1、The implementation of this PR is a little different from my imagination. My goal is that Inlong starts an HTTP service, receives CloudEvents data, writes it to the Pulsar Topic, and the structure stored in the Topic is CloudEvents. 2、If you want to use the InlongMsg structure uniformly, use cloudevents as the body of InlongMsg inside Inlong. 3、CloudEvents can be transmitted based on HTTP, TCP and gPRC protocols. I got it. I will reconstruct the code later. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[lucaspeng12138]

[自动回复]：您的邮件我已收到，我将尽快给您回复，谢谢

[github-actions[bot]]

This PR is stale because it has been open for 60 days with no activity.