{"push_id":1466236433,"size":161,"distinct_size":52,"ref":"refs/heads/explain_api_refactor_rest","head":"81c16f5e7fda464a9ea5e0e1e5eec2a2d94245b6","before":"e0d6df724b6d489129bbc4d0e382cf16e8114b98","commits":[{"sha":"318ce6ab16635392b6c0f17e7b54015b85eaf1d3","author":{"name":"makeyang","email":"951bdb7e7fab050529e29d148e60cb74d7e90f11@jd.com"},"message":"fix bug: https://github.com/elastic/elasticsearch/issues/21710","distinct":true,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/318ce6ab16635392b6c0f17e7b54015b85eaf1d3"},{"sha":"46cdb411b53cac6f35455e45623015b2f2bd4e0c","author":{"name":"makeyang","email":"951bdb7e7fab050529e29d148e60cb74d7e90f11@jd.com"},"message":"modified code according to nik9000's comments.","distinct":true,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/46cdb411b53cac6f35455e45623015b2f2bd4e0c"},{"sha":"ce0ad4e08e93cc4dc1b08f51960aee7e2f0000f3","author":{"name":"makeyang","email":"951bdb7e7fab050529e29d148e60cb74d7e90f11@jd.com"},"message":"add test case for parse include_in_all in mulit fields","distinct":true,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/ce0ad4e08e93cc4dc1b08f51960aee7e2f0000f3"},{"sha":"182e11969952fcc157d306e991214462d1a47ba2","author":{"name":"Adrien Grand","email":"83387f1adf6f01406cba47ad9f87966de8fe24be@gmail.com"},"message":"IP range masks exclude the maximum address of the range. (#22018)\n\nCloses #22005","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/182e11969952fcc157d306e991214462d1a47ba2"},{"sha":"18a3d6b4f3f893d8b229791df36e13cd37c77050","author":{"name":"David Pilato","email":"d8099b0f90e53c29d29eb12a7a3caa5af4f12681@pilato.fr"},"message":"S3/Azure snapshot repo documentation wrong for \"read_only\"\n\nWe used to write that people should use `read_only` although it should be `readonly`.\n\nCloses #22007.","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/18a3d6b4f3f893d8b229791df36e13cd37c77050"},{"sha":"0f7c20ae81e2dabd6e713299a28495d42e5d6e82","author":{"name":"Nik Everett","email":"8f968e953049b60f3547bb43375dfdb757e1c88c@gmail.com"},"message":"Build: NORELEASE is the same as norelease (#22006)\n\nChanges the build to recognize `NORELEASE` as well as `NOCOMMIT` to\r\nmean the same thing as `norelease` and `nocommit` respectively. This\r\nis useful because people have been using them that way but haven't\r\nrealized that only the lowercase versions worked.\r\n\r\nThis also explicitly forbids silly things like `NoReLeAsE` and\r\n`noCOMMIT`, failing the build and telling you to spell them properly.","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/0f7c20ae81e2dabd6e713299a28495d42e5d6e82"},{"sha":"8fe4bc1b743e970e64157c0fa7a5b415cfecb1cf","author":{"name":"Adrien Grand","email":"83387f1adf6f01406cba47ad9f87966de8fe24be@gmail.com"},"message":"Fix REST test for ip range aggregations.\n\nRelates to #22018","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/8fe4bc1b743e970e64157c0fa7a5b415cfecb1cf"},{"sha":"3da04293f32b36f2a6dcfb381d85c7f55fc289d6","author":{"name":"Ali Beyad","email":"6bef8114f791610f325e21bf98cab17795dfd86b@elastic.co"},"message":"Cannot force allocate primary to a node where the shard already exists (#22031)\n\nBefore, it was possible that the SameShardAllocationDecider would allow\r\nforce allocation of an unassigned primary to the same node on which an\r\nactive replica is assigned.  This could only happen with shadow replica\r\nindices, because when a shadow replica primary fails, the replica gets\r\npromoted to primary but in the INITIALIZED state, not in the STARTED\r\nstate (because the engine has specific reinitialization that must take\r\nplace in the case of shadow replicas).  Therefore, if the now promoted\r\nprimary that is initializing fails also, the primary will be in the\r\nunassigned state, because replica to primary promotion only happens when\r\nthe failed shard was in the started state.  The now unassigned primary\r\nshard will go through the allocation deciders, where the\r\nSameShardsAllocationDecider would return a NO decision, but would still\r\npermit force allocation on the primary if all deciders returned NO.\r\n\r\nThis commit implements canForceAllocatePrimary on the\r\nSameShardAllocationDecider, which ensures that a primary cannot be\r\nforce allocated to the same node on which an active replica already\r\nexists.","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/3da04293f32b36f2a6dcfb381d85c7f55fc289d6"},{"sha":"8b0df473814dc158eda8eee5fe974e019ff2c802","author":{"name":"David Pilato","email":"d8099b0f90e53c29d29eb12a7a3caa5af4f12681@pilato.fr"},"message":"readonly on azure repository must be taken into account\n\nWhile I was fixing a documentation issue (#22007), I looked at the code and discovered that we actually never read what the user entered as a `readonly` parameter when he creates an azure repository.\n\nSo if someone sends:\n\n```\nPUT _snapshot/my_backup4\n{\n    \"type\": \"azure\",\n    \"settings\": {\n        \"account\": \"my_account2\",\n        \"location_mode\": \"primary_only\",\n        \"readonly\": true\n    }\n}\n```\n\nThe repository is not actually defined as `readonly`.\n\nIt's caused by the fact we are always overwriting `readonly`setting based on `location_mode`.\nIf a user sets it to `primary_only`, `readonly` is forced to `false`.\nIf a user sets it to `primary_then_secondary`, `readonly` is forced to `false`.\nIf a user sets it to `secondary_only`, `readonly` is forced to `false`.\n\nNote that with this change, a user can force a `secondary_only` repository to `readonly: false` which will lead him to an error later on when we check the repository as per definition in Azure, a secondary repository is not writable.\nAnother option could have been to detect this mismatch and throw an exception in that case. Note sure it is worth writing more code though.\n\nCloses #22053.","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/8b0df473814dc158eda8eee5fe974e019ff2c802"},{"sha":"e9bb8d8b38c5ec50f46f9703f4284e1d617ac65d","author":{"name":"Nik Everett","email":"8f968e953049b60f3547bb43375dfdb757e1c88c@gmail.com"},"message":"Don't allow yaml tests with `warnings` that don't skip `warnings` (#21989)\n\nIf you write a yaml test with a `warnings` section in a `do` block\r\nthat doesn't also have a corresponding `skip` section for `warnings`\r\nthen client test runners that don't support `warnings` will fail.\r\nThis causes the elasticsearch build to fail so we catch these errors\r\nearlier.\r\n\r\nRelated to #21811","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/e9bb8d8b38c5ec50f46f9703f4284e1d617ac65d"},{"sha":"f713106827abeb1c6bf85ed7949570f6b1d73266","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Bump version to 5.1.2\n\nThis commit bumps the version to 5.1.2.\n\nRelates #22057","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/f713106827abeb1c6bf85ed7949570f6b1d73266"},{"sha":"4aae0178912309eba92e2ae8028facd636c8679a","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Skip IP range query REST test prior to 5.1.2\n\nThis commit adds a skip for the IP range query REST test on version\nprior to 5.1.2 due to a exclusive bug on the top end of the range.","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/4aae0178912309eba92e2ae8028facd636c8679a"},{"sha":"c9882dd1a0f3c513d4c39e99c8a928ec2a6bab18","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Avoid NPE in NodeService#stats if HTTP is disabled\n\nThis commit adds safety against an NPE if HTTP stats are requested but\r\nHTTP is disabled on a node.\r\n\r\nRelates #22060","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/c9882dd1a0f3c513d4c39e99c8a928ec2a6bab18"},{"sha":"ee22a477df841d2c7087674d5389b3adacc1701b","author":{"name":"Lee Hinman","email":"e62162cf4d95df85defedbb6fc7531efd473b77b@writequit.org"},"message":"Add internal _primary_term doc values field, fix _seq_no indexing\n\nThis adds the `_primary_term` field internally to the mappings. This field is\npopulated with the current shard's primary term.\n\nIt is intended to be used for collision resolution when two document copies have\nthe same sequence id, therefore, doc_values for the field are stored but the\nfiled itself is not indexed.\n\nThis also fixes the `_seq_no` field so that doc_values are retrievable (they\nwere previously stored but irretrievable) and changes the `stats` implementation\nto more efficiently use the points API to retrieve the min/max instead of\niterating on each doc_value value. Additionally, even though we intend to be\nable to search on the field, it was previously not searchable. This commit makes\nit searchable.\n\nThere is no user-visible `_primary_term` field. Instead, the fields are\nupdated by calling:\n\n```java\nindex.parsedDoc().updateSeqID(seqNum, primaryTerm);\n```\n\nThis includes example methods in `Versions` and `Engine` for retrieving the\nsequence id values from the index (see `Engine.getSequenceID`) that are only\nused in unit tests. These will be extended/replaced by actual implementations\nonce we make use of sequence numbers as a conflict resolution measure.\n\nRelates to #10708\nSupercedes #21480\n\nP.S. As a side effect of this commit, `SlowCompositeReaderWrapper` cannot be\nused for documents that contain `_seq_no` because it is a Point value and SCRW\ncannot wrap documents with points, so the tests have been updated to loop\nthrough the `LeafReaderContext`s now instead.","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/ee22a477df841d2c7087674d5389b3adacc1701b"},{"sha":"ef64d230e79f8237c4449dbd5dad744e904acb92","author":{"name":"Lee Hinman","email":"e62162cf4d95df85defedbb6fc7531efd473b77b@writequit.org"},"message":"Merge remote-tracking branch 'dakrone/index-seq-id-and-primary-term'","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/ef64d230e79f8237c4449dbd5dad744e904acb92"},{"sha":"7f79c99e9a8f7cb79e9a0ad99e351e631784e555","author":{"name":"Igor Motov","email":"3b85b3e83e658d5d33308486a92b220edc8ae0a6@motovs.org"},"message":"Add descriptions to bulk tasks\n\nRelated to #21768","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/7f79c99e9a8f7cb79e9a0ad99e351e631784e555"},{"sha":"b1cef5fdf8e1f8e9982a4724986b2731ca4d522b","author":{"name":"Ryan Ernst","email":"8f18e670ec432ee5e15365d38d203f741b57c02e@iernst.net"},"message":"Remove 2.0 prerelease version constants (#22004)\n\n* Remove 2.0 prerelease version constants\r\n\r\nThis is a start to addressing #21887. This removes:\r\n* pre 2.0 snapshot format support\r\n* automatic units addition to cluster settings\r\n* bwc check for delete by query in pre 2.0 indexes","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/b1cef5fdf8e1f8e9982a4724986b2731ca4d522b"},{"sha":"36f598138afec1ff16afe9d160850a9ca19db83c","author":{"name":"Adrien Grand","email":"83387f1adf6f01406cba47ad9f87966de8fe24be@gmail.com"},"message":"Start using `ObjectParser` for aggs. (#22048)\n\nThis is an attempt to start moving aggs parsing to `ObjectParser`. There is\r\nstill A LOT to do, but ObjectParser is way better than the way aggregations\r\nparsing works today. For instance in most cases, we reject numbers that are\r\nprovided as strings, which we are supposed to accept since some client languages\r\n(looking at you Perl) cannot make sure to use the appropriate types.\r\n\r\nRelates to #22009","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/36f598138afec1ff16afe9d160850a9ca19db83c"},{"sha":"9524c81af97a40269ca82e303a130def98dd70bc","author":{"name":"Adrien Grand","email":"83387f1adf6f01406cba47ad9f87966de8fe24be@gmail.com"},"message":"Document the `locale` option of the `date` field. (#22050)\n\nThis also adds another level of protection against using the default locale.\r\nRelates to https://discuss.elastic.co/t/mapping-for-12h-date-format/68433/3.","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/9524c81af97a40269ca82e303a130def98dd70bc"},{"sha":"1bdf4a2c5b15ada1c76cb6981677b2525327f74c","author":{"name":"Adrien Grand","email":"83387f1adf6f01406cba47ad9f87966de8fe24be@gmail.com"},"message":"Partition-based include-exclude does not implement equals/hashcode/serialization correctly. (#22051)","distinct":false,"url":"https://api.github.com/repos/abeyad/elasticsearch/commits/1bdf4a2c5b15ada1c76cb6981677b2525327f74c"}]}
{"actor":{"display_login":"abeyad"}}