Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@dev.tarantool.org, kostja.osipov@gmail.com,
	alexander.turenko@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/1] box: export box_session_push to the public C API
Date: Tue, 21 Jan 2020 00:14:15 +0100	[thread overview]
Message-ID: <f93ca916-2ec4-ba5c-c052-177ef76d63e3@tarantool.org> (raw)
In-Reply-To: <1065f691482e681b779abd3698ec4489267c11fd.1579558507.git.v.shpilevoy@tarantool.org>

Alexander noticed that the patch crashes when C push
works from console. I am going to fix this by dumping
pushed data in the same way as with Lua pushes - decode
the data into YAML and return as a string.

If nobody has something against this.

Talking of YAML vs Lua output format - I am not going
to fix this in scope of this issue.

On 20/01/2020 23:16, Vladislav Shpilevoy wrote:
> It was a customer request. Nothing special here, the patch is
> trivial, with a couple of short notes:
> 
> 1) Sync argument was removed. It will disappear from Lua API as
>   well, according to #4689. Port is replaced with raw MessagePack,
>   because port is not a part of public API. Session is omitted as
>   well. Indeed, a user can't push to a foreign session, and the
>   current session can be obtained inside box_session_push(). And
>   anyway session is not in the public C API.
> 
> 2) Dump is done using obuf_dup(), just like tuple_to_obuf() does.
>   obuf_alloc() would be a bad call here, because it wouldn't be
>   able to split the pushed data into several obuf chunks, and
>   would cause obuf fragmentation.
> 
> Closes #4734
> ---
> Issue: https://github.com/tarantool/tarantool/issues/4734
> Branch: https://github.com/tarantool/tarantool/tree/gerold103/gh-4734-export-box-session-push
> 

  reply	other threads:[~2020-01-20 23:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 22:16 Vladislav Shpilevoy
2020-01-20 23:14 ` Vladislav Shpilevoy [this message]
2020-01-21  0:24 ` Alexander Turenko
2020-01-22  0:06   ` Vladislav Shpilevoy
2020-01-22  2:25     ` Alexander Turenko
2020-01-22 23:05       ` Vladislav Shpilevoy
2020-04-06 23:12         ` Igor Munkin
2020-04-07 23:20           ` Vladislav Shpilevoy
2020-04-06 23:40         ` Alexander Turenko
2020-03-30 20:42 ` Vladislav Shpilevoy
2020-03-30 21:03   ` Igor Munkin
2020-03-30 20:42 ` Vladislav Shpilevoy
2020-04-03  2:30   ` Nikita Pettik

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=f93ca916-2ec4-ba5c-c052-177ef76d63e3@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=kostja.osipov@gmail.com \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 1/1] box: export box_session_push to the public C API' \
    /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