Impala Public Jenkins has submitted this change and it was merged. Change subject: IMPALA-5595: Only set KuduScanner timestamp feature flag if necessary ......................................................................
IMPALA-5595: Only set KuduScanner timestamp feature flag if necessary To support Kudu timestamps, Impala sets a KuduScanner flag which pads the result tuples: KuduScanner::PAD_UNIXTIME_MICROS_TO_16_BYTES It is always set, which is correct, but means that newer versions of Impala cannot scan older Kudus even if there are no TIMESTAMP columns. Even though Impala provides no guarantees about supporting older versions of Kudu (i.e. there is no testing), the flag should just be set when there are TIMESTAMP columns since this is a known incompatibility that is easy to work around for users who are still willing to use unsupported setups. Testing: This works against the current version of Kudu (the only supported configuration). Change-Id: If5a83d2a6db97812295e6e8d37c274fe1f1dc3fb Reviewed-on: http://gerrit.cloudera.org:8080/7321 Reviewed-by: Matthew Jacobs <[email protected]> Tested-by: Impala Public Jenkins --- M be/src/exec/kudu-scanner.cc 1 file changed, 6 insertions(+), 2 deletions(-) Approvals: Impala Public Jenkins: Verified Matthew Jacobs: Looks good to me, approved -- To view, visit http://gerrit.cloudera.org:8080/7321 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: merged Gerrit-Change-Id: If5a83d2a6db97812295e6e8d37c274fe1f1dc3fb Gerrit-PatchSet: 3 Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-Owner: Matthew Jacobs <[email protected]> Gerrit-Reviewer: Dan Hecht <[email protected]> Gerrit-Reviewer: Impala Public Jenkins Gerrit-Reviewer: Matthew Jacobs <[email protected]>
