impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharath Vissapragada (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-5881: Use native allocation while building catalog updates
Date Thu, 07 Sep 2017 01:58:34 GMT
Bharath Vissapragada has posted comments on this change.

Change subject: IMPALA-5881: Use native allocation while building catalog updates

Patch Set 6:


Fixed the tests. Figured out that the problem was with thrift doing an initial copy using
getBytes() which causes problems. Worked around it by splitting the test struct into 8 strings
(instead of 2). Now I can repro all scenarios in unit tests.
File be/src/catalog/

PS1, Line 106: TNativeByteBuffer nbuffer;
> I'm not really sure what error scenario you are worried about. We allocate 
makes sense. Done.
File fe/src/main/java/org/apache/impala/service/

Line 153:       LOG.warn("Detected a potentially large catalog update. Serialized size: "
> I'm not opposed to adding warnings, just concerned that users will worry ab
Hmm, my thinking was that we can use this for postmortem  in case of crashes. Let me know
your thoughts. I'm fine either way.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I383684effa9524734ce3c6c0fb7ed37de0e15782
Gerrit-PatchSet: 6
Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-Owner: Bharath Vissapragada <>
Gerrit-Reviewer: Alex Behm <>
Gerrit-Reviewer: Bharath Vissapragada <>
Gerrit-Reviewer: Dimitris Tsirogiannis <>
Gerrit-Reviewer: Mostafa Mokhtar <>
Gerrit-Reviewer: Tim Armstrong <>
Gerrit-HasComments: Yes

View raw message