We provided a set of examples on using the latest flink-connector-pulsar in the Flink repository.
Showing the user how to use this connector.
SimpleSource: Consuming the message from Pulsar by using Flink'sStringSchema.SimpleSink: Write the message into Pulsar by using Flink'sStringSchema.LoadEventSink: Write load event messages with multiple sub-classes into Pulsar byJSONSchema.LoadEventSource: Consuming load event messages from Pulsar byJSONSchemaand filter theLoadCreateEventclass.
Docker compose is quite easy to use. Simply execute docker compose run pulsar in project root directory.
We use docker to run an operable Pulsar environment. All the thing you need to do is just one command.
cd "${this flink-example project directory}"
sudo docker run -it \
-p 6650:6650 \
-p 8080:8080 \
--mount type=bind,source=${PWD}/docker/data,target=/pulsar/data \
--mount type=bind,source=${PWD}/docker/bootstrap.sh,target=/pulsar/bin/bootstrap.sh \
apachepulsar/pulsar:2.10.2 \
/pulsar/bin/bootstrap.shAfter install and setup the Pulsar standalone, we need some management tools for operating on the Pulsar cluster. We prefer to use pulsarctl because it supports shell auto-completion. You can skip this section if you want to use the scripts bundled in Pulsar distribution.
Use homebrew to install pulsarctl on the Mac operating system.
brew tap streamnative/streamnative
brew install pulsarctlWe would auto install zsh-completion and bash-completion when you use Homebrew.
Use this command to install pulsarctl on the Linux operating system.
sh -c "$(curl -fsSL https://raw.githubusercontent.com/streamnative/pulsarctl/master/install.sh)"To install pulsarctl on the Windows operating system, follow these steps:
- Download the package from here.
- Add the
pulsarctldirectory to your system PATH. - Execute
pulsarctl -hto verify thatpulsarctlis work.
All the code snippet shown below was using pulsarctl. You can convert it to Pulsar scripts
by reading the documentation for the Pulsar admin interface.
- Create and use pulsarctl's context for connecting to a Pulsar standalone instance.
## Change the 192.168.50.8 to your Pulsar standalone address.
pulsarctl context set development --admin-service-url="http://192.168.50.8:8080"
## Use the created context
pulsarctl context use development- Execute the initialization scripts.
docker/create-topics.sh
All the required configurations are defined in configs.yml file. Change the serviceUrl and adminUrl to your
pulsar standalone address.
We share the IDEA run configuration in .run directory. You can choose the example case in IDEA's Run Configuration and execute it.
Please go to SQL examples