Skip to content

Updated stream properties are not sent before data until it is flushed #14

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

Open
peter-quix opened this issue Dec 8, 2023 · 0 comments

Comments

@peter-quix
Copy link
Contributor

There is a bit of delay before metadata is sent to avoid sending it multiple times for each change in a very short interval.

Once this interval elapses ( or Flush is called), it gets set as the latest set of properties and sent to the wire.

In addition to this, we have a certain period of properties re-broadcast. To avoid re-broadcasting it on its own, filling up the topic with nothing else, we have logic to only do this if there is other message type to send, like parameter data.
In this scenario, the properties gets sent, then the actual data if the re-broadcast logic is fulfilled.

Now, the problem is that when initially a stream is created, properties are set and data gets sent, the re-broadcast logic is triggered, but with the initial null stream properties instead of the configured one, as the properties flush is not yet triggered.

Moved from quixio/quix-streams#11

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

No branches or pull requests

1 participant