+1 if we add them to Alternative config.
Kazuaki Ishizaki
From: Takeshi Yamamuro
To: Wenchen Fan
Cc: Spark dev list
Date: 2020/02/13 16:02
Subject:[EXTERNAL] Re: [DISCUSS] naming policy of Spark configs
+1; the idea sounds reasonable.
Bests,
Takeshi
On Thu, Feb 13
>>>>> Thank you, Wenchen.
>>>>>
>>>>> The new policy looks clear to me. +1 for the explicit policy.
>>>>>
>>>>> So, are we going to revise the existing conf names before 3.0.0
>>>>> release?
>
t;>>> The new policy looks clear to me. +1 for the explicit policy.
>>>>
>>>> So, are we going to revise the existing conf names before 3.0.0 release?
>>>>
>>>> Or, is it applied to new up-coming configurations from now?
>>>>
>&
new up-coming configurations from now?
>>>
>>> Bests,
>>> Dongjoon.
>>>
>>> On Wed, Feb 12, 2020 at 7:43 AM Wenchen Fan wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'd like to di
f names before 3.0.0 release?
>>
>> Or, is it applied to new up-coming configurations from now?
>>
>> Bests,
>> Dongjoon.
>>
>> On Wed, Feb 12, 2020 at 7:43 AM Wenchen Fan wrote:
>>
>>> Hi all,
>>>
>>> I'd like to discuss
on.
>
> On Wed, Feb 12, 2020 at 7:43 AM Wenchen Fan wrote:
>
>> Hi all,
>>
>> I'd like to discuss the naming policy of Spark configs, as for now it
>> depends on personal preference which leads to inconsistent namings.
>>
>> In g
conf names before 3.0.0 release?
>
> Or, is it applied to new up-coming configurations from now?
>
> Bests,
> Dongjoon.
>
>> On Wed, Feb 12, 2020 at 7:43 AM Wenchen Fan wrote:
>> Hi all,
>>
>> I'd like to discuss the naming policy of Spark con
d0...@gmail.com ) > wrote:
>
>
>> Hi all,
>>
>>
>> I'd like to discuss the naming policy of Spark configs, as for now it
>> depends on personal preference which leads to inconsistent namings.
>>
>>
>> In general,
all,
>
> I'd like to discuss the naming policy of Spark configs, as for now it
> depends on personal preference which leads to inconsistent namings.
>
> In general, the config name should be a noun that describes its meaning
> clearly.
> Good examples:
>
Hi all,
I'd like to discuss the naming policy of Spark configs, as for now it
depends on personal preference which leads to inconsistent namings.
In general, the config name should be a noun that describes its meaning
clearly.
Good examples:
spark.sql.session.timeZone
10 matches
Mail list logo