Skip to content
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

Pipeline stepping is slower to seek to a record number #4561

Open
p-kimberley opened this issue Oct 28, 2024 · 0 comments
Open

Pipeline stepping is slower to seek to a record number #4561

p-kimberley opened this issue Oct 28, 2024 · 0 comments
Assignees
Labels
bug p:high High priority
Milestone

Comments

@p-kimberley
Copy link
Contributor

Before the 7.5 upgrade, it was possible to quickly jump directly to a particular record number in a segmented stream. This made it more efficient to start stepping (with a filter enabled) from a known location - as opposed to waiting for the entire stream to step through.

Now, trying to jump to a record number (even with no filter defined) requires the user to wait while stepping progresses through the entire stream to that point. For large streams, this effectively removes the previously handy shortcut.

@at055612 at055612 added the bug label Oct 28, 2024
@at055612 at055612 added this to the v7.5 milestone Oct 28, 2024
@stroomdev66 stroomdev66 self-assigned this Oct 28, 2024
@stroomdev66 stroomdev66 added the p:high High priority label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug p:high High priority
Projects
None yet
Development

No branches or pull requests

3 participants