You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@drill.apache.org by "Poirier, Arnaud" <Ar...@concur.com> on 2016/01/29 19:40:18 UTC

Dynamodb connector for Drill

Hi,
Is there any plans to build a Dynamodb connector for Drill?
As a workaround, I exported the data from Dynamodb to S3 but the json exported is difficult to exploit especially with nested types.

{"trip_id":{"s":"68ead4e8-891f-4acd-87ea-f3abc1a99afd"},"display_name":{"s":"test3142"},"end_date":{"s":"2016-07-13 00:00:00"},"created_at":{"s":"2016-01-28 01:04:59.323616"},"user_id":{"s":"0b8cdea0-b899-11e5-9912-ba0be0483c18"},"start_date":{"s":"2016-07-12 00:00:00”}}

Thanks!

________________________________

This e-mail message is authorized for use by the intended recipient only and may contain information that is privileged and confidential. If you received this message in error, please call us immediately at (425) 590-5000 and ask to speak to the message sender. Please do not copy, disseminate, or retain this message unless you are the intended recipient. In addition, to ensure the security of your data, please do not send any unencrypted credit card or personally identifiable information to this email address. Thank you.

Re: Dynamodb connector for Drill

Posted by Hanifi Gunes <hg...@maprtech.com>.
I am not aware of DynamoDB plugin per se however if you have JDBC, ODBC
access into your instances you could use respective Drill plugins. Also, it
is relatively easy to write a new storage plugin. If you can consider
contributing native DynamoDB plugin that would be great. We can get you
jump started on dev@drill list.


The last, can you clarfiy what you mean by "the json exported is difficult
to exploit especially with nested types."? Do you hit any exceptions of
some sort?

-Hanifi

On Fri, Jan 29, 2016 at 10:40 AM, Poirier, Arnaud <Arnaud.Poirier@concur.com
> wrote:

> Hi,
> Is there any plans to build a Dynamodb connector for Drill?
> As a workaround, I exported the data from Dynamodb to S3 but the json
> exported is difficult to exploit especially with nested types.
>
> {"trip_id":{"s":"68ead4e8-891f-4acd-87ea-f3abc1a99afd"},"display_name":{"s":"test3142"},"end_date":{"s":"2016-07-13
> 00:00:00"},"created_at":{"s":"2016-01-28
> 01:04:59.323616"},"user_id":{"s":"0b8cdea0-b899-11e5-9912-ba0be0483c18"},"start_date":{"s":"2016-07-12
> 00:00:00”}}
>
> Thanks!
>
> ________________________________
>
> This e-mail message is authorized for use by the intended recipient only
> and may contain information that is privileged and confidential. If you
> received this message in error, please call us immediately at (425)
> 590-5000 and ask to speak to the message sender. Please do not copy,
> disseminate, or retain this message unless you are the intended recipient.
> In addition, to ensure the security of your data, please do not send any
> unencrypted credit card or personally identifiable information to this
> email address. Thank you.
>