RE: PostgreSQL and big data - FDW - Mailing list pgsql-hackers

From ROS Didier
Subject RE: PostgreSQL and big data - FDW
Date
Msg-id 09065d806143460fa090b44f5e095ecb@NOEINTPEXMU001.NEOPROD.EDF.FR
Whole thread Raw
In response to Re: PostgreSQL and big data - FDW  (Stephen Frost <sfrost@snowman.net>)
Responses Re: PostgreSQL and big data - FDW
List pgsql-hackers
Hi Stephen

My EDF company is very interested in this feature (KERBEROS authentication method and hdfs_fdw ).
Is it possible to know how many days of development does this represent ? who can develop this implementation ? what
cost? 

Best Regards
Didier ROS
EDF
-----Message d'origine-----
De : sfrost@snowman.net [mailto:sfrost@snowman.net]
Envoyé : mercredi 24 juin 2020 18:53
À : Bruce Momjian <bruce@momjian.us>
Cc : ROS Didier <didier.ros@edf.fr>; pgsql-hackers@lists.postgresql.org
Objet : Re: PostgreSQL and big data - FDW

Greetings,

* Bruce Momjian (bruce@momjian.us) wrote:
> On Wed, Jun 24, 2020 at 09:05:30AM +0000, ROS Didier wrote:
> > I would like to use a Foreign Data Wrapper (FDW) to connect to a
> > HADOOP cluster which uses KERBEROS authentication.

Sadly, not really.

> > is it possible to achieve this ? which FDW should be used ?
>
> Well, I would use the Hadoop FDW:
>
>     https://github.com/EnterpriseDB/hdfs_fdw
>
> and it only supports these authentication methods:
>
>     Authentication Support
>
>     The FDW supports NOSASL and LDAP authentication modes. In order to use
>     NOSASL do not specify any OPTIONS while creating user mapping. For LDAP
>     username and password must be specified in OPTIONS while creating user mapping.
>
> Not every FDW supports every Postgres server authentication method.

That isn't really the issue here, the problem is really that the GSSAPI support in PG today doesn't support credential
delegation-if it did, then the HDFS FDW (and the postgres FDW) could be easily extended to leverage those delegated
credentialsto connect. 

That's been something that's been on my personal todo list of things to work on but unfortunately I've not, as yet, had
timeto go implement.  I don't actually think it would be very hard- if someone writes it, I'd definitely review it. 

Thanks,

Stephen



Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires
etles informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa
destination,toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. 

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le
divulguerou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre
système,ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous
remercionségalement d'en avertir immédiatement l'expéditeur par retour du message. 

Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont
sécuriséesou dénuées de toute erreur ou virus. 
____________________________________________________

This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in
thisMessage is confidential. Any use of information contained in this Message not in accord with its purpose, any
disseminationor disclosure, either whole or partial, is prohibited except formal approval. 

If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this
messagein error, please delete it and all copies from your system and notify the sender immediately by return message. 

E-mail communication cannot be guaranteed to be timely secure, error or virus-free.




pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: some more pg_dump refactoring
Next
From: Daniel Gustafsson
Date:
Subject: Re: Ought to use heap_multi_insert() for pg_attribute/dependinsertions?