From 4dad7edd5aee832a937bb79aa45308b9d80bb24e Mon Sep 17 00:00:00 2001 From: Alex Rodoni Date: Fri, 22 Jun 2018 13:54:31 -0700 Subject: [PATCH] [DOCS] Update to the workaround for IMPALA-3316 Both the date and time strings can be stored and converted to TIMESTAMP Change-Id: If45da5d24dd3bc5f649d95b5bc104047420dbea1 Reviewed-on: http://gerrit.cloudera.org:8080/10800 Reviewed-by: Csaba Ringhofer Tested-by: Impala Public Jenkins --- docs/topics/impala_known_issues.xml | 48 +++++++++++++++-------------- 1 file changed, 25 insertions(+), 23 deletions(-) diff --git a/docs/topics/impala_known_issues.xml b/docs/topics/impala_known_issues.xml index 21a99fe70..59b4606c4 100644 --- a/docs/topics/impala_known_issues.xml +++ b/docs/topics/impala_known_issues.xml @@ -187,10 +187,19 @@ under the License.

- Workaround: If the TIMESTAMP values stored in the table - represent dates only, with no time portion, consider storing them as strings in - yyyy-MM-dd format. Impala implicitly converts such string values to - TIMESTAMP in calls to date/time functions. + Workaround:Store the TIMESTAMP values as + strings in one of the following formats: +

    +
  • yyyy-MM-dd
    • +
  • yyyy-MM-dd HH:mm:ss
    • +
  • yyyy-MM-dd HH:mm:ss.SSSSSSSSS +

    The date can + have the 1-9 digits in the fractional part. +

    +
    • +
+ Impala implicitly converts such string values to + TIMESTAMP in calls to date/time functions.

@@ -349,33 +358,26 @@ under the License.

+ - - + Handling large rows during upgrade to <keyword keyref="impala210_full"/> or higher - - +

After an upgrade to or higher, + users who process very large column values (long strings), or have + increased the --read_size configuration setting from + its default of 8 MB, might encounter capacity errors for some queries + that previously worked.

- After an upgrade to or higher, users who process - very large column values (long strings), or have increased the - --read_size configuration setting from its default of 8 MB, might - encounter capacity errors for some queries that previously worked. -

- + Resolution: After the upgrade, follow the instructions in to check if your queries are affected + by these changes and to modify your configuration settings if so.

- Resolution: After the upgrade, follow the instructions in - to check if your queries are affected by these - changes and to modify your configuration settings if so. + Apache Issue: + IMPALA-6028

- -

- Apache Issue: IMPALA-6028 -

- -