Sitelet https://web.archive.org/web/20210911182135/https://github.com/apache/incubator-doris/pull/6271
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Implementation Pulsar Sink Doris plugin #6271

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

@Denovo1998
Copy link

@Denovo1998 Denovo1998 commented Jul 19, 2021 •

Proposed changes

Doris's Routine Load realizes the import of data from Kafka to Doris, and make a feature of real-time synchronization of data from Pulsar to Doris based on Pulsar IO.

  1. The custom abstract class DorisAbstractSink implements the interface org.apache.pulsar.io.core.Sink.

  2. The DorisGenericRecordSink class inherits the abstract class DorisAbstractSink, and the specified source data format is org.apache.pulsar.client.api.schema.GenericRecord.

  3. Implement the open and write methods, initialize the configuration file in open(), and implement the logic of inserting data in write().

  4. Construct JsonArray through Stream Load, and then flush data to Doris.

Types of changes

What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)
  • Code refactor (Modify the code structure, format the code, etc...)
  • Optimization. Including functional usability improvements and performance improvements.
  • Dependency. Such as changes related to third-party components.
  • Other.

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
  • Compiling and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • If these changes need document changes, I have updated the document
  • Any dependent changes have been merged

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants