[GSoC Idea Discussion] "Thrift datatype support" Project
Hi,
I am Udit Juneja, a Computer Science undergraduate student at Thapar
Institute of Engineering and Technology, India. I am interested in
contributing to PostgreSQL.
A brief introduction about me:
I am familiar with programming languages (C, C++, Python, SQL).
I am interested in "Thrift datatype support" project. I have already
started exploring PostgreSQL, and the libraries involved in this project.
I would like to discuss the idea further and maybe submit a proposal in
GSoC later.
Regards,
Udit Juneja
Isn't thrift the communications protocol?
Do we have foreign server support for parquet and ORC files?
On Tue, Feb 13, 2018 at 8:40 AM, Udit Juneja <uditjuneja1@gmail.com> wrote:
Show quoted text
Hi,
I am Udit Juneja, a Computer Science undergraduate student at Thapar
Institute of Engineering and Technology, India. I am interested in
contributing to PostgreSQL.A brief introduction about me:
I am familiar with programming languages (C, C++, Python, SQL).I am interested in "Thrift datatype support" project. I have already
started exploring PostgreSQL, and the libraries involved in this project.I would like to discuss the idea further and maybe submit a proposal in
GSoC later.Regards,
Udit Juneja
Technically speaking, Thrift is "language-independent"
serialization-deserialization format with clean approach to backward
compatibility.
I think Thrift (or something like that) can be useful, as it can generate
serializers/deserializers for lots of languages.
PostgreSQL's "binary" format is tied to the PostgreSQL and it has to be
reimplemented for each and every client language.
"text" format is non-trivial as well (e.g. it is hard to get quoting right
for structs, and text is server-locale-dependent)
Vladimir
On Tue, Feb 13, 2018 at 10:24 AM, Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
Technically speaking, Thrift is "language-independent"
serialization-deserialization format with clean approach to backward
compatibility.I think Thrift (or something like that) can be useful, as it can generate
serializers/deserializers for lots of languages.
PostgreSQL's "binary" format is tied to the PostgreSQL and it has to be
reimplemented for each and every client language."text" format is non-trivial as well (e.g. it is hard to get quoting right
for structs, and text is server-locale-dependent)Vladimir
Thanks. I've been helping a coworker with an older parquet writer and
the URL for the hive metastore uses a thrift:// scheme. That is why I
thought it is a communications protocol.