impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailesh Mukil (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-6144: PublishFilter() continues to run after query failure/cancellation
Date Fri, 03 Nov 2017 20:13:54 GMT
Sailesh Mukil has posted comments on this change. ( )

Change subject: IMPALA-6144: PublishFilter() continues to run after query failure/cancellation

Patch Set 2:

File be/src/runtime/
PS1, Line 394:   {
> same
PS1, Line 394:   {
> Also, should we check if the backend is done too?
File be/src/runtime/
PS1, Line 1082:   TPublishFilterParams rpc_params;
> lock_?
I removed this check since the check in L1106 should be sufficient.
PS1, Line 1106:     if (filter_updates_received_->value() == 0) {
> I think checking for the filter disabled is sufficient in this function, si
Good point. I removed the above check. Plus acquiring the lock above to check the status would
be very expensive.
PS1, Line 1130:     swap(rpc_params.bloom_filter, aggregated_filter);
> I think we should also track the rpc_params memory and prevent the query fr
Sure I opened IMPALA-6153 and linked it to IMPALA-1575.

To view, visit
To unsubscribe, visit

Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I400456ad85adb9c23d2d432d772311fa4dcff2ed
Gerrit-Change-Number: 8455
Gerrit-PatchSet: 2
Gerrit-Owner: Sailesh Mukil <>
Gerrit-Reviewer: Bharath Vissapragada <>
Gerrit-Reviewer: Sailesh Mukil <>
Gerrit-Reviewer: Tim Armstrong <>
Gerrit-Comment-Date: Fri, 03 Nov 2017 20:13:54 +0000
Gerrit-HasComments: Yes

  • Unnamed multipart/alternative (inline, 8-Bit, 0 bytes)
View raw message