-
Notifications
You must be signed in to change notification settings - Fork 882
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
Change parameter name to enable Hypercore TAM #7411
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7411 +/- ##
==========================================
+ Coverage 80.06% 82.56% +2.49%
==========================================
Files 190 229 +39
Lines 37181 42731 +5550
Branches 9450 10731 +1281
==========================================
+ Hits 29770 35279 +5509
- Misses 2997 3168 +171
+ Partials 4414 4284 -130 ☔ View full report in Codecov by Sentry. |
e1d53bc
to
22aa0fa
Compare
3faae59
to
0dfefaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one question about name of configuration in policy json. Should it be the same as the parameter name in compress_chunk?
Yes, I think so. All user-facing parameters should be coordinated. Will fix. |
45c1e8b
to
159ea80
Compare
Done. |
159ea80
to
39b2556
Compare
39b2556
to
a83c471
Compare
Changing from using the `compress_using` parameter with a table access method name to use the boolean parameter `hypercore_use_access_method` instead to avoid having to provide a name when using the table access method for compression.
a83c471
to
623270b
Compare
Changing from using the
compress_using
parameter with a table access method name to use the boolean parameterhypercore_use_access_method
instead to avoid having to provide a name when using the table access method for compression.