Suhas Karanth
06/24/2025, 5:50 AMRunLLM
06/24/2025, 5:50 AMEntryFilter interface, packaging it as a NAR file, and configuring it in the broker (entryFilterNames and entryFiltersDirectory in broker.conf) or at the namespace/topic level using the admin API. The filter logic can access message properties and subscription properties to decide whether to accept, reject, or reschedule a message for delivery to a consumer. See Pulsar plugin development docs and EntryFilter interface.
It is possible to filter messages for a specific subscription by using subscription properties as part of your filter logic. When creating a consumer, you can set subscriptionProperties, and the filter can use these properties to match and filter messages with specific attributes (e.g., message properties). Example usage and test cases are shown in TestEntryFilters.java and PatternEntryFilter.java.
Would you like more detail or a code example?
Sources:
- Pulsar plugin development docs
- TestEntryFilters.java
- PatternEntryFilter.java
- EntryFilter interface 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.