[SERVER-9731] hashed index seed explicitly should be set to BSONElementHasher::DEFAULT_HASH_SEED Created: 20/May/13  Updated: 11/Jul/16  Resolved: 08/Jul/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5.1

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

see: hash_access_method.cpp

If not already the DEFAULT in previous versions, we need to backport to 2.2/2.4. Not a correctness issue (now), but want to make sure we always use the same default seed for the index and computing hash range bounds.



 Comments   
Comment by Greg Studer [ 08/Jul/13 ]

Fixed by:

commit 1e03edb5a6432018af994e1f41e359ae903493a9
Author: Greg Studer <greg@10gen.com>
Date: Tue Jun 11 10:28:44 2013 -0400

SERVER-9859 SERVER-8687 prevent hashed sharding w/o default seed

Generated at Thu Feb 08 03:21:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.