{"push_id":1336018392,"size":1,"distinct_size":1,"ref":"refs/heads/shards-preference","head":"950a23d95b6209647f6c6d70224faf5b320b7880","before":"ca1a8dfeec8435427f738b00d4b4277508efd6ba","commits":[{"sha":"950a23d95b6209647f6c6d70224faf5b320b7880","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Change separator for shards preference\n\nThe shards preference on a search request enables specifying a list of\nshards to hit, and then a secondary preference (e.g., \"_primary\") can be\nadded. Today, the separator between the shards list and the secondary\npreference is ';'. Unfortunately, this is also a valid separtor for URL\nquery parameters. This means that a preference like \"_shards:0;_primary\"\nwill be parsed into two URL parameters: \"_shards:0\" and \"_primary\". With\nthe recent change to strict URL parsing, the second parameter will be\nrejected, \"_primary\" is not a valid URL parameter on a search\nrequest. This means that this feature has never worked (unless the ';'\nis escaped, but no one does that because our docs do not that, and there\nwas no indication from Elasticsearch that this did not work). This\ncommit changes the separator to '+'.","distinct":true,"url":"https://api.github.com/repos/jasontedor/elasticsearch/commits/950a23d95b6209647f6c6d70224faf5b320b7880"}]}
{"actor":{"display_login":"jasontedor"}}