Hi Quanlong, Thank you for adding me to the Contributors group and for the pointers.
I’ll start by looking into IMPALA-12956. The batch summary output for impala-profile-tool looks like a good first contribution and is close to the profile triage workflows I’m interested in. I’ll check the current issue details and assign it to myself if it is still unassigned. I’ll leave IMPALA-12955 for later since it sounds more refactoring-heavy and probably less suitable as a first contribution. I’ll also take a look at plan-graph.py. The profile visualization direction is interesting, especially for helping users and developers understand query profiles faster. Thanks again for the guidance. Best regards, Aleksandr пн, 25 мая 2026 г. в 05:47, Quanlong Huang <[email protected]>: > Hi Aleksandr, > > I've added you into the Contributors group. You should be able to assign > Impala JIRAs to yourself. > > Apart from IMPALA-13033, you can also look into other JIRAs: > IMPALA-12956 is also an unassigned JIRA for impala-profile-tool. It aims to > add a summary output for a batch of profiles. > IMPALA-12955 is another unassigned JIRA to slim down impala-profile-tool > which includes lots of unused dependencies. But this requires some > refactors and might not be suitable as a starting point. > > Apart from impala-profile-tool and the AI Query Profile Analyzer, we can > also develop/improve tools to help developers visualize or better > understand the profiles. E.g. There is a script in the repo to visualize > the query plan with > annotated information: bin/diagnostics/experimental/plan-graph.py > > Welcome and looking forward to your contribution! > > Best regards, > Quanlong > > On Fri, May 22, 2026 at 9:08 PM Александр Ефимов <[email protected]> > wrote: > > > Hi Impala devs, > > > > I’d like to start contributing in the query profile tooling area. > > > > My Apache Jira username is alexandrefimov. Could someone please add me to > > the Jira contributor whitelist so I can be assigned to issues? > > > > I work with Impala runtime profiles in production diagnostics, and > > IMPALA-13033 looks like a good small issue to start with: supporting > thrift > > profiles downloaded from the WebUI in impala-profile-tool. > > > > I see that IMPALA-13033 is currently assigned, so I wanted to check > whether > > it is still being worked on, or whether help would be useful. > > > > I also noticed the recent profile analyzer/parser/redactor work around > > IMPALA-14953 / IMPALA-14961 / IMPALA-14962. Before looking further into > > IMPALA-13033, I wanted to check whether it is still useful as a separate > > fix, or whether it is expected to be covered by the new parser interface > > work. > > > > If it is useful and nobody is actively working on it, I’d be happy to > take > > it. I’d keep the change limited to impala-profile-tool and add a focused > > test for the WebUI-downloaded thrift profile case. > > > > Thanks, > > Aleksandr > > >
