From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Date: Thu, 25 Apr 2019 19:42:41 +0300 From: Konstantin Osipov Subject: Re: [tarantool-patches] Re: [PATCH v3 6/7] Add merger for tuples streams (C part) Message-ID: <20190425164241.GB7320@atlas> References: <963ad528ad35199943931150956c1d5e2c374c40.1554906327.git.alexander.turenko@tarantool.org> <20190425114343.GM29257@atlas> <20190425133227.mvell3bwcbhzqkyb@tkn_work_nb> <20190425134539.GA10572@atlas> <20190425153210.kbwzjlq3fdjwogcn@tkn_work_nb> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190425153210.kbwzjlq3fdjwogcn@tkn_work_nb> To: Alexander Turenko Cc: tarantool-patches@freelists.org, Vladimir Davydov List-ID: * Alexander Turenko [19/04/25 18:36]: > Anyway, I see the word 'input' is quite often in map-reduce libraries > documentation. Should we use it instead of 'source'? merge_input or > merger_input? The problem is not with the word "source", it's with the word "merger". -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov