Re: GSoC 2018: thrift encoding format

From: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>
To: Charles Cui <charles(dot)cui1984(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Subject: Re: GSoC 2018: thrift encoding format
Date: 2018-05-03 09:39:15
Message-ID: 20180503093914.GA27569@e733.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Charles,

> Thanks for your confirm Aleksander!
> Also I am thinking of how to deal with complex
> data structure like map, list, or set. I guess one possible
> solution is to get raw data bytes for these data structure?
> Otherwise it could be hard to wrap into a Datum.

Personally I think raw data bytes are OK if functions for getting all
keys and values from this data are provided. Another possibility is just
converting Thrift to JSONB and vise versa. In this case only two
procedures are required and all the rest is available out-of-the-box.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2018-05-03 09:56:51 Re: GSOC 2018
Previous Message Craig Ringer 2018-05-03 08:54:05 Re: Anyone keep mirrors of old packages from apt.postgresql.org?