[ISSUE #4869] Add Webhook support for HTTP Source Connector

[cnzakii]

Fixes #4869

Motivation

[Feature] Add Webhook support for HTTP Source Connector #4869

Modifications

1. Support Github webhook
2. Support Common webhook
3. Some other optimizations

Documentation

• Does this pull request introduce a new feature? (yes)
• 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

[cnzakii]

@Pil0tXia PTAL

[Pil0tXia]

I haven't finished reading it yet, I need to travel tomorrow and the next day. I will continue to review when I have time.

[cnzakii]

I haven't finished reading it yet, I need to travel tomorrow and the next day. I will continue to review when I have time.

No problem, open-source work is not the main focus for most people, but don't forget to continue the code review.🤪

[Pil0tXia]

Could you please let me know if the logical order of the information has not been submitted yet?

BTW, please resolve conflicts. ☺️

[cnzakii]

BTW, please resolve conflicts.

OK

Could you please let me know if the logical order of the information has not been submitted yet?

First, for the GitHub protocol, I have imposed a restriction where the source can only receive either forms or JSON, but not both simultaneously. This ensures that all data is either parsed (form) or not parsed (JSON). Consequently, this should ensure that data undergoes the same processing logic, thereby maintaining the order.

For the thread-safe queue, I have currently encapsulated CircularFifoQueue and made it thread-safe using the synchronized keyword. The reason for not using some convenient utility classes is that the fetchRange method is unique to the current queue, and using utility classes cannot guarantee the thread safety of this method.

[Pil0tXia]

Good job, LGTM.

The assignee of #4825 has already started working at a company and doesn't have time to develop this issue. I can assign this issue to you instead. Are you interested?

[cnzakii]

The assignee of #4825 has already started working at a company and doesn't have time to develop this issue. I can assign this issue to you instead. Are you interested?

Although I would very much like to claim and complete this issue, I currently have other work to finish. You can try assigning it to other contributors first. If I have free time and the issue hasn't been resolved, I will claim and solve it.

[xwm1992]

LGTM