You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by ta...@apache.org on 2018/03/20 20:44:37 UTC
[02/11] impala git commit: [DOCS] Changed to
--use_local_tz_for_unix_timestamp_conversions
[DOCS] Changed to --use_local_tz_for_unix_timestamp_conversions
Change-Id: Id75ec73031b97aa8a3c61ccdbaea39db008b4093
Reviewed-on: http://gerrit.cloudera.org:8080/9620
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
Tested-by: Impala Public Jenkins
Project: http://git-wip-us.apache.org/repos/asf/impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/impala/commit/b62ecb67
Tree: http://git-wip-us.apache.org/repos/asf/impala/tree/b62ecb67
Diff: http://git-wip-us.apache.org/repos/asf/impala/diff/b62ecb67
Branch: refs/heads/master
Commit: b62ecb6795cca22a6641f10d00d097c4957aa5fc
Parents: 0532ff9
Author: Alex Rodoni <ar...@cloudera.com>
Authored: Tue Mar 13 17:47:38 2018 -0700
Committer: Impala Public Jenkins <im...@gerrit.cloudera.org>
Committed: Fri Mar 16 16:36:14 2018 +0000
----------------------------------------------------------------------
docs/shared/impala_common.xml | 10 ++++++----
docs/topics/impala_datetime_functions.xml | 2 +-
docs/topics/impala_timestamp.xml | 8 ++++----
3 files changed, 11 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/impala/blob/b62ecb67/docs/shared/impala_common.xml
----------------------------------------------------------------------
diff --git a/docs/shared/impala_common.xml b/docs/shared/impala_common.xml
index 4a96565..c272e4f 100644
--- a/docs/shared/impala_common.xml
+++ b/docs/shared/impala_common.xml
@@ -1251,7 +1251,7 @@ drop database temp;
<p rev="2.2.0" id="timezone_conversion_caveat">
The way this function deals with time zones when converting to or from <codeph>TIMESTAMP</codeph>
- values is affected by the <codeph>-use_local_tz_for_unix_timestamp_conversions</codeph> startup flag for the
+ values is affected by the <codeph>--use_local_tz_for_unix_timestamp_conversions</codeph> startup flag for the
<cmdname>impalad</cmdname> daemon. See <xref href="../topics/impala_timestamp.xml#timestamp"/> for details about
how Impala handles time zone considerations for the <codeph>TIMESTAMP</codeph> data type.
</p>
@@ -1409,11 +1409,13 @@ drop database temp;
</p>
<p>
- <ph id="cast_int_to_timestamp">Casting an integer or floating-point value <codeph>N</codeph> to
+ <ph id="cast_int_to_timestamp">
+ Casting an integer or floating-point value <codeph>N</codeph> to
<codeph>TIMESTAMP</codeph> produces a value that is <codeph>N</codeph> seconds past the start of the epoch
date (January 1, 1970). By default, the result value represents a date and time in the UTC time zone.
- If the setting <codeph>-use_local_tz_for_unix_timestamp_conversions=true</codeph> is in effect,
- the resulting <codeph>TIMESTAMP</codeph> represents a date and time in the local time zone.</ph>
+ If the setting <codeph>--use_local_tz_for_unix_timestamp_conversions=true</codeph> is in effect,
+ the resulting <codeph>TIMESTAMP</codeph> represents a date and time in the local time zone.
+ </ph>
</p>
<p id="redaction_yes" rev="2.2.0">
http://git-wip-us.apache.org/repos/asf/impala/blob/b62ecb67/docs/topics/impala_datetime_functions.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_datetime_functions.xml b/docs/topics/impala_datetime_functions.xml
index d9c77dc..d40e28b 100644
--- a/docs/topics/impala_datetime_functions.xml
+++ b/docs/topics/impala_datetime_functions.xml
@@ -52,7 +52,7 @@ under the License.
<p rev="2.2.0">
Some of these functions are affected by the setting of the
- <codeph>-use_local_tz_for_unix_timestamp_conversions</codeph> startup flag for the
+ <codeph>--use_local_tz_for_unix_timestamp_conversions</codeph> startup flag for the
<cmdname>impalad</cmdname> daemon. This setting is off by default, meaning that
functions such as <codeph>from_unixtime()</codeph> and <codeph>unix_timestamp()</codeph>
consider the input values to always represent the UTC time zone.
http://git-wip-us.apache.org/repos/asf/impala/blob/b62ecb67/docs/topics/impala_timestamp.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_timestamp.xml b/docs/topics/impala_timestamp.xml
index 94e9c69..320f99d 100644
--- a/docs/topics/impala_timestamp.xml
+++ b/docs/topics/impala_timestamp.xml
@@ -163,21 +163,21 @@ insert into auction_details
If you have data files written by Hive, those <codeph>TIMESTAMP</codeph> values represent the local timezone
of the host where the data was written, potentially leading to inconsistent results when processed by Impala.
To avoid compatibility problems or having to code workarounds, you can specify one or both of these
- <cmdname>impalad</cmdname> startup flags: <codeph>-use_local_tz_for_unix_timestamp_conversions=true</codeph>
+ <cmdname>impalad</cmdname> startup flags: <codeph>--use_local_tz_for_unix_timestamp_conversions=true</codeph>
<codeph>-convert_legacy_hive_parquet_utc_timestamps=true</codeph>. Although
<codeph>-convert_legacy_hive_parquet_utc_timestamps</codeph> is turned off by default to avoid performance overhead, where practical
turn it on when processing <codeph>TIMESTAMP</codeph> columns in Parquet files written by Hive, to avoid unexpected behavior.
</p>
<p rev="2.2.0">
- The <codeph>-use_local_tz_for_unix_timestamp_conversions</codeph> setting affects conversions from
+ The <codeph>--use_local_tz_for_unix_timestamp_conversions</codeph> setting affects conversions from
<codeph>TIMESTAMP</codeph> to <codeph>BIGINT</codeph>, or from <codeph>BIGINT</codeph>
to <codeph>TIMESTAMP</codeph>. By default, Impala treats all <codeph>TIMESTAMP</codeph> values as UTC,
to simplify analysis of time-series data from different geographic regions. When you enable the
- <codeph>-use_local_tz_for_unix_timestamp_conversions</codeph> setting, these operations
+ <codeph>--use_local_tz_for_unix_timestamp_conversions</codeph> setting, these operations
treat the input values as if they are in the local tie zone of the host doing the processing.
See <xref href="impala_datetime_functions.xml#datetime_functions"/> for the list of functions
- affected by the <codeph>-use_local_tz_for_unix_timestamp_conversions</codeph> setting.
+ affected by the <codeph>--use_local_tz_for_unix_timestamp_conversions</codeph> setting.
</p>
<p>