+1
On Wed, Sep 19, 2018 at 8:07 AM Ted Yu wrote:
> +1
>
> Original message
> From: Dongjin Lee
> Date: 9/19/18 7:20 AM (GMT-08:00)
> To: dev
> Subject: Re: from_csv
>
> Another +1.
>
> I already experienced this case several times.
>
+1
Original message From: Dongjin Lee Date:
9/19/18 7:20 AM (GMT-08:00) To: dev Subject: Re:
from_csv
Another +1.
I already experienced this case several times.
On Mon, Sep 17, 2018 at 11:03 AM Hyukjin Kwon wrote:
+1 for this idea since text parsing in CSV/JSON is quite
Another +1.
I already experienced this case several times.
On Mon, Sep 17, 2018 at 11:03 AM Hyukjin Kwon wrote:
> +1 for this idea since text parsing in CSV/JSON is quite common.
>
> One thing is about schema inference likewise with JSON functionality. In
> case of JSON, we added schema_of_json
+1 for this idea since text parsing in CSV/JSON is quite common.
One thing is about schema inference likewise with JSON functionality. In
case of JSON, we added schema_of_json for it and same thing should be able
to apply to CSV too.
If we see some more needs for it, we can consider a function lik
Hi Reynold,
> i'd make this as consistent as to_json / from_json as possible
Sure, new function from_csv() has the same signature as from_json().
> how would this work in sql? i.e. how would passing options in work?
The options are passed to the function via map, for example:
select from_csv('2
makes sense - i'd make this as consistent as to_json / from_json as
possible.
how would this work in sql? i.e. how would passing options in work?
--
excuse the brevity and lower case due to wrist injury
On Sat, Sep 15, 2018 at 2:58 AM Maxim Gekk
wrote:
> Hi All,
>
> I would like to propose ne
