Tim Armstrong has posted comments on this change. ( http://gerrit.cloudera.org:8080/10646 )
Change subject: IMPALA-7102: Disable support of erasure coding by default ...................................................................... Patch Set 1: (1 comment) http://gerrit.cloudera.org:8080/#/c/10646/1//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/10646/1//COMMIT_MSG@9 PS1, Line 9: In this patch we add a query option ALLOW_ERASURE_CODED_FILES, that I had a high-level question: what's the rationale for making it a query option as opposed to a startup flag? Reason being that users can toggle query options, so this wouldn't let an admin disable it service wide. This seems fine if the feature is just lacking some polish or performance and it's expected to be stable, but just wanted to understand the rationale. -- To view, visit http://gerrit.cloudera.org:8080/10646 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Icd3b1754541262467a6e67068b0b447882a40fb3 Gerrit-Change-Number: 10646 Gerrit-PatchSet: 1 Gerrit-Owner: Taras Bobrovytsky <[email protected]> Gerrit-Reviewer: Adrian Ng Gerrit-Reviewer: Tianyi Wang <[email protected]> Gerrit-Reviewer: Tim Armstrong <[email protected]> Gerrit-Comment-Date: Tue, 19 Jun 2018 00:02:52 +0000 Gerrit-HasComments: Yes
