Cheng Pan

cc @cloud-fan @sunchao @ulysses-you @huaxingao

The rule `V2Writers` is placed in the optimizing phase but does something maybe should happen in analyzing phase like resolve function and implicit type cast. The current approach is trying...

@cloud-fan @sunchao sorry for bothering you again, please take a look when you have time.

> I guess AQE can also help us to coalesce and split too big partitions during writes. This should be covered by SPARK-37523. Thanks @cloud-fan @sunchao @aokolnychyi for reviewing and...

我遇到了几次这样的场景: 1. 某个method会偶尔触发bug, 导致cpu 100%, 由于日志的缺失, 不能确定到底是什么入参触发了method的bug; 2. 因为Filter的bug, 某个(或某些)特定HTTP请求在被Dispatch到具体的业务Controller之前, 在Tomcat内部就发生了错误, 导致死循环, 同样的的因缺少日志打印, 而不能迅速定位是哪个url请求触发了bug; 如果采用Arthas的watch机制, 也就意味着不能直接从已经出错的线程栈堆栈中提取变量信息, 而必须等待下次bug触发才能获取到一些信息; 但是在已经出错的线程栈帧中, 应该是有method调用链路中一些变量信息的, 如果能够展示出来, 或许对迅速定位bug原因有极大帮助. 我没有在Arthas 3.1.1版本文档中找到类似的功能, 也可能是我对文档漏读或误读忽略了该功能.

> > 我遇到了几次这样的场景: > > > > 1. 某个method会偶尔触发bug, 导致cpu 100%, 由于日志的缺失, 不能确定到底是什么入参触发了method的bug; > > 2. 因为Filter的bug, 某个(或某些)特定HTTP请求在被Dispatch到具体的业务Controller之前, 在Tomcat内部就发生了错误, 导致死循环, 同样的的因缺少日志打印, 而不能迅速定位是哪个url请求触发了bug; > > > > 如果采用Arthas的watch机制, 也就意味着不能直接从已经出错的线程栈堆栈中提取变量信息, 而必须等待下次bug触发才能获取到一些信息; >...

Hadoop, Spark, Hive, and Trino support run service both on frontend or as daemon, can we follow them?

I'm neutral for `activeByDefault`, but recommend to unify the profile style, e.g. ``` spark-2.3 spark-2.4 spark-3.0 spark-3.1 spark-3.2 ```

> ... the default profile is the version which we mainly support. With the community growing, other versions of Spark may be adopted by users in large-scale production, how about...

Hi @zhongjun2, currently, esdk-obs-java:3.20.4.2 still depends on okhttp, I checked the latest https://mvnrepository.com/artifact/com.huaweicloud/esdk-obs-java/3.22.3.1 removed (or shaded?) it, could you please update it?