Tarantool development patches archive
 help / color / mirror / Atom feed
From: Oleg Babin <olegrok@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>,
	tarantool-patches@dev.tarantool.org,
	yaroslav.dynnikov@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH vshard 2/2] storage: introduce vshard.storage._call()
Date: Sun, 22 Mar 2020 08:08:04 +0300	[thread overview]
Message-ID: <1f571d45-179d-1b72-941d-3de21c2e8f11@tarantool.org> (raw)
In-Reply-To: <f68117750f221d0fe67134bd5058ac3c92db5be7.1584817081.git.v.shpilevoy@tarantool.org>

Thanks for your patch! See comments bellow.

On 21/03/2020 21:59, Vladislav Shpilevoy wrote:
> _call can't be properly integrated at this moment, because that
> would break rebalancing from old nodes. The new function is only
> added. Its usage and drop of old functions will happen in 0.1.17
> when I will finish and merge top commit from this branch:
> https://github.com/tarantool/vshard/tree/gerold103/gh-227-drop-old-functions

Could you add some "smoke" tests for "_call" function? The test in this 
patch only checks that it exists but don't check that it works. If it's 
hard and non-trivial ignore this comment.

>   
> +local service_call_api = {
> +    bucket_recv = bucket_recv,
> +    rebalancer_apply_routes = rebalancer_apply_routes,
> +    rebalancer_request_state = rebalancer_request_state,
> +}
> +
> +local function service_call(...)
> +    local service_name = select(1, ...)
> +    return service_call_api[service_name](select(2, ...))
> +end

What's about checking that "service_call_api[service_name]" exists?

  reply	other threads:[~2020-03-22  5:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 18:59 [Tarantool-patches] [PATCH vshard 0/2] vshard upgrade and _call Vladislav Shpilevoy
2020-03-21 18:59 ` [Tarantool-patches] [PATCH vshard 1/2] storage: introduce upgrade strategy Vladislav Shpilevoy
2020-03-22  5:05   ` Oleg Babin
2020-03-22 19:12     ` Vladislav Shpilevoy
2020-03-23  6:35       ` Oleg Babin
2020-03-23 22:32         ` Vladislav Shpilevoy
2020-03-24  4:32           ` Oleg Babin
2020-03-24 15:21   ` Yaroslav Dynnikov
2020-03-24 23:44     ` Vladislav Shpilevoy
2020-03-21 18:59 ` [Tarantool-patches] [PATCH vshard 2/2] storage: introduce vshard.storage._call() Vladislav Shpilevoy
2020-03-22  5:08   ` Oleg Babin [this message]
2020-03-22 19:13     ` Vladislav Shpilevoy
2020-03-23  6:42       ` Oleg Babin
2020-03-23 22:32         ` Vladislav Shpilevoy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1f571d45-179d-1b72-941d-3de21c2e8f11@tarantool.org \
    --to=olegrok@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --cc=yaroslav.dynnikov@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH vshard 2/2] storage: introduce vshard.storage._call()' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox