Re: New Apache Impala committer - Shant Hovsepian

Congrats! On Wed, Oct 14, 2020 at 11:09 AM Norbert Luksa wrote: > > Congratulations, Shant! > > On Wed, Oct 14, 2020 at 10:55 AM Laszlo Gaal > wrote: > > > Congratulations, Shant! > > > > On Wed, Oct 14, 2020 at 9:39 AM Tamas Mate wrote: > > > > > Congrats, Shant! > > > > > > On Wed, Oct 14,

Re: New Committer: Norbert Luksa

Congrats, Norbert! On Tue, Apr 7, 2020 at 8:35 PM Zoltán Borók-Nagy wrote: > > The Project Management Committee (PMC) for Apache Impala has > invited Norbert Luksa to become a committer and we are pleased to announce > that they have accepted. > Congratulations and welcome, Norbert!

Re: [DISCUSS] 3.2.0 release

. Jeszy On Mon, Mar 18, 2019 at 1:50 PM Quanlong Huang wrote: > > Hi Gabor, > > IMO, the change log is too detailed to be readable for users. There're no > any highlights. It's hard for users to find significant changes. A > summarized doc about new features and significant

Re: New PMC member: Quanlong Huang

Congrats Quanlong! On Mon, Mar 11, 2019 at 7:57 AM Jim Apple wrote: > > The Project Management Committee (PMC) for Apache Impala has invited > Quanlong Huang to become a PMC member and we are pleased to announce > that they have accepted. > > Congratulations and welcome, Quanlong!

Re: Next round of the Impala community meeting

I'd try to make it if the meeting was in a Europe-friendly time out of interest, but I don't feel I have much to contribute - probably not worth a reschedule by itself. On Wed, 6 Mar 2019 at 00:21, Lars Volker wrote: > > I'm good with that time too. However, I have not seen interest from folks >

Re: Impalad JVM OOM minutes after restart

until users started running queries. > > I0820 19:45:25.106437 25474 statestore.cc:568] Preparing initial > catalog-update topic update for impalad@XXX:22000. Size = 1.45 MB > > Brock > > On Tue, Aug 21, 2018 at 1:18 PM, Jeszy wrote: > > Hey, > > > > If it happen

Re: Impalad JVM OOM minutes after restart

Hey, If it happens shortly after a restart, there is a fair chance you're crashing while processing the initial catalog topic update. Statestore logs will tell you how big that was (it takes more memory to process it than the actual size of the update). If this is the case, it should also be

Re: New Impala committer - Quanlong Huang

Congrats Quanlong! On 17 August 2018 at 19:51, Csaba Ringhofer wrote: > Congrats! > > On Fri, Aug 17, 2018 at 6:32 PM, Philip Zeyliger > wrote: > >> Congrats! >> >> On Fri, Aug 17, 2018 at 9:29 AM Tim Armstrong >> wrote: >> >> > The Project Management Committee (PMC) for Apache Impala has

Re: Breaking changes after 3.0, versioning, IMPALA-3307

I think we should include it in 3.1, with the feature disabled by default (to not break on a minor upgrade), but recommend enabling it in docs and make it enabled by default in 4.0. On 11 June 2018 at 10:23, Jim Apple wrote: > Any more thoughts? This question is for everyone in the Impala

Re: [jira] [Created] (IMPALA-6620) Compute incremental stats for groups of partitions does not update stats correctly

It's addressed in IMPALA-5615. On 2018. Apr 2., Mon at 7:56, Jim Apple wrote: > I feel like I saw a similar JIRA and patch recently. Is this addressed In > another ticket? > > If not, it feels like a P2 to me: it’s not exactly incorrect, but I expect > it means that some

PHJ node assignment

IIUC, every row scanned in a partitioned hash join (both sides) is sent across the network (an exchange on HASH(key)). The targets of this exchange are nodes that have data locality with the left side of the join. Why does Impala do it that way? Since all rows are sent across the network anyway,