{{ message }}
Set the capacity of the SELECT sink to 1 temporarily#104
Merged
Conversation
Member
Author
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When streaming video frames from RPi, the process is easily killed by OOM if the receiver can't consume tuples fast enough. Although users can specify
BUFFER SIZEandDROP IFin the SELECT statement, there's no way to specify those parameters for the Sink connected to the SELECT BQL box.This problem should be solved by adding a way in SELECT (and perhaps INSERT INTO) statements to specify buffer size and drop mode, but it's temporarily fixed by setting 1 to the buffer size (i.e. capacity).