[Spark SQL] A single-pass resolution approach for the Catalyst Analyzer

logical plans and got 7-10x performance speedups. Is this something that would be interesting for the Spark community? What would be the best way to proceed with this idea? Regards, Vladimir Golubev.

Re: [Spark SQL] A single-pass resolution approach for the Catalyst Analyzer

accidentally break the analyzer? Are >existing tests enough? >- How can we introduce this incrementally? Can we run the analyzer in >mixed mode (both single pass rules and the existing tree traversal rules) >for a while? > > Cheers, > Herman > > On Fri, A

[VOTE][RESULT] Single-pass Analyzer for Catalyst

n (*) L. C. Hsieh (*) Angel Alvarez Vladimir Golubev +0: None -1: None Thanks to all participants! Vladimir.

Re: [VOTE][RESULT] Single-pass Analyzer for Catalyst

Alvarez Mich Talebzadeh Vladimir Golubev +0: None -1: None Vladimir. On Fri, Oct 4, 2024 at 11:34 AM Mich Talebzadeh wrote: > yes it was +1 > > +1 on the assumption that we should phase this release on an incremental > basis. Probably will take us to the end of release 5. > &g

[VOTE] Single-pass Analyzer for Catalyst

Hi all, I’d like to start a vote for a single-pass Analyzer for the Catalyst project. This project will introduce a new analysis framework to the Catalyst, which will eventually replace the fixed-point one. Please refer to the SPIP jira: https://issues.apache.org/jira/browse/SPARK-49834 [ ] +1:

Re: [VOTE] Single-pass Analyzer for Catalyst

>>>> > > >>>> > > >>>> > > On Mon, Sep 30, 2024 at 3:36 PM Dongjoon Hyun >>>> wrote: >>>> > > >>>> > >> Thank you for leading this, Vladimir, Reynold, Herman. >>>> > >> >&g

Re: [VOTE] Single-pass Analyzer for Catalyst

Spark 4.0.0. >>> >>> If it's expected that we are unable to deliver it, shall we postpone >>> this vote until 4.1.0 planning? >>> >>> Anyway, since SPARK-49834 has a target version 4.0.0 explicitly, >>> >>> -1 from my side. >>>