Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Reynold Xin
+1

On Mon, Mar 11 2024 at 7:38 PM, Jungtaek Lim < kabhwan.opensou...@gmail.com > 
wrote:

> 
> +1 (non-binding), thanks Gengliang!
> 
> 
> On Mon, Mar 11, 2024 at 5:46 PM Gengliang Wang < ltn...@gmail.com > wrote:
> 
> 
> 
>> Hi all,
>> 
>> I'd like to start the vote for SPIP: Structured Logging Framework for
>> Apache Spark
>> 
>> References:
>> 
>> 
>> * JIRA ticket ( https://issues.apache.org/jira/browse/SPARK-47240 )
>> * SPIP doc (
>> https://docs.google.com/document/d/1rATVGmFLNVLmtxSpWrEceYm7d-ocgu8ofhryVs4g3XU/edit?usp=sharing
>> )
>> * Discussion thread (
>> https://lists.apache.org/thread/gocslhbfv1r84kbcq3xt04nx827ljpxq )
>> 
>> 
>> Please vote on the SPIP for the next 72 hours:
>> 
>> [ ] +1: Accept the proposal as an official SPIP
>> [ ] +0
>> [ ] -1: I don’t think this is a good idea because …
>> 
>> Thanks!
>> 
>> Gengliang Wang
>> 
> 
>

smime.p7s
Description: S/MIME Cryptographic Signature


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Jungtaek Lim
+1 (non-binding), thanks Gengliang!

On Mon, Mar 11, 2024 at 5:46 PM Gengliang Wang  wrote:

> Hi all,
>
> I'd like to start the vote for SPIP: Structured Logging Framework for
> Apache Spark
>
> References:
>
>- JIRA ticket 
>- SPIP doc
>
> 
>- Discussion thread
>
>
> Please vote on the SPIP for the next 72 hours:
>
> [ ] +1: Accept the proposal as an official SPIP
> [ ] +0
> [ ] -1: I don’t think this is a good idea because …
>
> Thanks!
> Gengliang Wang
>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Scott
+1

On Mon, Mar 11, 2024 at 4:11 AM yangjie01 
wrote:

> +1
>
>
>
> Jie Yang
>
>
>
> *发件人**: *Haejoon Lee 
> *日期**: *2024年3月11日 星期一 17:09
> *收件人**: *Gengliang Wang 
> *抄送**: *dev 
> *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>
>
>
> +1
>
>
>
> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang  wrote:
>
> Hi all,
>
> I'd like to start the vote for SPIP: Structured Logging Framework for
> Apache Spark
>
>
> References:
>
>- JIRA ticket
>
> 
>- SPIP doc
>
> 
>- Discussion thread
>
> 
>
> Please vote on the SPIP for the next 72 hours:
>
> [ ] +1: Accept the proposal as an official SPIP
> [ ] +0
> [ ] -1: I don’t think this is a good idea because …
>
> Thanks!
>
> Gengliang Wang
>
>


Re: [Spark-Core] Improving Reliability of spark when Executors OOM

2024-03-11 Thread Ashish Singh
Hi Kalyan,

Is this something you are still interested in pursuing? There are some open
discussion threads on the doc you shared.

@Mridul Muralidharan  In what state are your efforts
along this? Is it something that your team is actively pursuing/ building
or are mostly planning right now? Asking so that we can align efforts on
this.

On Sun, Feb 18, 2024 at 10:32 PM xiaoping.huang <1754789...@qq.com> wrote:

> Hi all,
> Any updates on this project? This will be a very useful feature.
>
> xiaoping.huang
> 1754789...@qq.com
>
>  Replied Message 
> From kalyan 
> Date 02/6/2024 10:08
> To Jay Han 
> Cc Ashish Singh ,
>  Mridul Muralidharan ,
>  dev ,
>  
> 
> Subject Re: [Spark-Core] Improving Reliability of spark when Executors
> OOM
> Hey,
> Disk space not enough is also a reliability concern, but might need a diff
> strategy to handle it.
> As suggested by Mridul, I am working on making things more configurable in
> another(new) module… with that, we can plug in new rules for each type of
> error.
>
> Regards
> Kalyan.
>
> On Mon, 5 Feb 2024 at 1:10 PM, Jay Han  wrote:
>
>> Hi,
>> what about supporting for solving the disk space problem of "device space
>> isn't enough"? I think it's same as OOM exception.
>>
>> kalyan  于2024年1月27日周六 13:00写道:
>>
>>> Hi all,
>>>
>>
>>> Sorry for the delay in getting the first draft of (my first) SPIP out.
>>>
>>> https://docs.google.com/document/d/1hxEPUirf3eYwNfMOmUHpuI5dIt_HJErCdo7_yr9htQc/edit?pli=1
>>>
>>> Let me know what you think.
>>>
>>> Regards
>>> kalyan.
>>>
>>> On Sat, Jan 20, 2024 at 8:19 AM Ashish Singh  wrote:
>>>
 Hey all,

 Thanks for this discussion, the timing of this couldn't be better!

 At Pinterest, we recently started to look into reducing OOM failures
 while also reducing memory consumption of spark applications. We considered
 the following options.
 1. Changing core count on executor to change memory available per task
 in the executor.
 2. Changing resource profile based on task failures and gc metrics to
 grow or shrink executor memory size. We do this at application level based
 on the app's past runs today.
 3. K8s vertical pod autoscaler
 

 Internally, we are mostly getting aligned on option 2. We would love to
 make this happen and are looking forward to the SPIP.


 On Wed, Jan 17, 2024 at 9:34 AM Mridul Muralidharan 
 wrote:

>
> Hi,
>
>   We are internally exploring adding support for dynamically changing
> the resource profile of a stage based on runtime characteristics.
> This includes failures due to OOM and the like, slowness due to
> excessive GC, resource wastage due to excessive overprovisioning, etc.
> Essentially handles scale up and scale down of resources.
> Instead of baking these into the scheduler directly (which is already
> complex), we are modeling it as a plugin - so that the 'business logic' of
> how to handle task events and mutate state is pluggable.
>
> The main limitation I find with mutating only the cores is the limits
> it places on what kind of problems can be solved with it - and mutating
> resource profiles is a much more natural way to handle this
> (spark.task.cpus predates RP).
>
> Regards,
> Mridul
>
> On Wed, Jan 17, 2024 at 9:18 AM Tom Graves
>  wrote:
>
>> It is interesting. I think there are definitely some discussion
>> points around this.  reliability vs performance is always a trade off and
>> its great it doesn't fail but if it doesn't meet someone's SLA now that
>> could be as bad if its hard to figure out why.   I think if something 
>> like
>> this kicks in, it needs to be very obvious to the user so they can see 
>> that
>> it occurred.  Do you have something in place on UI or something that
>> indicates this? The nice thing is also you aren't wasting memory by
>> increasing it for all tasks when maybe you only need it for one or two.
>> The downside is you are only finding out after failure.
>>
>> I do also worry a little bit that in your blog post, the error you
>> pointed out isn't a java OOM but an off heap memory issue (overhead + 
>> heap
>> usage).  You don't really address heap memory vs off heap in that 
>> article.
>> Only thing I see mentioned is spark.executor.memory which is heap memory.
>> Obviously adjusting to only run one task is going to give that task more
>> overall memory but the reasons its running out in the first place could 
>> be
>> different.  If it was on heap memory for instance with more tasks I would
>> expect to see more GC and not executor OOM.  If you are getting executor
>> OOM you are likely using more off heap memory/stack space, etc then you
>> allocated.   Ultimately it would be nice to know 

Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Xinrong Meng
+1

Thanks @Gengliang Wang !

On Mon, Mar 11, 2024 at 1:09 PM Gengliang Wang  wrote:

> Hi Steve,
>
> thanks for the suggestion in this email thread and the SPIP doc! I will
> read the Audit Log and seek your feedback through PR reviews during the
> implementation process.
>
> > So worrying about how pass and manage that at the thread level matters.
>
> We can have a specific logger for org.apache.spark and only show specific
> keys from log context (MDC).
>
> > The files get really big fast. I'd recommend considering Avro as an
> option from the outset.
>
> Agree, I have mentioned how to address this issue in section Q6. What are
> the risks?
> 
>
>
> Thanks,
> Gengliang
>
> On Mon, Mar 11, 2024 at 9:30 AM huaxin gao  wrote:
>
>> +1
>>
>> On Mon, Mar 11, 2024 at 7:02 AM Wenchen Fan  wrote:
>>
>>> +1
>>>
>>> On Mon, Mar 11, 2024 at 5:26 PM Hyukjin Kwon 
>>> wrote:
>>>
 +1

 On Mon, 11 Mar 2024 at 18:11, yangjie01 
 wrote:

> +1
>
>
>
> Jie Yang
>
>
>
> *发件人**: *Haejoon Lee 
> *日期**: *2024年3月11日 星期一 17:09
> *收件人**: *Gengliang Wang 
> *抄送**: *dev 
> *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>
>
>
> +1
>
>
>
> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang 
> wrote:
>
> Hi all,
>
> I'd like to start the vote for SPIP: Structured Logging Framework for
> Apache Spark
>
>
> References:
>
>- JIRA ticket
>
> 
>- SPIP doc
>
> 
>- Discussion thread
>
> 
>
> Please vote on the SPIP for the next 72 hours:
>
> [ ] +1: Accept the proposal as an official SPIP
> [ ] +0
> [ ] -1: I don’t think this is a good idea because …
>
> Thanks!
>
> Gengliang Wang
>
>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Dongjoon Hyun
Ya, I also have a similar opinion with Mridul.

+1

Thank you, Gengliang.

Dongjoon.


On Mon, Mar 11, 2024 at 1:34 PM Mridul Muralidharan 
wrote:

>
>   I am supportive of the proposal - this is a step in the right direction !
> Additional metadata (explicit and inferred) for log records, and exposing
> them for indexing is extremely useful.
>
> The specifics of the API still need some work IMO and does not need to be
> this disruptive, but I consider that is orthogonal to this vote itself -
> and something we need to iterate upon during PR reviews.
>
> +1
>
> Regards,
> Mridul
>
>
> On Mon, Mar 11, 2024 at 11:09 AM Mich Talebzadeh <
> mich.talebza...@gmail.com> wrote:
>
>> +1
>>
>> Mich Talebzadeh,
>> Dad | Technologist | Solutions Architect | Engineer
>> London
>> United Kingdom
>>
>>
>>view my Linkedin profile
>> 
>>
>>
>>  https://en.everybodywiki.com/Mich_Talebzadeh
>>
>>
>>
>> *Disclaimer:* The information provided is correct to the best of my
>> knowledge but of course cannot be guaranteed . It is essential to note
>> that, as with any advice, quote "one test result is worth one-thousand
>> expert opinions (Werner
>> Von Braun
>> )".
>>
>>
>> On Mon, 11 Mar 2024 at 09:27, Hyukjin Kwon  wrote:
>>
>>> +1
>>>
>>> On Mon, 11 Mar 2024 at 18:11, yangjie01 
>>> wrote:
>>>
 +1



 Jie Yang



 *发件人**: *Haejoon Lee 
 *日期**: *2024年3月11日 星期一 17:09
 *收件人**: *Gengliang Wang 
 *抄送**: *dev 
 *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark



 +1



 On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang 
 wrote:

 Hi all,

 I'd like to start the vote for SPIP: Structured Logging Framework for
 Apache Spark


 References:

- JIRA ticket

 
- SPIP doc

 
- Discussion thread

 

 Please vote on the SPIP for the next 72 hours:

 [ ] +1: Accept the proposal as an official SPIP
 [ ] +0
 [ ] -1: I don’t think this is a good idea because …

 Thanks!

 Gengliang Wang




Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Gengliang Wang
Hi Steve,

thanks for the suggestion in this email thread and the SPIP doc! I will
read the Audit Log and seek your feedback through PR reviews during the
implementation process.

> So worrying about how pass and manage that at the thread level matters.

We can have a specific logger for org.apache.spark and only show specific
keys from log context (MDC).

> The files get really big fast. I'd recommend considering Avro as an
option from the outset.

Agree, I have mentioned how to address this issue in section Q6. What are
the risks?



Thanks,
Gengliang

On Mon, Mar 11, 2024 at 9:30 AM huaxin gao  wrote:

> +1
>
> On Mon, Mar 11, 2024 at 7:02 AM Wenchen Fan  wrote:
>
>> +1
>>
>> On Mon, Mar 11, 2024 at 5:26 PM Hyukjin Kwon 
>> wrote:
>>
>>> +1
>>>
>>> On Mon, 11 Mar 2024 at 18:11, yangjie01 
>>> wrote:
>>>
 +1



 Jie Yang



 *发件人**: *Haejoon Lee 
 *日期**: *2024年3月11日 星期一 17:09
 *收件人**: *Gengliang Wang 
 *抄送**: *dev 
 *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark



 +1



 On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang 
 wrote:

 Hi all,

 I'd like to start the vote for SPIP: Structured Logging Framework for
 Apache Spark


 References:

- JIRA ticket

 
- SPIP doc

 
- Discussion thread

 

 Please vote on the SPIP for the next 72 hours:

 [ ] +1: Accept the proposal as an official SPIP
 [ ] +0
 [ ] -1: I don’t think this is a good idea because …

 Thanks!

 Gengliang Wang




Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread huaxin gao
+1

On Mon, Mar 11, 2024 at 7:02 AM Wenchen Fan  wrote:

> +1
>
> On Mon, Mar 11, 2024 at 5:26 PM Hyukjin Kwon  wrote:
>
>> +1
>>
>> On Mon, 11 Mar 2024 at 18:11, yangjie01 
>> wrote:
>>
>>> +1
>>>
>>>
>>>
>>> Jie Yang
>>>
>>>
>>>
>>> *发件人**: *Haejoon Lee 
>>> *日期**: *2024年3月11日 星期一 17:09
>>> *收件人**: *Gengliang Wang 
>>> *抄送**: *dev 
>>> *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>>>
>>>
>>>
>>> +1
>>>
>>>
>>>
>>> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang 
>>> wrote:
>>>
>>> Hi all,
>>>
>>> I'd like to start the vote for SPIP: Structured Logging Framework for
>>> Apache Spark
>>>
>>>
>>> References:
>>>
>>>- JIRA ticket
>>>
>>> 
>>>- SPIP doc
>>>
>>> 
>>>- Discussion thread
>>>
>>> 
>>>
>>> Please vote on the SPIP for the next 72 hours:
>>>
>>> [ ] +1: Accept the proposal as an official SPIP
>>> [ ] +0
>>> [ ] -1: I don’t think this is a good idea because …
>>>
>>> Thanks!
>>>
>>> Gengliang Wang
>>>
>>>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Mridul Muralidharan
  I am supportive of the proposal - this is a step in the right direction !
Additional metadata (explicit and inferred) for log records, and exposing
them for indexing is extremely useful.

The specifics of the API still need some work IMO and does not need to be
this disruptive, but I consider that is orthogonal to this vote itself -
and something we need to iterate upon during PR reviews.

+1

Regards,
Mridul


On Mon, Mar 11, 2024 at 11:09 AM Mich Talebzadeh 
wrote:

> +1
>
> Mich Talebzadeh,
> Dad | Technologist | Solutions Architect | Engineer
> London
> United Kingdom
>
>
>view my Linkedin profile
> 
>
>
>  https://en.everybodywiki.com/Mich_Talebzadeh
>
>
>
> *Disclaimer:* The information provided is correct to the best of my
> knowledge but of course cannot be guaranteed . It is essential to note
> that, as with any advice, quote "one test result is worth one-thousand
> expert opinions (Werner  Von
> Braun )".
>
>
> On Mon, 11 Mar 2024 at 09:27, Hyukjin Kwon  wrote:
>
>> +1
>>
>> On Mon, 11 Mar 2024 at 18:11, yangjie01 
>> wrote:
>>
>>> +1
>>>
>>>
>>>
>>> Jie Yang
>>>
>>>
>>>
>>> *发件人**: *Haejoon Lee 
>>> *日期**: *2024年3月11日 星期一 17:09
>>> *收件人**: *Gengliang Wang 
>>> *抄送**: *dev 
>>> *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>>>
>>>
>>>
>>> +1
>>>
>>>
>>>
>>> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang 
>>> wrote:
>>>
>>> Hi all,
>>>
>>> I'd like to start the vote for SPIP: Structured Logging Framework for
>>> Apache Spark
>>>
>>>
>>> References:
>>>
>>>- JIRA ticket
>>>
>>> 
>>>- SPIP doc
>>>
>>> 
>>>- Discussion thread
>>>
>>> 
>>>
>>> Please vote on the SPIP for the next 72 hours:
>>>
>>> [ ] +1: Accept the proposal as an official SPIP
>>> [ ] +0
>>> [ ] -1: I don’t think this is a good idea because …
>>>
>>> Thanks!
>>>
>>> Gengliang Wang
>>>
>>>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Denny Lee
+1 (non-binding)

On Sun, Mar 10, 2024 at 23:36 Gengliang Wang  wrote:

> Hi all,
>
> I'd like to start the vote for SPIP: Structured Logging Framework for
> Apache Spark
>
> References:
>
>- JIRA ticket 
>- SPIP doc
>
> 
>- Discussion thread
>
>
> Please vote on the SPIP for the next 72 hours:
>
> [ ] +1: Accept the proposal as an official SPIP
> [ ] +0
> [ ] -1: I don’t think this is a good idea because …
>
> Thanks!
>
> Gengliang Wang
>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Steve Loughran
I consider the context info as more important than just logging; at hadoop
level we do it to attach things like task/jobIds, kerberos principals etc
to all store requests.
https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/auditing.html

So worrying about how pass and manage that at the thread level matters.
Hadoop does various things like creating audit spans propagating it and the
IOStatistics context through submitter/task pools, so as to correlate
better all activity. After all, if something deleted all the files in a
table: you want to know who and what, just as you want to understand what
is overloading your store with too many GET requests.

You also need to think about cluster-wide context info, such as the
specific SQL query triggering all the work. This is context info which the
spark driver has to generate and which is then propagated down to the work
thread across the cluster. I'd like that in the Hadoop auditing stuff too.
if you are targeting hadoop 3.3.2+ only, I can provide some guidance as
having it go further down the stack can only be advantageous.

I actually played with generating Log4j to JSON lines a long, long time ago.
https://hadoop.apache.org/docs/r2.8.2/hadoop-project-dist/hadoop-common/api/org/apache/hadoop/log/Log4Json.html
The files get really big fast. I'd recommend considering Avro as an option
from the outset. It's also really good it's still be able to use ripgrep to
scan a few GB of gzipped output *and get all messages a few seconds either
side*.

One interesting place for the structured output is actually test reports.
Everyone is a bit crippled here because they are stuck using an XML test
result format which was written purely to match our XSL understanding at
the time (2000!) rather than thinking of the need to correlate integration
test output. It might be that scalatest can support better structure here
than a simple model of "tests and stack traces" + stdout/stderr. While
rethinking test output formats is quite a radical undertaking and not one I
would recommend to people, leaving the option open would be good.

Finally, if you plan for the structured output to be stable over time,
you're going to have to have a policy in place about making those logs part
of the spark public API -because they will implicitly be this. HDFS Audit
Log is one such log; I think there may actually even be some regression
tests.

On Mon, 11 Mar 2024 at 01:36, Gengliang Wang  wrote:

> Hi all,
>
> I'd like to start the vote for SPIP: Structured Logging Framework for
> Apache Spark
>
> References:
>
>- JIRA ticket 
>- SPIP doc
>
> 
>- Discussion thread
>
>
> Please vote on the SPIP for the next 72 hours:
>
> [ ] +1: Accept the proposal as an official SPIP
> [ ] +0
> [ ] -1: I don’t think this is a good idea because …
>
> Thanks!
> Gengliang Wang
>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Kent Yao
+1 (non-binding)


Kent Yao

Hyukjin Kwon  于2024年3月11日周一 17:26写道:
>
> +1
>
> On Mon, 11 Mar 2024 at 18:11, yangjie01  wrote:
>>
>> +1
>>
>>
>>
>> Jie Yang
>>
>>
>>
>> 发件人: Haejoon Lee 
>> 日期: 2024年3月11日 星期一 17:09
>> 收件人: Gengliang Wang 
>> 抄送: dev 
>> 主题: Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>>
>>
>>
>> +1
>>
>>
>>
>> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang  wrote:
>>
>> Hi all,
>>
>> I'd like to start the vote for SPIP: Structured Logging Framework for Apache 
>> Spark
>>
>>
>> References:
>>
>> JIRA ticket
>> SPIP doc
>> Discussion thread
>>
>> Please vote on the SPIP for the next 72 hours:
>>
>> [ ] +1: Accept the proposal as an official SPIP
>> [ ] +0
>> [ ] -1: I don’t think this is a good idea because …
>>
>> Thanks!
>>
>> Gengliang Wang

-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org



Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Mich Talebzadeh
+1

Mich Talebzadeh,
Dad | Technologist | Solutions Architect | Engineer
London
United Kingdom


   view my Linkedin profile



 https://en.everybodywiki.com/Mich_Talebzadeh



*Disclaimer:* The information provided is correct to the best of my
knowledge but of course cannot be guaranteed . It is essential to note
that, as with any advice, quote "one test result is worth one-thousand
expert opinions (Werner  Von
Braun )".


On Mon, 11 Mar 2024 at 09:27, Hyukjin Kwon  wrote:

> +1
>
> On Mon, 11 Mar 2024 at 18:11, yangjie01 
> wrote:
>
>> +1
>>
>>
>>
>> Jie Yang
>>
>>
>>
>> *发件人**: *Haejoon Lee 
>> *日期**: *2024年3月11日 星期一 17:09
>> *收件人**: *Gengliang Wang 
>> *抄送**: *dev 
>> *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>>
>>
>>
>> +1
>>
>>
>>
>> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang  wrote:
>>
>> Hi all,
>>
>> I'd like to start the vote for SPIP: Structured Logging Framework for
>> Apache Spark
>>
>>
>> References:
>>
>>- JIRA ticket
>>
>> 
>>- SPIP doc
>>
>> 
>>- Discussion thread
>>
>> 
>>
>> Please vote on the SPIP for the next 72 hours:
>>
>> [ ] +1: Accept the proposal as an official SPIP
>> [ ] +0
>> [ ] -1: I don’t think this is a good idea because …
>>
>> Thanks!
>>
>> Gengliang Wang
>>
>>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Wenchen Fan
+1

On Mon, Mar 11, 2024 at 5:26 PM Hyukjin Kwon  wrote:

> +1
>
> On Mon, 11 Mar 2024 at 18:11, yangjie01 
> wrote:
>
>> +1
>>
>>
>>
>> Jie Yang
>>
>>
>>
>> *发件人**: *Haejoon Lee 
>> *日期**: *2024年3月11日 星期一 17:09
>> *收件人**: *Gengliang Wang 
>> *抄送**: *dev 
>> *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>>
>>
>>
>> +1
>>
>>
>>
>> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang  wrote:
>>
>> Hi all,
>>
>> I'd like to start the vote for SPIP: Structured Logging Framework for
>> Apache Spark
>>
>>
>> References:
>>
>>- JIRA ticket
>>
>> 
>>- SPIP doc
>>
>> 
>>- Discussion thread
>>
>> 
>>
>> Please vote on the SPIP for the next 72 hours:
>>
>> [ ] +1: Accept the proposal as an official SPIP
>> [ ] +0
>> [ ] -1: I don’t think this is a good idea because …
>>
>> Thanks!
>>
>> Gengliang Wang
>>
>>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Hyukjin Kwon
+1

On Mon, 11 Mar 2024 at 18:11, yangjie01  wrote:

> +1
>
>
>
> Jie Yang
>
>
>
> *发件人**: *Haejoon Lee 
> *日期**: *2024年3月11日 星期一 17:09
> *收件人**: *Gengliang Wang 
> *抄送**: *dev 
> *主题**: *Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark
>
>
>
> +1
>
>
>
> On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang  wrote:
>
> Hi all,
>
> I'd like to start the vote for SPIP: Structured Logging Framework for
> Apache Spark
>
>
> References:
>
>- JIRA ticket
>
> 
>- SPIP doc
>
> 
>- Discussion thread
>
> 
>
> Please vote on the SPIP for the next 72 hours:
>
> [ ] +1: Accept the proposal as an official SPIP
> [ ] +0
> [ ] -1: I don’t think this is a good idea because …
>
> Thanks!
>
> Gengliang Wang
>
>


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread yangjie01
+1

Jie Yang

发件人: Haejoon Lee 
日期: 2024年3月11日 星期一 17:09
收件人: Gengliang Wang 
抄送: dev 
主题: Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

+1

On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang 
mailto:ltn...@gmail.com>> wrote:
Hi all,

I'd like to start the vote for SPIP: Structured Logging Framework for Apache 
Spark

References:

  *   JIRA 
ticket
  *   SPIP 
doc
  *   Discussion 
thread
Please vote on the SPIP for the next 72 hours:

[ ] +1: Accept the proposal as an official SPIP
[ ] +0
[ ] -1: I don’t think this is a good idea because …

Thanks!
Gengliang Wang


Re: [VOTE] SPIP: Structured Logging Framework for Apache Spark

2024-03-11 Thread Haejoon Lee
+1

On Mon, Mar 11, 2024 at 10:36 AM Gengliang Wang  wrote:

> Hi all,
>
> I'd like to start the vote for SPIP: Structured Logging Framework for
> Apache Spark
>
> References:
>
>- JIRA ticket 
>- SPIP doc
>
> 
>- Discussion thread
>
>
> Please vote on the SPIP for the next 72 hours:
>
> [ ] +1: Accept the proposal as an official SPIP
> [ ] +0
> [ ] -1: I don’t think this is a good idea because …
>
> Thanks!
> Gengliang Wang
>