-
Notifications
You must be signed in to change notification settings - Fork 351
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
Comments
We could store the last selection in the frontend. That would be relatively easy to add, do you want to give it a shot? |
@weeco Of course, I really need this feature. Also, if you can do a message recall feature, it would be even better. Sometimes I want to reuse old messages, this will help save more time |
What do you mean by a recall feature? Reproducing an existing message and possibly editing it along the way? |
@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. |
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 |
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 |
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
The text was updated successfully, but these errors were encountered: