[
https://issues.apache.org/jira/browse/IMPALA-15035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087764#comment-18087764
]
Aleksandr Efimov edited comment on IMPALA-15035 at 6/9/26 9:44 PM:
-------------------------------------------------------------------
Thanks [~gokul.kolady], that makes sense. I’ll hold off on IMPALA-15035 until
the v2 profile structure stabilizes.
For your team discussion, the directly relevant pieces on my side are the
profile parsing / profile-tool changes and V2/aggregated profile fixtures. I
also have some adjacent experience from testing profile-analysis and redaction
workflows with sanitized data, and can share design notes or pointers where
useful.
was (Author: JIRAUSER313444):
{*}{*}Thanks [~gokul.kolady], that makes sense. I’ll hold off on IMPALA-15035
until the v2 profile structure stabilizes.
For your team discussion, the directly relevant pieces on my side are the
profile parsing / profile-tool changes and V2/aggregated profile fixtures. I
also have some adjacent experience from testing profile-analysis and redaction
workflows with sanitized data, and can share design notes or pointers where
useful.
> AI Query Profile Analyzer: Support V2 Profiles
> ----------------------------------------------
>
> Key: IMPALA-15035
> URL: https://issues.apache.org/jira/browse/IMPALA-15035
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Gokul Kolady
> Priority: Major
>
> Currently the Impala AI Query Profile Analyzer is built to ingest v1 query
> profiles, but eventually we will be switching to v2 (aggregated) profiles as
> the default for Impala. Thus, we should support v2 profile structure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
