3.x: Flowable.publish() should not drop items if there are no consumers · Issue #5899 · ReactiveX/RxJava (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

Unlike Observable.publish(), the Flowable.publish() has an internal queue and fetches data from upstream based on consumption. For historical reasons, the 2.x implementation drops items when there are no consumers, which can lead to unnecessary dataloss when switching between consumers on an item boundary.

I propose changing the operator in 3.x to not drop items when there are no consumers. The 2.x behavior can be achieved via an additional unbounded consumer which stays subscribed until the operator completes.