+1 (for what it's worth)
Thanks for making such a robust proposal, i'm excited to see the new work
coming from this
> On Mar 8, 2021, at 11:44 PM, Dongjoon Hyun wrote:
>
> +1 (binding)
>
> Thank you, Ryan.
>
> Bests,
> Dongjoon.
>
>
> On Mon, Mar 8, 2021 at 5:20 PM Chao Sun
+1 (binding)
Thank you, Ryan.
Bests,
Dongjoon.
On Mon, Mar 8, 2021 at 5:20 PM Chao Sun wrote:
> +1 (non-binding)
>
> On Mon, Mar 8, 2021 at 5:13 PM John Zhuge wrote:
>
>> +1 (non-binding)
>>
>> On Mon, Mar 8, 2021 at 4:32 PM Holden Karau wrote:
>>
>>> +1 (binding)
>>>
>>> On Mon, Mar 8,
+1 (non-binding)
On Mon, Mar 8, 2021 at 5:13 PM John Zhuge wrote:
> +1 (non-binding)
>
> On Mon, Mar 8, 2021 at 4:32 PM Holden Karau wrote:
>
>> +1 (binding)
>>
>> On Mon, Mar 8, 2021 at 3:56 PM Ryan Blue wrote:
>>
>>> Hi everyone, I’d like to start a vote for the FunctionCatalog design
>>>
+1 (non-binding)
On Mon, Mar 8, 2021 at 4:32 PM Holden Karau wrote:
> +1 (binding)
>
> On Mon, Mar 8, 2021 at 3:56 PM Ryan Blue wrote:
>
>> Hi everyone, I’d like to start a vote for the FunctionCatalog design
>> proposal (SPIP).
>>
>> The proposal is to add a FunctionCatalog interface that can
+1 (binding)
On Mon, Mar 8, 2021 at 3:56 PM Ryan Blue wrote:
> Hi everyone, I’d like to start a vote for the FunctionCatalog design
> proposal (SPIP).
>
> The proposal is to add a FunctionCatalog interface that can be used to
> load and list functions for Spark to call. There are interfaces for
Hi everyone, I’d like to start a vote for the FunctionCatalog design
proposal (SPIP).
The proposal is to add a FunctionCatalog interface that can be used to load
and list functions for Spark to call. There are interfaces for scalar and
aggregate functions.
In the discussion we’ve come to
Thank you Dongjoon.
I'm going to cut the branch now. Hopefully I can make it soon (need to get
familiar with the process as first time :) )
Liang-Chi
Dongjoon Hyun-2 wrote
> Thank you, Liang-Chi! Next Monday sounds good.
>
> To All. Please ping Liang-Chi if you have a missed backport.
>
>
Hi,
I do not think this could cause any problem.
The PODs polling snapshots would contain those PODs which were inactivated
before. Every time when the polling is triggered, so here it make sense to
handle them like deleted PODs and skip those.
On the other hand PODs watcher only informed about
