public interface TopicService
Messages are delivered in the order they were published on the node they were published on. If node N publishes messages m1, m2..mn, all listeners receive messages m1, m2..mn in order.
Messages are not durable and message delivery is guaranteed only to the listeners that were reachable at
the time a message is published. In the case of network partitions, listeners may miss messages. Plugins that rely
on TopicService
to handle cluster coherency are encouraged to also listen for the various
cluster node events
to handle nodes joining, rejoining and leaving the cluster.
Modifier and Type | Method and Description |
---|---|
<T extends Serializable> |
getTopic(String topic,
TopicSettings<T> settings)
Returns the existing topic, or creates new topic with the provided settings if it does not yet exist.
|
@Nonnull <T extends Serializable> Topic<T> getTopic(@Nonnull String topic, @Nonnull TopicSettings<T> settings)
T
- the message type of the topictopic
- the topic namesettings
- the topic configurationCopyright © 2020 Atlassian. All rights reserved.