Repository: incubator-impala Updated Branches: refs/heads/doc_prototype 152018d17 -> 8039fbb3b
Updating Impala SQL Ref files with Laurel's changes for a clean build. New files added by Laurel for clean build. (cherry picked from commit d9fcd28a3085b46912d0bb2c1be0db08d9b55b3a) Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/8039fbb3 Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/8039fbb3 Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/8039fbb3 Branch: refs/heads/doc_prototype Commit: 8039fbb3b951d2cc518ced9483b0fb3be39a1fbf Parents: 152018d Author: John Russell <[email protected]> Authored: Fri Oct 28 14:55:04 2016 -0700 Committer: John Russell <[email protected]> Committed: Fri Oct 28 15:28:38 2016 -0700 ---------------------------------------------------------------------- docs/images/impala_arch.jpeg | Bin 0 -> 41900 bytes docs/shared/ImpalaVariables.xml | 20 +- docs/topics/cdh_ig_parquet.xml | 20 ++ docs/topics/impala_admission.xml | 24 ++ docs/topics/impala_analytic_functions.xml | 6 +- docs/topics/impala_array.xml | 2 +- docs/topics/impala_authorization.xml | 23 ++ docs/topics/impala_avro.xml | 23 ++ docs/topics/impala_char.xml | 4 +- docs/topics/impala_complex_types.xml | 2 +- docs/topics/impala_components.xml | 19 ++ docs/topics/impala_create_role.xml | 4 +- docs/topics/impala_decimal.xml | 4 +- docs/topics/impala_delete.xml | 2 +- docs/topics/impala_disk_space.xml | 19 ++ docs/topics/impala_drop_role.xml | 4 +- docs/topics/impala_explain_plan.xml | 20 ++ docs/topics/impala_file_formats.xml | 36 +++ docs/topics/impala_grant.xml | 8 +- docs/topics/impala_hadoop.xml | 20 ++ docs/topics/impala_hbase.xml | 23 ++ docs/topics/impala_impala_shell.xml | 20 ++ docs/topics/impala_incompatible_changes.xml | 19 ++ docs/topics/impala_install.xml | 19 ++ docs/topics/impala_isilon.xml | 23 ++ docs/topics/impala_jdbc.xml | 21 ++ docs/topics/impala_kudu.xml | 24 ++ docs/topics/impala_logging.xml | 21 ++ docs/topics/impala_map.xml | 2 +- docs/topics/impala_new_features.xml | 21 ++ docs/topics/impala_odbc.xml | 24 ++ docs/topics/impala_parquet.xml | 29 ++ docs/topics/impala_partitioning.xml | 26 ++ docs/topics/impala_perf_hdfs_caching.xml | 22 ++ docs/topics/impala_perf_joins.xml | 22 ++ docs/topics/impala_perf_stats.xml | 22 ++ docs/topics/impala_performance.xml | 20 ++ docs/topics/impala_prereqs.xml | 22 ++ docs/topics/impala_processes.xml | 18 ++ docs/topics/impala_reserved_words.xml | 365 +++++++++++++++++++++++ docs/topics/impala_resource_management.xml | 20 ++ docs/topics/impala_revoke.xml | 8 +- docs/topics/impala_s3.xml | 27 ++ docs/topics/impala_scalability.xml | 21 ++ docs/topics/impala_security.xml | 21 ++ docs/topics/impala_shell_options.xml | 20 ++ docs/topics/impala_struct.xml | 2 +- docs/topics/impala_tables.xml | 2 +- docs/topics/impala_timeouts.xml | 21 ++ docs/topics/impala_truncate_table.xml | 2 +- docs/topics/impala_tutorial.xml | 19 ++ docs/topics/impala_txtfile.xml | 24 ++ docs/topics/impala_update.xml | 2 +- docs/topics/impala_upgrading.xml | 18 ++ docs/topics/impala_varchar.xml | 4 +- docs/topics/impala_views.xml | 4 +- docs/topics/sg_hive_sql.xml | 27 ++ docs/topics/sg_redaction.xml | 22 ++ 58 files changed, 1246 insertions(+), 41 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/images/impala_arch.jpeg ---------------------------------------------------------------------- diff --git a/docs/images/impala_arch.jpeg b/docs/images/impala_arch.jpeg new file mode 100644 index 0000000..8289469 Binary files /dev/null and b/docs/images/impala_arch.jpeg differ http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/shared/ImpalaVariables.xml ---------------------------------------------------------------------- diff --git a/docs/shared/ImpalaVariables.xml b/docs/shared/ImpalaVariables.xml index 60f8143..226eee9 100644 --- a/docs/shared/ImpalaVariables.xml +++ b/docs/shared/ImpalaVariables.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="impala_vars"> +<concept xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"; id="impala_vars" ditaarch:DITAArchVersion="1.2" domains="(topic concept) (topic hi-d) (topic ut-d) (topic indexing-d) (topic hazard-d) (topic abbrev-d) (topic pr-d) (topic sw-d) (topic ui-d) " xml:lang="en-US"> <title>Cloudera Impala Variables</title> <prolog id="prolog_slg_nmv_km"> <metadata id="metadata_ecq_qmv_km"> @@ -20,15 +20,15 @@ The docs included with a distro can refer to the distro release number by editing the values here. <ul> - <li><!-- Formerly: CDH 5.8 --><ph id="impala26">Impala 2.6</ph></li> - <li><!-- Formerly: CDH 5.7 --><ph id="impala25">Impala 2.5</ph></li> - <li><!-- Formerly: CDH 5.6 --><ph id="impala24">Impala 2.4</ph></li> - <li><!-- Formerly: CDH 5.5 --><ph id="impala23">Impala 2.3</ph></li> - <li><!-- Formerly: CDH 5.4 --><ph id="impala22">Impala 2.2</ph></li> - <li><!-- Formerly: CDH 5.3 --><ph id="impala21">Impala 2.1</ph></li> - <li><!-- Formerly: CDH 5.2 --><ph id="impala20">Impala 2.0</ph></li> - <li><!-- Formerly: CDH 5.1 --><ph id="impala14">Impala 1.4</ph></li> - <li><!-- Formerly: CDH 5.0 --><ph id="impala13">Impala 1.3</ph></li> + <li><ph id="impala26">CDH 5.8</ph></li> + <li><ph id="impala25">CDH 5.7</ph></li> + <li><ph id="impala24">CDH 5.6</ph></li> + <li><ph id="impala23">CDH 5.5</ph></li> + <li><ph id="impala22">CDH 5.4</ph></li> + <li><ph id="impala21">CDH 5.3</ph></li> + <li><ph id="impala20">CDH 5.2</ph></li> + <li><ph id="impala14">CDH 5.1</ph></li> + <li><ph id="impala13">CDH 5.0</ph></li> </ul> </p> <p>Banner for examples showing shell version - <ph id="ShellBanner">(Shell http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/cdh_ig_parquet.xml ---------------------------------------------------------------------- diff --git a/docs/topics/cdh_ig_parquet.xml b/docs/topics/cdh_ig_parquet.xml new file mode 100644 index 0000000..2eba8b3 --- /dev/null +++ b/docs/topics/cdh_ig_parquet.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"; id="parquet_format" xml:lang="en-US" ditaarch:DITAArchVersion="1.2" domains="(topic concept) (topic hi-d) (topic ut-d) (topic indexing-d) (topic hazard-d) (topic abbrev-d) (topic pr-d) (topic sw-d) (topic ui-d) "> + <title>Parquet Files</title> + + + <conbody> + + <p><xref href="https://parquet.apache.org/"; format="html" scope="external" + >Apache Parquet</xref> is a <xref + href="http://en.wikipedia.org/wiki/Column-oriented_DBMS"; format="html" + scope="external">columnar storage</xref> format available to any + component in the Hadoop ecosystem, regardless of the data processing + framework, data model, or programming language. The Parquet file format + incorporates several features that support data warehouse-style + operations:</p> + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_admission.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_admission.xml b/docs/topics/impala_admission.xml new file mode 100644 index 0000000..0921546 --- /dev/null +++ b/docs/topics/impala_admission.xml @@ -0,0 +1,24 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="1.3.0" id="admission_control"> + + <title>Admission Control and Query Queuing</title> + + + <conbody> + + <p id="admission_control_intro"> + Admission control is an Impala feature that imposes limits on concurrent SQL queries, to avoid resource usage + spikes and out-of-memory conditions on busy CDH clusters. + It is a form of <q>throttling</q>. + New queries are accepted and executed until + certain conditions are met, such as too many queries or too much + total memory used across the cluster. + When one of these thresholds is reached, + incoming queries wait to begin execution. These queries are + queued and are admitted (that is, begin executing) when the resources become available. + </p> + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_analytic_functions.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_analytic_functions.xml b/docs/topics/impala_analytic_functions.xml index 35a6de2..293a512 100644 --- a/docs/topics/impala_analytic_functions.xml +++ b/docs/topics/impala_analytic_functions.xml @@ -477,7 +477,7 @@ output as above. Because <codeph>RANGE</codeph> currently does not support numer <concept rev="2.3.0" id="cume_dist"> - <title>CUME_DIST() Function (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> or higher only)</title> + <title>CUME_DIST() Function (CDH 5.5 or higher only)</title> <conbody> @@ -1213,7 +1213,7 @@ from stock_ticker <concept rev="2.3.0" id="ntile"> - <title>NTILE() Function (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> or higher only)</title> + <title>NTILE() Function (CDH 5.5 or higher only)</title> <conbody> @@ -1348,7 +1348,7 @@ order by kilos desc; <concept rev="2.3.0" id="percent_rank"> - <title>PERCENT_RANK() Function (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> or higher only)</title> + <title>PERCENT_RANK() Function (CDH 5.5 or higher only)</title> <conbody> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_array.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_array.xml b/docs/topics/impala_array.xml index 06d261f..1e60795 100644 --- a/docs/topics/impala_array.xml +++ b/docs/topics/impala_array.xml @@ -2,7 +2,7 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept id="array"> - <title>ARRAY Complex Type (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> or higher only)</title> + <title>ARRAY Complex Type (CDH 5.5 or higher only)</title> <prolog> <metadata> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_authorization.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_authorization.xml b/docs/topics/impala_authorization.xml new file mode 100644 index 0000000..12cdb98 --- /dev/null +++ b/docs/topics/impala_authorization.xml @@ -0,0 +1,23 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="1.1" id="authorization"> + + <title>Enabling Sentry Authorization for Impala</title> + + + <conbody id="sentry"> + + <p> + Authorization determines which users are allowed to access which resources, and what operations they are + allowed to perform. In Impala 1.1 and higher, you use the Sentry open source project for authorization. + Sentry adds a fine-grained authorization framework for Hadoop. By default (when authorization is not + enabled), Impala does all read and write operations with the privileges of the <codeph>impala</codeph> user, + which is suitable for a development/test environment but not for a secure production environment. When + authorization is enabled, Impala uses the OS user ID of the user who runs <cmdname>impala-shell</cmdname> or + other client program, and associates various privileges with each user. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_avro.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_avro.xml b/docs/topics/impala_avro.xml new file mode 100644 index 0000000..ae19192 --- /dev/null +++ b/docs/topics/impala_avro.xml @@ -0,0 +1,23 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="avro"> + + <title>Using the Avro File Format with Impala Tables</title> + <titlealts audience="PDF"><navtitle>Avro Data Files</navtitle></titlealts> + + + <conbody> + + <p rev="1.4.0"> + <indexterm audience="Cloudera">Avro support in Impala</indexterm> + Impala supports using tables whose data files use the Avro file format. Impala can query Avro + tables, and in Impala 1.4.0 and higher can create them, but currently cannot insert data into them. For + insert operations, use Hive, then switch back to Impala to run queries. + </p> + + + + </conbody> + </concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_char.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_char.xml b/docs/topics/impala_char.xml index c176525..68cabeb 100644 --- a/docs/topics/impala_char.xml +++ b/docs/topics/impala_char.xml @@ -2,8 +2,8 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept id="char" rev="2.0.0"> - <title>CHAR Data Type (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala20"/> or higher only)</title> - <titlealts><navtitle>CHAR</navtitle></titlealts> + <title>CHAR Data Type (CDH 5.2 or higher only)</title> + <titlealts><navtitle>CHAR (CDH 5.2 or higher only)</navtitle></titlealts> <prolog> <metadata> <data name="Category" value="Impala"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_complex_types.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_complex_types.xml b/docs/topics/impala_complex_types.xml index a6708ec..9fe7362 100644 --- a/docs/topics/impala_complex_types.xml +++ b/docs/topics/impala_complex_types.xml @@ -2,7 +2,7 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept rev="2.3.0" id="complex_types"> - <title id="nested_types">Complex Types (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> and higher only)</title> + <title id="nested_types">Complex Types (CDH 5.5 and higher only)</title> <prolog> <metadata> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_components.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_components.xml b/docs/topics/impala_components.xml new file mode 100644 index 0000000..bf09ab0 --- /dev/null +++ b/docs/topics/impala_components.xml @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="intro_components"> + + <title>Components of the Impala Server</title> + <titlealts audience="PDF"><navtitle>Components</navtitle></titlealts> + + + <conbody> + + <p> + The Impala server is a distributed, massively parallel processing (MPP) database engine. It consists of + different daemon processes that run on specific hosts within your CDH cluster. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_create_role.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_create_role.xml b/docs/topics/impala_create_role.xml index 0c42f07..975ce15 100644 --- a/docs/topics/impala_create_role.xml +++ b/docs/topics/impala_create_role.xml @@ -2,8 +2,8 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept rev="1.4.0" id="create_role"> - <title>CREATE ROLE Statement (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala20"/> or higher only)</title> - <titlealts><navtitle>CREATE ROLE</navtitle></titlealts> + <title>CREATE ROLE Statement (CDH 5.2 or higher only)</title> + <titlealts><navtitle>CREATE ROLE (CDH 5.2 or higher only)</navtitle></titlealts> <prolog> <metadata> <data name="Category" value="Impala"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_decimal.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_decimal.xml b/docs/topics/impala_decimal.xml index 49097b1..c0c98d9 100644 --- a/docs/topics/impala_decimal.xml +++ b/docs/topics/impala_decimal.xml @@ -2,8 +2,8 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept rev="1.4.0" id="decimal"> - <title>DECIMAL Data Type (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala14"/> or higher only)</title> - <titlealts><navtitle>DECIMAL</navtitle></titlealts> + <title>DECIMAL Data Type (CDH 5.1 or higher only)</title> + <titlealts><navtitle>DECIMAL (CDH 5.1 or higher only)</navtitle></titlealts> <prolog> <metadata> <data name="Category" value="Impala"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_delete.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_delete.xml b/docs/topics/impala_delete.xml index 7f08a08..fcac5e4 100644 --- a/docs/topics/impala_delete.xml +++ b/docs/topics/impala_delete.xml @@ -2,7 +2,7 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept id="delete"> - <title>DELETE Statement (CDH ?? and higher only)</title> + <title>DELETE Statement (CDH 5.5 and higher only)</title> <titlealts><navtitle>DELETE</navtitle></titlealts> <prolog> <metadata> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_disk_space.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_disk_space.xml b/docs/topics/impala_disk_space.xml new file mode 100644 index 0000000..8bc3ca8 --- /dev/null +++ b/docs/topics/impala_disk_space.xml @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="disk_space"> + + <title>Managing Disk Space for Impala Data</title> + <titlealts audience="PDF"><navtitle>Managing Disk Space</navtitle></titlealts> + + + <conbody> + + <p> + Although Impala typically works with many large files in an HDFS storage system with plenty of capacity, + there are times when you might perform some file cleanup to reclaim space, or advise developers on techniques + to minimize space consumption and file duplication. + </p> + + + </conbody> +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_drop_role.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_role.xml b/docs/topics/impala_drop_role.xml index 5e514f4..35d2157 100644 --- a/docs/topics/impala_drop_role.xml +++ b/docs/topics/impala_drop_role.xml @@ -2,8 +2,8 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept rev="1.4.0" id="drop_role"> - <title>DROP ROLE Statement (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala20"/> or higher only)</title> - <titlealts><navtitle>DROP ROLE</navtitle></titlealts> + <title>DROP ROLE Statement (CDH 5.2 or higher only)</title> + <titlealts><navtitle>DROP ROLE (CDH 5.2 or higher only)</navtitle></titlealts> <prolog> <metadata> <data name="Category" value="Impala"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_explain_plan.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_explain_plan.xml b/docs/topics/impala_explain_plan.xml new file mode 100644 index 0000000..44c8b74 --- /dev/null +++ b/docs/topics/impala_explain_plan.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="explain_plan"> + + <title>Understanding Impala Query Performance - EXPLAIN Plans and Query Profiles</title> + <titlealts audience="PDF"><navtitle>EXPLAIN Plans and Query Profiles</navtitle></titlealts> + + + <conbody> + + <p> + To understand the high-level performance considerations for Impala queries, read the output of the + <codeph>EXPLAIN</codeph> statement for the query. You can get the <codeph>EXPLAIN</codeph> plan without + actually running the query itself. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_file_formats.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_file_formats.xml b/docs/topics/impala_file_formats.xml new file mode 100644 index 0000000..64bf8a5 --- /dev/null +++ b/docs/topics/impala_file_formats.xml @@ -0,0 +1,36 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="file_formats"> + + <title>How Impala Works with Hadoop File Formats</title> + <titlealts audience="PDF"><navtitle>File Formats</navtitle></titlealts> + <prolog> + <metadata> + <data name="Category" value="Impala"/> + <data name="Category" value="Concepts"/> + <data name="Category" value="Hadoop"/> + <data name="Category" value="File Formats"/> + <data name="Category" value="Developers"/> + <data name="Category" value="Data Analysts"/> + <!-- Like Impala Administration, this page has a fair bit of info already, but it could benefit from wiki-style embedded of intro text from those other pages. --> + <!-- In this case, that would also enable a good in-page TOC since there is already one lonely subtopic on this same page. --> + <data name="Category" value="Stub Pages"/> + </metadata> + </prolog> + + <conbody> + + <p> + <indexterm audience="Cloudera">file formats</indexterm> + <indexterm audience="Cloudera">compression</indexterm> + Impala supports several familiar file formats used in Apache Hadoop. Impala can load and query data files + produced by other Hadoop components such as Pig or MapReduce, and data files produced by Impala can be used + by other components also. The following sections discuss the procedures, limitations, and performance + considerations for using each file format with Impala. + </p> + + + </conbody> + + +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_grant.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_grant.xml b/docs/topics/impala_grant.xml index 9598668..ddbd39c 100644 --- a/docs/topics/impala_grant.xml +++ b/docs/topics/impala_grant.xml @@ -2,8 +2,8 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept rev="2.0.0" id="grant"> - <title>GRANT Statement (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala20"/> or higher only)</title> - <titlealts><navtitle>GRANT</navtitle></titlealts> + <title>GRANT Statement (CDH 5.2 or higher only)</title> + <titlealts><navtitle>GRANT (CDH 5.2 or higher only)</navtitle></titlealts> <prolog> <metadata> <data name="Category" value="Impala"/> @@ -69,8 +69,8 @@ object_type ::= TABLE | DATABASE | SERVER | URI <p rev="2.3.0 collevelauth"> The ability to grant or revoke <codeph>SELECT</codeph> privilege on specific columns is available - in CDH 5.5 / Impala 2.3 and higher. See <xref href="sg_hive_sql.xml#concept_c2q_4qx_p4/col_level_auth_sentry"/> - for details. + in CDH 5.5 / Impala 2.3 and higher. <!--See <xref href="sg_hive_sql.xml#concept_c2q_4qx_p4/col_level_auth_sentry"/> + for details.--> </p> <!-- Turn compatibility info into a conref or series of conrefs. (In both GRANT and REVOKE.) --> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_hadoop.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_hadoop.xml b/docs/topics/impala_hadoop.xml new file mode 100644 index 0000000..a3700c6 --- /dev/null +++ b/docs/topics/impala_hadoop.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="intro_hadoop"> + + <title>How Impala Fits Into the Hadoop Ecosystem</title> + <titlealts audience="PDF"><navtitle>Role in the Hadoop Ecosystem</navtitle></titlealts> + + + <conbody> + + <p> + Impala makes use of many familiar components within the Hadoop ecosystem. Impala can interchange data with + other Hadoop components, as both a consumer and a producer, so it can fit in flexible ways into your ETL and + ELT pipelines. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_hbase.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_hbase.xml b/docs/topics/impala_hbase.xml new file mode 100644 index 0000000..d8880d3 --- /dev/null +++ b/docs/topics/impala_hbase.xml @@ -0,0 +1,23 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="impala_hbase"> + + <title id="hbase">Using Impala to Query HBase Tables</title> + <titlealts audience="PDF"><navtitle>HBase Tables</navtitle></titlealts> + + + <conbody> + + <p> + <indexterm audience="Cloudera">HBase</indexterm> + You can use Impala to query HBase tables. This capability allows convenient access to a storage system that + is tuned for different kinds of workloads than the default with Impala. The default Impala tables use data + files stored on HDFS, which are ideal for bulk loads and queries using full-table scans. In contrast, HBase + can do efficient queries for data organized for OLTP-style workloads, with lookups of individual rows or + ranges of values. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_impala_shell.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_impala_shell.xml b/docs/topics/impala_impala_shell.xml new file mode 100644 index 0000000..3010fff --- /dev/null +++ b/docs/topics/impala_impala_shell.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="impala_shell"> + + <title>Using the Impala Shell (impala-shell Command)</title> + <titlealts audience="PDF"><navtitle>The Impala Shell</navtitle></titlealts> + + <conbody> + + <p> + + You can use the Impala shell tool (<codeph>impala-shell</codeph>) to set up databases and tables, insert + data, and issue queries. For ad hoc queries and exploration, you can submit SQL statements in an interactive + session. To automate your work, you can specify command-line options to process a single statement or a + script file. + </p> + + + </conbody> +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_incompatible_changes.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_incompatible_changes.xml b/docs/topics/impala_incompatible_changes.xml new file mode 100644 index 0000000..1814553 --- /dev/null +++ b/docs/topics/impala_incompatible_changes.xml @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="ver" id="incompatible_changes"> + + <title><ph audience="standalone">Incompatible Changes and Limitations in Apache Impala (incubating)</ph><ph audience="integrated">Apache Impala (incubating) Incompatible Changes and Limitations</ph></title> + + + <conbody> + + <p> + The Impala version covered by this documentation library contains the following incompatible changes. These + are things such as file format changes, removed features, or changes to implementation, default + configuration, dependencies, or prerequisites that could cause issues during or after an Impala upgrade. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_install.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_install.xml b/docs/topics/impala_install.xml new file mode 100644 index 0000000..aab0a63 --- /dev/null +++ b/docs/topics/impala_install.xml @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="install"> + + <title><ph audience="standalone">Installing Impala</ph><ph audience="integrated">Impala Installation</ph></title> + + + <conbody> + + <p> + + Impala is an open-source add-on to the Cloudera Enterprise Core that returns rapid responses to + queries. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_isilon.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_isilon.xml b/docs/topics/impala_isilon.xml new file mode 100644 index 0000000..fe6a5de --- /dev/null +++ b/docs/topics/impala_isilon.xml @@ -0,0 +1,23 @@ +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="5.4.3" id="impala_isilon"> + + <title>Using Impala with Isilon Storage</title> + <titlealts audience="PDF"><navtitle>Isilon Storage</navtitle></titlealts> + + + + <conbody> + + <p> + <indexterm audience="Cloudera">Isilon</indexterm> + You can use Impala to query data files that reside on EMC Isilon storage devices, rather than in HDFS. + This capability allows convenient query access to a storage system where you might already be + managing large volumes of data. The combination of the Impala query engine and Isilon storage is + certified on CDH 5.4.4 or higher. + </p> + + +</conbody> +</concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_jdbc.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_jdbc.xml b/docs/topics/impala_jdbc.xml new file mode 100644 index 0000000..8a7a955 --- /dev/null +++ b/docs/topics/impala_jdbc.xml @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="impala_jdbc"> + + <title id="jdbc">Configuring Impala to Work with JDBC</title> + + + <conbody> + + <p> + <indexterm audience="Cloudera">JDBC</indexterm> + Impala supports the standard JDBC interface, allowing access from commercial Business Intelligence tools and + custom software written in Java or other programming languages. The JDBC driver allows you to access Impala + from a Java program that you write, or a Business Intelligence or similar tool that uses JDBC to communicate + with various database products. + </p> + + + </conbody> + </concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_kudu.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_kudu.xml b/docs/topics/impala_kudu.xml new file mode 100644 index 0000000..5b8e87c --- /dev/null +++ b/docs/topics/impala_kudu.xml @@ -0,0 +1,24 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="impala_kudu" rev="kudu"> + + <title>Using Impala to Query Kudu Tables</title> + + + <conbody> + + <p> + <indexterm audience="Cloudera">Kudu</indexterm> + You can use Impala to query Kudu tables. This capability allows convenient access to a storage system that is + tuned for different kinds of workloads than the default with Impala. The default Impala tables use data files + stored on HDFS, which are ideal for bulk loads and queries using full-table scans. In contrast, Kudu can do + efficient queries for data organized either in data warehouse style (with full table scans) or for OLTP-style + workloads (with key-based lookups for single rows or small ranges of values). + </p> + + + </conbody> + + </concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_logging.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_logging.xml b/docs/topics/impala_logging.xml new file mode 100644 index 0000000..9430178 --- /dev/null +++ b/docs/topics/impala_logging.xml @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="logging"> + + <title>Using Impala Logging</title> + <titlealts audience="PDF"><navtitle>Logging</navtitle></titlealts> + + + <conbody> + + <p> + The Impala logs record information about: + </p> + + + + </conbody> + + </concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_map.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_map.xml b/docs/topics/impala_map.xml index 34a3ada..41e4754 100644 --- a/docs/topics/impala_map.xml +++ b/docs/topics/impala_map.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept id="map"> - <title>MAP Complex Type (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> or higher only)</title> + <title>MAP Complex Type (CDH 5.5 or higher only)</title> <prolog> <metadata> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_new_features.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_new_features.xml b/docs/topics/impala_new_features.xml new file mode 100644 index 0000000..ad65782 --- /dev/null +++ b/docs/topics/impala_new_features.xml @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="ver" id="new_features"> + + <title><ph audience="standalone">New Features in Apache Impala (incubating)</ph><ph audience="integrated">What's New in Apache Impala (incubating)</ph></title> + + + + <conbody> + + <p> + This release of Impala contains the following changes and enhancements from previous releases. + </p> + + + + </conbody> + + </concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_odbc.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_odbc.xml b/docs/topics/impala_odbc.xml new file mode 100644 index 0000000..f899f8f --- /dev/null +++ b/docs/topics/impala_odbc.xml @@ -0,0 +1,24 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="impala_odbc"> + + <title id="odbc">Configuring Impala to Work with ODBC</title> + + + <conbody> + + <p> + <indexterm audience="Cloudera">ODBC</indexterm> + Third-party products can be designed to integrate with Impala using ODBC. For the best experience, ensure any + third-party product you intend to use is supported. Verifying support includes checking that the versions of + Impala, ODBC, the operating system, and the third-party product have all been approved for use together. + Before configuring your systems to use ODBC, download a connector. + You may need to sign in and accept license agreements before accessing the pages required for downloading + ODBC connectors. + </p> + + + </conbody> + </concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_parquet.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_parquet.xml b/docs/topics/impala_parquet.xml new file mode 100644 index 0000000..d068bea --- /dev/null +++ b/docs/topics/impala_parquet.xml @@ -0,0 +1,29 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="parquet"> + + <title>Using the Parquet File Format with Impala Tables</title> + <titlealts audience="PDF"><navtitle>Parquet Data Files</navtitle></titlealts> + + + <conbody> + + <p> + <indexterm audience="Cloudera">Parquet support in Impala</indexterm> + Impala helps you to create, manage, and query Parquet tables. Parquet is a column-oriented binary file format + intended to be highly efficient for the types of large-scale queries that Impala is best at. Parquet is + especially good for queries scanning particular columns within a table, for example to query <q>wide</q> + tables with many columns, or to perform aggregation operations such as <codeph>SUM()</codeph> and + <codeph>AVG()</codeph> that need to process most or all of the values from a column. Each data file contains + the values for a set of rows (the <q>row group</q>). Within a data file, the values from each column are + organized so that they are all adjacent, enabling good compression for the values from that column. Queries + against a Parquet table can retrieve and analyze these values from any column quickly and with minimal I/O. + </p> + + + + </conbody> + + + +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_partitioning.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_partitioning.xml b/docs/topics/impala_partitioning.xml new file mode 100644 index 0000000..46b1568 --- /dev/null +++ b/docs/topics/impala_partitioning.xml @@ -0,0 +1,26 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="partitioning"> + + <title>Partitioning for Impala Tables</title> + <titlealts audience="PDF"><navtitle>Partitioning</navtitle></titlealts> + + <conbody> + + <p> + <indexterm audience="Cloudera">partitioning</indexterm> + By default, all the data files for a table are located in a single directory. Partitioning is a technique for + physically dividing the data during loading, based on values from one or more columns, to speed up queries + that test those columns. For example, with a <codeph>school_records</codeph> table partitioned on a + <codeph>year</codeph> column, there is a separate data directory for each different year value, and all the + data for that year is stored in a data file in that directory. A query that includes a <codeph>WHERE</codeph> + condition such as <codeph>YEAR=1966</codeph>, <codeph>YEAR IN (1989,1999)</codeph>, or <codeph>YEAR BETWEEN + 1984 AND 1989</codeph> can examine only the data files from the appropriate directory or directories, greatly + reducing the amount of data to read and test. + </p> + + + + </conbody> + +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_perf_hdfs_caching.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_hdfs_caching.xml b/docs/topics/impala_perf_hdfs_caching.xml new file mode 100644 index 0000000..b00b804 --- /dev/null +++ b/docs/topics/impala_perf_hdfs_caching.xml @@ -0,0 +1,22 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="1.4" id="hdfs_caching"> + + <title>Using HDFS Caching with Impala (CDH 5.1 or higher only)</title> + <titlealts audience="PDF"><navtitle>HDFS Caching</navtitle></titlealts> + + + <conbody> + + <p> + HDFS caching provides performance and scalability benefits in production environments where Impala queries + and other Hadoop jobs operate on quantities of data much larger than the physical RAM on the data nodes, + making it impractical to rely on the Linux OS cache, which only keeps the most recently used data in memory. + Data read from the HDFS cache avoids the overhead of checksumming and memory-to-memory copying involved when + using data from the Linux OS cache. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_perf_joins.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_joins.xml b/docs/topics/impala_perf_joins.xml new file mode 100644 index 0000000..b7c88b2 --- /dev/null +++ b/docs/topics/impala_perf_joins.xml @@ -0,0 +1,22 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="perf_joins"> + + <title>Performance Considerations for Join Queries</title> + <titlealts audience="PDF"><navtitle>Join Performance</navtitle></titlealts> + + + <conbody> + + <p> + Queries involving join operations often require more tuning than queries that refer to only one table. The + maximum size of the result set from a join query is the product of the number of rows in all the joined + tables. When joining several tables with millions or billions of rows, any missed opportunity to filter the + result set, or other inefficiency in the query, could lead to an operation that does not finish in a + practical time and has to be cancelled. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_perf_stats.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_stats.xml b/docs/topics/impala_perf_stats.xml new file mode 100644 index 0000000..7ed878f --- /dev/null +++ b/docs/topics/impala_perf_stats.xml @@ -0,0 +1,22 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="perf_stats"> + + <title>Table and Column Statistics</title> + + + <conbody> + + <p> + Impala can do better optimization for complex or multi-table queries when it has access to statistics about + the volume of data and how the values are distributed. Impala uses this information to help parallelize and + distribute the work for a query. For example, optimizing join queries requires a way of determining if one + table is <q>bigger</q> than another, which is a function of the number of rows and the average row size + for each table. The following sections describe the categories of statistics Impala can work + with, and how to produce them and keep them up to date. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_performance.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_performance.xml b/docs/topics/impala_performance.xml new file mode 100644 index 0000000..3d454ca --- /dev/null +++ b/docs/topics/impala_performance.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="performance"> + + <title>Tuning Impala for Performance</title> + <titlealts audience="PDF"><navtitle>Performance Tuning</navtitle></titlealts> + + + <conbody> + + <p> + The following sections explain the factors affecting the performance of Impala features, and procedures for + tuning, monitoring, and benchmarking Impala queries and other SQL operations. + </p> + + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_prereqs.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_prereqs.xml b/docs/topics/impala_prereqs.xml new file mode 100644 index 0000000..bb10263 --- /dev/null +++ b/docs/topics/impala_prereqs.xml @@ -0,0 +1,22 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="prereqs"> + + <title>Impala Requirements</title> + <titlealts audience="PDF"><navtitle>Requirements</navtitle></titlealts> + + + + <conbody> + + <p> + <indexterm audience="Cloudera">prerequisites</indexterm> + <indexterm audience="Cloudera">requirements</indexterm> + To perform as expected, Impala depends on the availability of the software, hardware, and configurations + described in the following sections. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_processes.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_processes.xml b/docs/topics/impala_processes.xml new file mode 100644 index 0000000..be8a9b8 --- /dev/null +++ b/docs/topics/impala_processes.xml @@ -0,0 +1,18 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="processes"> + + <title>Starting Impala</title> + + + <conbody> + + <p> + + To activate Impala if it is installed but not yet started: + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_reserved_words.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_reserved_words.xml b/docs/topics/impala_reserved_words.xml new file mode 100644 index 0000000..79dfb5c --- /dev/null +++ b/docs/topics/impala_reserved_words.xml @@ -0,0 +1,365 @@ +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="reserved_words"> + + <title>Impala Reserved Words</title> + <prolog> + <metadata> + <data name="Category" value="Impala"/> + <data name="Category" value="Troubleshooting"/> + <data name="Category" value="SQL"/> + <data name="Category" value="Planning"/> + <data name="Category" value="Developers"/> + <data name="Category" value="Data Analysts"/> + </metadata> + </prolog> + + <conbody> + + <p> + <indexterm audience="Cloudera">reserved words</indexterm> + The following are the reserved words for the current release of Impala. A reserved word is one that + cannot be used directly as an identifier; you must quote it with backticks. For example, a statement + <codeph>CREATE TABLE select (x INT)</codeph> fails, while <codeph>CREATE TABLE `select` (x INT)</codeph> + succeeds. Impala does not reserve the names of aggregate or scalar built-in functions. (Formerly, Impala did + reserve the names of some aggregate functions.) + </p> + + <p> + Because different database systems have different sets of reserved words, and the reserved words change from + release to release, carefully consider database, table, and column names to ensure maximum compatibility + between products and versions. + </p> + + <p> + Because you might switch between Impala and Hive when doing analytics and ETL, also consider whether + your object names are the same as any Hive keywords, and rename or quote any that conflict. Consult the + <xref href="https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Keywords,Non-reservedKeywordsandReservedKeywords"; scope="external" format="html">list of Hive keywords</xref>. + </p> + + <p outputclass="toc inpage"/> + + </conbody> + +<concept id="reserved_words_current"> +<title>List of Current Reserved Words</title> +<conbody> +<!-- This list is derived from the source code at: + https://github.com/cloudera/Impala/blob/master/fe/src/main/jflex/sql-scanner.flex + +See the history, any recent changes, here: + https://github.com/cloudera/Impala/commits/master/fe/src/main/jflex/sql-scanner.flex +--> + +<codeblock rev="ver">add +aggregate +all +alter +<ph rev="2.0.0">analytic</ph> +and +<ph rev="2.0.0">anti</ph> +<ph rev="1.4.0">api_version</ph> +as +asc +avro +between +bigint +<ph rev="1.4.0">binary</ph> +boolean +<ph rev="2.6.0">buckets</ph> +by +<ph rev="1.4.0">cached</ph> +<ph rev="2.3.0">cascade</ph> +case +cast +change +<ph rev="2.0.0">char</ph> +<ph rev="1.4.0">class</ph> +<ph rev="1.2.1">close_fn</ph> +column +columns +comment +compute +create +cross +<ph rev="2.0.0">current</ph> +data +database +databases +date +datetime +decimal +<ph rev="2.6.0">delete</ph> +delimited +desc +describe +distinct +<ph rev="2.6.0">distribute</ph> +div +double +drop +else +end +escaped +exists +explain +<ph rev="2.5.0">extended</ph> +external +false +fields +fileformat +<ph rev="1.2.1">finalize_fn</ph> +first +float +<ph rev="2.0.0">following</ph> +<ph rev="2.1.0">for</ph> +format +formatted +from +full +function +functions +<ph rev="2.1.0">grant</ph> +group +<ph rev="2.6.0">hash</ph> +having +if +<ph rev="2.6.0">ignore</ph> +<ph rev="2.5.0">ilike</ph> +in +<ph rev="2.1.0">incremental</ph> +<ph rev="1.2.1">init_fn</ph> +inner +inpath +insert +int +integer +intermediate +interval +into +invalidate +<ph rev="2.5.0">iregexp</ph> +is +join +last +left +like +limit +lines +load +location +<ph rev="1.2.1">merge_fn</ph> +metadata +not +null +nulls +offset +on +or +order +outer +<ph rev="2.0.0">over</ph> +overwrite +parquet +parquetfile +partition +partitioned +<ph rev="1.4.0">partitions</ph> +<ph rev="2.0.0">preceding</ph> +<ph rev="1.2.1">prepare_fn</ph> +<ph rev="1.4.0">produced</ph> +<ph rev="2.3.0">purge</ph> +<ph rev="2.0.0">range</ph> +rcfile +real +refresh +regexp +rename +replace +<ph rev="2.3.0">restrict</ph> +returns +<ph rev="2.1.0">revoke</ph> +right +rlike +<ph rev="2.1.0">role</ph> +<ph rev="2.1.0">roles</ph> +row +<ph rev="2.0.0">rows</ph> +schema +schemas +select +semi +sequencefile +serdeproperties +<ph rev="2.0.0">serialize_fn</ph> +set +show +smallint +<ph rev="2.6.0">split</ph> +stats +stored +straight_join +string +symbol +table +tables +tblproperties +terminated +textfile +then +timestamp +tinyint +to +true +<ph rev="2.0.0">truncate</ph> +<ph rev="2.0.0">unbounded</ph> +<ph rev="1.4.0">uncached</ph> +union +<ph rev="2.6.0">update</ph> +<ph rev="1.2.1">update_fn</ph> +use +using +values +<ph rev="2.0.0">varchar</ph> +view +when +where +with</codeblock> +</conbody> +</concept> + +<concept id="reserved_words_planning"> +<title>Planning for Future Reserved Words</title> +<conbody> +<p> +The previous list of reserved words includes all the keywords +used in the current level of Impala SQL syntax. +To future-proof your code, +you should avoid additional words in case they +become reserved words if +Impala adds features in later releases. +This kind of planning can also help to avoid +name conflicts in case you port SQL from other systems that +have different sets of reserved words. +</p> + +<p> +The following list contains additional words that Cloudera +recommends avoiding for table, column, or other object names, +even though they are not currently reserved by Impala. +</p> + +<codeblock>any +authorization +backup +begin +break +browse +bulk +cascade +check +checkpoint +close +clustered +coalesce +collate +commit +constraint +contains +continue +convert +current +current_date +current_time +current_timestamp +current_user +cursor +dbcc +deallocate +declare +default +deny +disk +distributed +dump +errlvl +escape +except +exec +execute +exit +fetch +file +fillfactor +for +foreign +freetext +goto +holdlock +identity +index +intersect +key +kill +lineno +merge +national +nocheck +nonclustered +nullif +of +off +offsets +open +option +percent +pivot +plan +precision +primary +print +proc +procedure +public +raiserror +read +readtext +reconfigure +references +replication +restore +restrict +return +revert +rollback +rowcount +rule +save +securityaudit +session_user +setuser +shutdown +some +statistics +system_user +tablesample +textsize +then +top +tran +transaction +trigger +try_convert +unique +unpivot +updatetext +user +varying +waitfor +while +within +writetext +</codeblock> +</conbody> +</concept> + +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_resource_management.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_resource_management.xml b/docs/topics/impala_resource_management.xml new file mode 100644 index 0000000..3fdbb15 --- /dev/null +++ b/docs/topics/impala_resource_management.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="1.2" id="resource_management"> + + <title>Resource Management for Impala</title> + + + <conbody> + + <note conref="../shared/impala_common.xml#common/impala_llama_obsolete"/> + + <p> + You can limit the CPU and memory resources used by Impala, to manage and prioritize workloads on clusters + that run jobs from many Hadoop components. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_revoke.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_revoke.xml b/docs/topics/impala_revoke.xml index 455b528..312d2b0 100644 --- a/docs/topics/impala_revoke.xml +++ b/docs/topics/impala_revoke.xml @@ -2,8 +2,8 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept rev="2.0.0" id="revoke"> - <title>REVOKE Statement (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala20"/> or higher only)</title> - <titlealts><navtitle>REVOKE</navtitle></titlealts> + <title>REVOKE Statement (CDH 5.2 or higher only)</title> + <titlealts><navtitle>REVOKE (CDH 5.2 or higher only)</navtitle></titlealts> <prolog> <metadata> <data name="Category" value="Impala"/> @@ -43,8 +43,8 @@ object_type ::= TABLE | DATABASE | SERVER | URI <p rev="2.3.0 collevelauth"> The ability to grant or revoke <codeph>SELECT</codeph> privilege on specific columns is available - in CDH 5.5 / Impala 2.3 and higher. See <xref href="sg_hive_sql.xml#concept_c2q_4qx_p4/col_level_auth_sentry"/> - for details. + in CDH 5.5 / Impala 2.3 and higher. <!--See <xref href="sg_hive_sql.xml#concept_c2q_4qx_p4/col_level_auth_sentry"/> + for details.--> </p> <p conref="../shared/impala_common.xml#common/privileges_blurb"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_s3.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_s3.xml b/docs/topics/impala_s3.xml new file mode 100644 index 0000000..6cb7834 --- /dev/null +++ b/docs/topics/impala_s3.xml @@ -0,0 +1,27 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="s3" rev="2.2.0"> + + <title>Using Impala with the Amazon S3 Filesystem</title> + <titlealts audience="PDF"><navtitle>S3 Tables</navtitle></titlealts> + + + <conbody> + + + + <p rev="2.2.0"> + + You can use Impala to query data residing on the Amazon S3 filesystem. This capability allows convenient + access to a storage system that is remotely managed, accessible from anywhere, and integrated with various + cloud-based services. Impala can query files in any supported file format from S3. The S3 storage location + can be for an entire table, or individual partitions in a partitioned table. + </p> + + + + </conbody> + </concept> + + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_scalability.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_scalability.xml b/docs/topics/impala_scalability.xml new file mode 100644 index 0000000..9abb1c5 --- /dev/null +++ b/docs/topics/impala_scalability.xml @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="scalability"> + + <title>Scalability Considerations for Impala</title> + <titlealts audience="PDF"><navtitle>Scalability Considerations</navtitle></titlealts> + + + <conbody> + + <p> + This section explains how the size of your cluster and the volume of data influences SQL performance and + schema design for Impala tables. Typically, adding more cluster capacity reduces problems due to memory + limits or disk throughput. On the other hand, larger clusters are more likely to have other kinds of + scalability issues, such as a single slow node that causes performance problems for queries. + </p> + + + </conbody> + + +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_security.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_security.xml b/docs/topics/impala_security.xml new file mode 100644 index 0000000..5c98fb1 --- /dev/null +++ b/docs/topics/impala_security.xml @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="security"> + + <title><ph audience="standalone">Impala Security</ph><ph audience="integrated">Overview of Impala Security</ph></title> + + <conbody> + + <p> + Impala includes a fine-grained authorization framework for Hadoop, based on the Sentry + open source project. Sentry authorization was added in Impala 1.1.0. Together with the Kerberos authentication + framework, Sentry takes Hadoop security to a new level needed for the requirements of highly regulated industries + such as healthcare, financial services, and government. Impala also includes + an auditing capability; Impala generates the audit data, the Cloudera Navigator product consolidates + the audit data from all nodes in the cluster, and Cloudera Manager lets you filter, visualize, and produce + reports. The auditing feature was added in Impala 1.1.1. + </p> + + + </conbody> +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_shell_options.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_shell_options.xml b/docs/topics/impala_shell_options.xml new file mode 100644 index 0000000..9f0bf60 --- /dev/null +++ b/docs/topics/impala_shell_options.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="shell_options"> + + <title>impala-shell Configuration Options</title> + <titlealts audience="PDF"><navtitle>Configuration Options</navtitle></titlealts> + + + <conbody> + + <p> + You can specify the following options when starting the <codeph>impala-shell</codeph> command to change how + shell commands are executed. The table shows the format to use when specifying each option on the command + line, or through the <filepath>$HOME/.impalarc</filepath> configuration file. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_struct.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_struct.xml b/docs/topics/impala_struct.xml index b7adb08..1e440fc 100644 --- a/docs/topics/impala_struct.xml +++ b/docs/topics/impala_struct.xml @@ -2,7 +2,7 @@ <concept id="struct"> - <title>STRUCT Complex Type (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> or higher only)</title> + <title>STRUCT Complex Type (CDH 5.5 or higher only)</title> <prolog> <metadata> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_tables.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_tables.xml b/docs/topics/impala_tables.xml index 27ddf37..30e3737 100644 --- a/docs/topics/impala_tables.xml +++ b/docs/topics/impala_tables.xml @@ -55,7 +55,7 @@ </ul> <p rev="2.2.0"> - Impala tables can also represent data that is stored in HBase, or in the Amazon S3 filesystem (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala22"/> or higher), + Impala tables can also represent data that is stored in HBase, or in the Amazon S3 filesystem (CDH 5.4.0 or higher), or on Isilon storage devices (CDH 5.4.3 or higher). See <xref href="impala_hbase.xml#impala_hbase"/>, <xref href="impala_s3.xml#s3"/>, and <xref href="impala_isilon.xml#impala_isilon"/> for details about those special kinds of tables. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_timeouts.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_timeouts.xml b/docs/topics/impala_timeouts.xml new file mode 100644 index 0000000..fe537a6 --- /dev/null +++ b/docs/topics/impala_timeouts.xml @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept rev="1.2.1" id="timeouts"> + + <title>Setting Timeout Periods for Daemons, Queries, and Sessions</title> + <titlealts audience="PDF"><navtitle>Setting Timeouts</navtitle></titlealts> + + + <conbody> + + <p> + Depending on how busy your CDH cluster is, you might increase or decrease various timeout values. + Increase timeouts if Impala is cancelling operations prematurely, when the system is + responding slower than usual but the operations are still successful if given extra time. + Decrease timeouts if operations are idle or hanging for long periods, and the + idle or hung operations are consuming resources and reducing concurrency. + </p> + + + </conbody> +</concept> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_truncate_table.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_truncate_table.xml b/docs/topics/impala_truncate_table.xml index 501eb4b..9f0d00b 100644 --- a/docs/topics/impala_truncate_table.xml +++ b/docs/topics/impala_truncate_table.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept rev="2.3.0 5.5.0" id="truncate_table"> - <title>TRUNCATE TABLE Statement (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala23"/> or higher only)</title> + <title>TRUNCATE TABLE Statement (CDH 5.5 or higher only)</title> <titlealts><navtitle>TRUNCATE TABLE</navtitle></titlealts> <prolog> <metadata> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_tutorial.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_tutorial.xml b/docs/topics/impala_tutorial.xml new file mode 100644 index 0000000..14c72c7 --- /dev/null +++ b/docs/topics/impala_tutorial.xml @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="tutorial"> + + <title id="tutorials">Impala Tutorials</title> + <titlealts audience="PDF"><navtitle>Tutorials</navtitle></titlealts> + + + <conbody> + + <p> + This section includes tutorial scenarios that demonstrate how to begin using Impala once the software is + installed. It focuses on techniques for loading data, because once you have some data in tables and can query + that data, you can quickly progress to more advanced Impala features. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_txtfile.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_txtfile.xml b/docs/topics/impala_txtfile.xml new file mode 100644 index 0000000..ec8c059 --- /dev/null +++ b/docs/topics/impala_txtfile.xml @@ -0,0 +1,24 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="txtfile"> + + <title>Using Text Data Files with Impala Tables</title> + <titlealts audience="PDF"><navtitle>Text Data Files</navtitle></titlealts> + + + <conbody> + + <p> + <indexterm audience="Cloudera">Text support in Impala</indexterm> + Impala supports using text files as the storage format for input and output. Text files are a + convenient format to use for interchange with other applications or scripts that produce or read delimited + text files, such as CSV or TSV with commas or tabs for delimiters. + </p> + + + + </conbody> + + </concept> + + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_update.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_update.xml b/docs/topics/impala_update.xml index a6743c5..3b9e330 100644 --- a/docs/topics/impala_update.xml +++ b/docs/topics/impala_update.xml @@ -2,7 +2,7 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept id="update"> - <title>UPDATE Statement (CDH ?? and higher only)</title> + <title>UPDATE Statement (CDH 5.5 and higher only)</title> <titlealts><navtitle>UPDATE</navtitle></titlealts> <prolog> <metadata> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_upgrading.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_upgrading.xml b/docs/topics/impala_upgrading.xml new file mode 100644 index 0000000..6fef62e --- /dev/null +++ b/docs/topics/impala_upgrading.xml @@ -0,0 +1,18 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="upgrading"> + + <title>Upgrading Impala</title> + + + <conbody> + + <p> + Upgrading Impala involves stopping Impala services, using your operating system's package management + tool to upgrade Impala to the latest version, and then restarting Impala services. + </p> + + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_varchar.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_varchar.xml b/docs/topics/impala_varchar.xml index 1052ec3..32db4ae 100644 --- a/docs/topics/impala_varchar.xml +++ b/docs/topics/impala_varchar.xml @@ -2,8 +2,8 @@ <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> <concept id="varchar" rev="2.0.0"> - <title>VARCHAR Data Type (<ph conref="../shared/ImpalaVariables.xml/impala_vars/impala20"/> or higher only)</title> - <titlealts><navtitle>VARCHAR</navtitle></titlealts> + <title>VARCHAR Data Type (CDH 5.2 or higher only)</title> + <titlealts><navtitle>VARCHAR (CDH 5.2 or higher only)</navtitle></titlealts> <prolog> <metadata> <data name="Category" value="Impala"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/impala_views.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_views.xml b/docs/topics/impala_views.xml index a6c1a41..78288b3 100644 --- a/docs/topics/impala_views.xml +++ b/docs/topics/impala_views.xml @@ -93,9 +93,9 @@ select * from report;</codeblock> <li rev="2.3.0 collevelauth"> Set up fine-grained security where a user can query some columns from a table but not other columns. Because CDH 5.5 / Impala 2.3 and higher support column-level authorization, this technique is no longer - required. If you formerly implemented column-level security through views, see + required. <!--If you formerly implemented column-level security through views, see <xref href="sg_hive_sql.xml#concept_c2q_4qx_p4/col_level_auth_sentry"/> for details about the - column-level authorization feature. + column-level authorization feature.--> <!-- See <xref href="impala_authorization.xml#security_examples/sec_ex_views"/> for details. --> </li> </ul> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/sg_hive_sql.xml ---------------------------------------------------------------------- diff --git a/docs/topics/sg_hive_sql.xml b/docs/topics/sg_hive_sql.xml new file mode 100644 index 0000000..3924c78 --- /dev/null +++ b/docs/topics/sg_hive_sql.xml @@ -0,0 +1,27 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="concept_c2q_4qx_p4"> + <title>Hive SQL Syntax for Use with Sentry</title> + + <conbody> + <p id="intro">Sentry permissions can be configured through Grant and Revoke statements + issued either interactively or programmatically through the HiveServer2 + SQL command line interface, Beeline (documentation available <xref + href="https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-Beeline%E2%80%93NewCommandLineShell"; + format="html" scope="external">here</xref>). The syntax described below + is very similar to the <codeph>GRANT/REVOKE</codeph> commands available in + well-established relational database systems.<note type="important"> + <ul id="ul_u1d_l5t_4r"> + <li>When Sentry is enabled, you must use Beeline to execute Hive + queries. Hive CLI is not supported with Sentry and must be + disabled.</li> + <li>There are some differences in syntax between Hive and the + corresponding Impala SQL statements. For the Impala syntax, see + <xref href="impala_langref_sql.xml#langref_sql">SQL + Statements</xref>.</li> + </ul> + </note></p> + + </conbody> + </concept> + http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8039fbb3/docs/topics/sg_redaction.xml ---------------------------------------------------------------------- diff --git a/docs/topics/sg_redaction.xml b/docs/topics/sg_redaction.xml new file mode 100644 index 0000000..96d27c1 --- /dev/null +++ b/docs/topics/sg_redaction.xml @@ -0,0 +1,22 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> +<concept id="log_redact"> + <title>Sensitive Data Redaction</title> + + <conbody> + <p>Data redaction is the suppression of sensitive data, such as any + personally identifiable information (PII). PII can be used on its own or + with other information to identify or locate a single person, or to + identify an individual in context. Enabling redaction allows you to + transform PII to a pattern that does not contain any identifiable + information. For example, you could replace all Social Security numbers + (SSN) like <codeph>123-45-6789</codeph> with an unintelligible pattern + like <codeph>XXX-XX-XXXX</codeph>, or replace only part of the SSN + (<codeph>XXX-XX-6789</codeph>).</p> + + </conbody> + </concept> + + + +
