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

Set default compression type & reuse old messages #1405

Open
anhnmt opened this issue Aug 23, 2024 · 6 comments
Open

Set default compression type & reuse old messages #1405

anhnmt opened this issue Aug 23, 2024 · 6 comments
Labels
feature New feature or request frontend help wanted Good for newcomers

Comments

@anhnmt
Copy link

anhnmt commented Aug 23, 2024

image

Is there any way I can leave the default Compress type as UNCOMPRESSED?
I'm testing old programs and having to select UNCOMPRESSED every time is inconvenient

@weeco weeco added feature New feature or request help wanted Good for newcomers frontend labels Aug 23, 2024
@weeco
Copy link
Contributor

weeco commented Aug 23, 2024

We could store the last selection in the frontend. That would be relatively easy to add, do you want to give it a shot?

@anhnmt
Copy link
Author

anhnmt commented Aug 24, 2024

@weeco Of course, I really need this feature. Also, if you can do a message recall feature, it would be even better.

image

Sometimes I want to reuse old messages, this will help save more time

@anhnmt anhnmt changed the title Set default compression type Set default compression type & reuse old messages Aug 24, 2024
@weeco
Copy link
Contributor

weeco commented Aug 24, 2024

What do you mean by a recall feature? Reproducing an existing message and possibly editing it along the way?

@anhnmt
Copy link
Author

anhnmt commented Aug 25, 2024

@weeco Sorry I don't know what to call this function, I just want to copy the old message and push it to the end of the topic with all the information from before.

@oaklandcorp-jkaiser
Copy link

Either remembering the previous selection or allowing a default value to be configured at a system level would be very helpful. Just discovered today that the default value of SNAPPY causes a consumer in a local cluster I'm working on to become completely stuck without error. I now known to explicitly select UNCOMPRESSED to avoid this but having to remember it every time I test something means I'm likely to forget in the future and block up a working system.

@real-mday
Copy link

This issue is currently causing us to get spikes of >1 million messages over the course of hours on our development cluster when a test message is created and our software currently is not able to recover from trying to read a compressed message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request frontend help wanted Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants