You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
db_bench has several options that accept a compression type as a string and a function converts that string to a compression type enum. For invalid strings the function logs an error message and then returns kSnappyCompression.
I want it to fail (exit with an error code) in that case because nobody is writing scripts to look for that error message, including all of the usage in our perf QA testing. The current code will allow a test to run using the wrong compression and much time can be wasted trying to figure that out.
The text was updated successfully, but these errors were encountered:
…9729)
Summary:
This changes db_bench to fail at startup for invalid compression types. It had been
changing them to Snappy. For other invalid options it fails at startup.
This is for #9621
Pull Request resolved: #9729
Test Plan:
This continues to work:
./db_bench --benchmarks=fillrandom --compression_type=lz4
This now fails rather than changing the compression type to Snappy
./db_bench --benchmarks=fillrandom --compression_type=lz44
Cannot parse compression type 'lz44'
Reviewed By: jay-zhuang
Differential Revision: D35081323
Pulled By: mdcallag
fbshipit-source-id: 9b38c835abddce11aa7feb235df63f53cf829981
db_bench has several options that accept a compression type as a string and a function converts that string to a compression type enum. For invalid strings the function logs an error message and then returns kSnappyCompression.
I want it to fail (exit with an error code) in that case because nobody is writing scripts to look for that error message, including all of the usage in our perf QA testing. The current code will allow a test to run using the wrong compression and much time can be wasted trying to figure that out.
The text was updated successfully, but these errors were encountered: