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

Add apache pulsar based indexing service #11223

Conversation

bananaaggle
Copy link
Contributor

@bananaaggle bananaaggle commented May 8, 2021

Description

Druid has Kafka and kinesis ingestions. Pulsar is a message queue which is similar to Kafka. We have created SeekableStreamSupervisor interface to server this type of message queue. I implement a Pulsar ingestion follow this model. This ingestion use Pulsar message ID as sequence number and use exclusive consume mode which can ordered consume message from Pulsar. I've test it on my MAC and it works for creating/suspending/resuming supervisor and publishing segments. I'll add unit tests and document for it later.
It's type is pulsar and IOconfig will like this:

    "ioConfig": {
      "topic": "persistent://public/default/some-topic",
      "consumerProperties": {
        "pulsar.url": "pulsar://pulsar-address"
      },
      "stream": "persistent://public/default/some-topic"
       ...
    }

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

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

Successfully merging this pull request may close these issues.

None yet

4 participants