Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
allow hash type to be configured #1051
Although the content cache was written so the hash type could be configured to use an algorithm other than the default sha1, there are a few obstacles to overcome to make that work.
First is to allow the hash type to be configured on the broker command line, e.g.
Next is to have the KVS pick up the configured hash type and use it, since it pre-generates blobrefs to use as hash keys in its internal cache when content store requests are sent off (they can't wait for the response to get the hash key).
Finally, add a test that makes sure this works.
Along the way I updated the names of all the attributes used by the content store to be namespaced in the more modern way:
@@ Coverage Diff @@ ## master #1051 +/- ## ========================================== - Coverage 77.75% 77.67% -0.08% ========================================== Files 148 148 Lines 25739 25752 +13 ========================================== - Hits 20014 20004 -10 - Misses 5725 5748 +23