[ https://issues.apache.org/jira/browse/IMPALA-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-13111. ------------------------------------ Fix Version/s: Impala 4.5.0 Resolution: Fixed > impala-gdb.py's find-query-ids/find-fragment-instances return unusable query > ids > -------------------------------------------------------------------------------- > > Key: IMPALA-13111 > URL: https://issues.apache.org/jira/browse/IMPALA-13111 > Project: IMPALA > Issue Type: Bug > Components: Infrastructure > Affects Versions: Impala 4.5.0 > Reporter: Joe McDonnell > Assignee: Joe McDonnell > Priority: Major > Fix For: Impala 4.5.0 > > > The gdb helpers in lib/python/impala_py_lib/gdb/impala-gdb.py provide > information about the queries / fragments running in a core file. However, > the query/fragment ids that it returns have issues with the signedness of the > integers: > {noformat} > (gdb) find-fragment-instances > Fragment Instance Id Thread IDs > -23b76c1699a831a1:2793586800000036 [117120] > -23b76c1699a831a1:2793586800000037 [117121] > -23b76c1699a831a1:2793586800000038 [117122] > .. > (gdb) find-query-ids > -3cbda1606b3ade7c:f170c4bd00000000 > -23b76c1699a831a1:2793586800000000 > 68435df1364aa90f:1752944f00000000 > 3442ed6354c7355d:78c83d2000000000{noformat} > The low values for find-query-ids don't have this problem, because it is > ANDed with 0xFFFFFFFFFFFF0000: > {noformat} > qid_low = format(int(qid_low, 16) & 0xFFFFFFFFFFFF0000, > 'x'){noformat} > We can fix the other locations by ANDing with 0xFFFFFFFFFFFFFFFF. -- This message was sent by Atlassian Jira (v8.20.10#820010)