Since it sounds like there is consensus here, I've opened an issue for
this: https://issues.apache.org/jira/browse/SPARK-23889
On Sun, Apr 1, 2018 at 9:32 AM, Patrick Woody
wrote:
> Yep, that sounds reasonable to me!
>
> On Fri, Mar 30, 2018 at 5:50 PM, Ted Yu wrote:
>
>> +1
>>
>> Orig
Thank you Jose for the quick reply!
I have made myself a watcher on them.
From: Joseph Torres
Date: Friday, April 6, 2018 at 10:41 AM
To: "Thakrar, Jayesh"
Cc: "dev@spark.apache.org"
Subject: Re: Spark 2.3 V2 Datasource API questions
Thanks for trying it out!
We haven't hooked continuous stre
Thanks for trying it out!
We haven't hooked continuous streaming up to query.status or
query.recentProgress yet - commit() should be called under the hood, we
just don't yet report that it is. I've filed SPARK-23886 and SPARK-23887 to
track the work to add those things.
The issue with printing wa
First of all thank you to the Spark dev team for coming up with the
standardized and intuitive API interfaces.
I am sure it will encourage integrating a lot more new datasource integration.
I have been creating playing with the API and have some questions on the
continuous streaming API
(see htt
Hi Matthias,
This doeesn't look possible now. It may be worth filing an improvement
jira for.
But I'm trying to understand what you're trying to do a little better. So
you intentionally have each thread create a new unique pool when its
submits a job? So that pool will just get the default poo
