+0 (non-binding)
I think there are benefits to unifying all the Spark-internal datasources
into a common public API for sure. It will serve as a forcing function to
ensure that those internal datasources aren't advantaged vs datasources
developed externally as plugins to Spark, and that all Spark
+1 (binding)
I personally believe that there is quite a big difference between having a
generic data source interface with a low surface area and pushing down a
significant part of query processing into a datasource. The later has much
wider wider surface area and will require us to stabilize most
In a separate conversation about bugs and a security issue fixed in 2.1.x
and 2.0.x, Marcelo suggested it could be time for a maintenance release.
I'm not sure what our stance on 2.0.x is, but 2.1.2 seems like it could be
valuable to release.
Thoughts? I believe Holden had expressed interest in ev
For those following along, see discussions at
https://github.com/apache/spark/pull/19134
It's now also clear that we'd need to remove Kafka 0.8 examples if Kafka
0.8 becomes optional. I think that's all reasonable but the change is
growing beyond just putting it behind a profile.
On Wed, Sep 6, 2
+1 (non-binding)
Thanks for making the updates reflected in the current PR. It would be
great to see the doc updated before it is finally published though.
Right now it feels like this SPIP is focused more on getting the basics
right for what many datasources are already doing in API V1 combined
Hi all,
I've written a new Spark feature and I would love to have a committer take a
look at it. I want to increase Spark performance when using dynamic allocation
by preserving cached data.
The PR and Jira ticket are here:
https://github.com/apache/spark/pull/19041
https://issues.apache.org/j
+1
On Thu, Sep 7, 2017 at 9:32 AM, Ryan Blue wrote:
> +1 (non-binding)
>
> Thanks for making the updates reflected in the current PR. It would be
> great to see the doc updated before it is finally published though.
>
> Right now it feels like this SPIP is focused more on getting the basics
> ri
+1 as well
On Thu, Sep 7, 2017 at 9:12 PM, Michael Armbrust
wrote:
> +1
>
> On Thu, Sep 7, 2017 at 9:32 AM, Ryan Blue
> wrote:
>
>> +1 (non-binding)
>>
>> Thanks for making the updates reflected in the current PR. It would be
>> great to see the doc updated before it is finally published though
+1
Reynold Xin 于2017年9月7日 周四下午12:04写道：
> +1 as well
>
> On Thu, Sep 7, 2017 at 9:12 PM, Michael Armbrust
> wrote:
>
>> +1
>>
>> On Thu, Sep 7, 2017 at 9:32 AM, Ryan Blue
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>> Thanks for making the updates reflected in the current PR. It would be
>>> great t
+1!
As of today,
For 2.1.2, we have 87 commits. (2.1.1 was released 4 months ago)
For 2.2.1, we have 95 commits. (2.2.0 was released 2 months ago)
Can we have 2.2.1, too?
Bests,
Dongjoon.
On Thu, Sep 7, 2017 at 2:14 AM, Sean Owen wrote:
> In a separate conversation about bugs and a security
+1 (non-binding).
On Thu, Sep 7, 2017 at 12:46 PM, 蒋星博 wrote:
> +1
>
>
> Reynold Xin 于2017年9月7日 周四下午12:04写道：
>
>> +1 as well
>>
>> On Thu, Sep 7, 2017 at 9:12 PM, Michael Armbrust
>> wrote:
>>
>>> +1
>>>
>>> On Thu, Sep 7, 2017 at 9:32 AM, Ryan Blue
>>> wrote:
>>>
+1 (non-binding)
>>
I'd be happy to manage the 2.1.2 maintenance release (and 2.2.1 after that)
if people are ok with a committer / me running the release process rather
than a full PMC member.
On Thu, Sep 7, 2017 at 1:05 PM, Dongjoon Hyun
wrote:
> +1!
>
> As of today,
>
> For 2.1.2, we have 87 commits. (2.1.1 was
Hi,
I am upgrading my Spark application from Spark 2.1 to 2.2. I found that in
many places that qualifiers of AttributeReferences for base tables are no
longer existing. Is there any reason to take out qualifiers from
AttributeReferences? Thanks.
Best regards,
Ey-Chih Chow
--
Sent from:
+1 (non-binding) Great to see data source API is going to be improved!
best regards,
-Zhenhua(Xander)
发件人: Dongjoon Hyun [mailto:dongjoon.h...@gmail.com]
发送时间: 2017年9月8日 4:07
收件人: 蒋星博
抄送: Michael Armbrust; Reynold Xin; Andrew Ash; Herman van Hövell tot
Westerflier; Ryan Blue; Spark dev list; Su
+1 (non-binding) for the goals and non-goals of this SPIP. I think it's
fine to work out the minor details of the API during review.
Bryan
On Wed, Sep 6, 2017 at 5:17 AM, Takuya UESHIN
wrote:
> Hi all,
>
> Thank you for voting and suggestions.
>
> As Wenchen mentioned and also we're discussing
Hi Spark Experts,
Can someone point me to some examples for non-linear (DAG) ML pipelines.
That would be of great help.
Thanks much in advance
-Srikanth
Hi,
Pranay/Joseph, Can you share an example of ML DAG pipeline?
Thanks,
-Srikanth
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
17 matches
Mail list logo
