{"push_id":738833683,"size":2,"distinct_size":2,"ref":"refs/heads/1.7_patched","head":"f69f42c29c8b81142f4e9d460764f23078219c6c","before":"1ec019ee28dc2b1116fbd1982423c9b6f75be11c","commits":[{"sha":"8bb65dc810c83565c16d4b5e8071b7e063a62018","author":{"email":"0c5d2c7a5e7bbd302e51760f7eb6e13b943bfac8@gmail.com","name":"Gregory"},"message":"elasticsearch/issues/4880","distinct":true,"url":"https://api.github.com/repos/Kamapcuc/elasticsearch/commits/8bb65dc810c83565c16d4b5e8071b7e063a62018"},{"sha":"f69f42c29c8b81142f4e9d460764f23078219c6c","author":{"email":"b13aba5297af128a2b2a07d1d5939f5cd94d7368@gmail.com","name":"Gregory"},"message":"* Automatically thread client based action listeners\nToday, we rely on the user to set request listener threads to true when they are on the client side in order not to block the IO threads on heavy operations. This proves to be very trappy for users, and end up creating problems that are very hard to debug.\nInstead, we can do the right thing, and automatically thread listeners that are used from the client when the client is a node client or a transport client.\nThis change also removes the ability to set request level listener threading, in the effort of simplifying the code path and reasoning around when something is threaded and when it is not.\ncloses #10940","distinct":true,"url":"https://api.github.com/repos/Kamapcuc/elasticsearch/commits/f69f42c29c8b81142f4e9d460764f23078219c6c"}]}