Re: Time for release v3.3.2

+10086. Wenchen Fan 于2023年2月1日 周三10:54写道： > +1, thanks! > > On Tue, Jan 31, 2023 at 3:17 PM Maxim Gekk > wrote: > >> +1 >> >> On Tue, Jan 31, 2023 at 10:12 AM John Zhuge wrote: >> >>> +1 Thanks Liang-Chi for driving the release! >>> >>> On Mon, Jan 30, 2023 at 10:26 PM Yuming Wang wrote: >>>

Re: Time for release v3.3.2

+1, thanks! On Tue, Jan 31, 2023 at 3:17 PM Maxim Gekk wrote: > +1 > > On Tue, Jan 31, 2023 at 10:12 AM John Zhuge wrote: > >> +1 Thanks Liang-Chi for driving the release! >> >> On Mon, Jan 30, 2023 at 10:26 PM Yuming Wang wrote: >> >>> +1 >>> >>> On Tue, Jan 31, 2023 at 12:18 PM yangjie01

Re: [DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

+1 On Tue, Jan 31, 2023 at 6:10 PM DB Tsai wrote: > +1 > > Sent from my iPhone > > On Jan 31, 2023, at 4:16 PM, Yuming Wang wrote: > >  > +1. > > On Wed, Feb 1, 2023 at 7:42 AM kazuyuki tanimura > wrote: > >> Great! Much appreciated, Mitch! >> >> Kazu >> >> On Jan 31, 2023, at 3:07 PM, Mich

Re: [DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

+1Sent from my iPhoneOn Jan 31, 2023, at 4:16 PM, Yuming Wang wrote:+1.On Wed, Feb 1, 2023 at 7:42 AM kazuyuki tanimura wrote:Great! Much appreciated, Mitch! KazuOn Jan 31, 2023, at 3:07 PM, Mich Talebzadeh wrote:Thanks, Kazu.I followed that template link and indeed

Re: [DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

+1. On Wed, Feb 1, 2023 at 7:42 AM kazuyuki tanimura wrote: > Great! Much appreciated, Mitch! > > Kazu > > On Jan 31, 2023, at 3:07 PM, Mich Talebzadeh > wrote: > > Thanks, Kazu. > > I followed that template link and indeed as you pointed out it is a common > template. If it works then it is

Re: [DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

Great! Much appreciated, Mitch! Kazu > On Jan 31, 2023, at 3:07 PM, Mich Talebzadeh > wrote: > > Thanks, Kazu. > > I followed that template link and indeed as you pointed out it is a common > template. If it works then it is what it is. > > I will be going through your design proposals and

Re: [DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

Thanks, Kazu. I followed that template link and indeed as you pointed out it is a common template. If it works then it is what it is. I will be going through your design proposals and hopefully we can review it. Regards, Mich view my Linkedin profile

Re: [DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

Thank you Mich. I followed the instruction at https://spark.apache.org/improvement-proposals.html and used its template. While we are open to revise our design doc, it seems more like you are proposing the community to change the instruction

Re: [DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

Hi, Thanks for these proposals. good suggestions. Is this style of breaking down your approach standard? My view would be that perhaps it makes more sense to follow the industry established approach of breaking down your technical proposal into: 1. Background 2. Objective 3. Scope

[DISCUSS] SPIP: Lazy Materialization for Parquet Read Performance Improvement

Hi everyone, I would like to start a discussion on “Lazy Materialization for Parquet Read Performance Improvement" Chao and I propose a Parquet reader with lazy materialization. For Spark-SQL filter operations, evaluating the filters first and lazily materializing only the used values can