The text from impala_common.xml is reused verbatim under
the REFRESH page and in the UDFs page by a #include-like
mechanism.
Change-Id: Ic41fec781396b69e6df06b8de0b29c42ad51ce8f
Reviewed-on: http://gerrit.cloudera.org:8080/7044
Reviewed-by: Taras Bobrovytsky <tbobrovytsky@cloudera.com>
Tested-by: Impala Public Jenkins
The discussion / illustration of which operators are pushed to Kudu
is under the EXPLAIN topic.
Change-Id: I3af6d3dbb10528081603c103bf1c2be2e6fc51c3
Reviewed-on: http://gerrit.cloudera.org:8080/7066
Reviewed-by: Matthew Jacobs <mj@cloudera.com>
Tested-by: Impala Public Jenkins
Switched the example for Infinity and NaN in the
impala.common file so it will be correct every-
where this example is used in the Impala
documentation. Instead of saying, "pow(-1, 0.5)
returns infinity and 1/0 returns NaN" it has
been corrected to "1/0 returns infinity and
pow(-1, 0.5) returns NaN."
Change-Id: I0e5d950b250c2e4425bde7d9e0bccbb068a73e12
Reviewed-on: http://gerrit.cloudera.org:8080/7083
Reviewed-by: Todd Lipcon <todd@apache.org>
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
The related JIRAs IMPALA-2293 and IMPALA-1503 are asking for the
code behavior to be changed to match the documentation. In the
meantime, changing the documentation to match the code.
I grepped the doc source for other instances of INTERVAL arithmetic
and this was the only one that used a string literal as the
starting point.
Change-Id: I3e2af386176e7c310ced221fa77d73c97a9f8590
Reviewed-on: http://gerrit.cloudera.org:8080/7067
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
Review part 1: Just tackling the CREATE TABLE syntax and examples for
now. Will have separate gerrits for ALTER TABLE and more far-flung
places to mention this feature (New Features, Performance
Considerations, Parquet File Format).
Change-Id: Icd571cd8840368edb327d16d27192458838ef234
Reviewed-on: http://gerrit.cloudera.org:8080/6981
Reviewed-by: Lars Volker <lv@cloudera.com>
Tested-by: Impala Public Jenkins
IMPALA-4432 is actually an incompatible change, so it gets
listed on the separate "Incompatible Changes" page.
Change-Id: Ibeed92e8f6603b858622b1d397d1f5cad810f4cf
Reviewed-on: http://gerrit.cloudera.org:8080/5809
Reviewed-by: Tim Armstrong <tarmstrong@cloudera.com>
Reviewed-by: Sailesh Mukil <sailesh@cloudera.com>
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
I added the syntax and examples under ALTER TABLE, and also amended
the wording in the list of ALTER TABLE restrictions to reflect the
lifting of some restrictions.
I didn't have detailed discussion of ALTER TABLE in the impala_kudu.xml
page, so I didn't make any changes there.
Change-Id: I5f87155dcba860f6fd9259387fea52bbe439e028
Reviewed-on: http://gerrit.cloudera.org:8080/7041
Reviewed-by: Matthew Jacobs <mj@cloudera.com>
Tested-by: Impala Public Jenkins
Included syntax, mention of performance benefit, and examples.
Also added an item in the "new features" list with a link to the
detailed writeup.
Change-Id: Ib576fba03673bd6708a46f45c8388477b25e34da
Reviewed-on: http://gerrit.cloudera.org:8080/6979
Reviewed-by: Greg Rahn <grahn@cloudera.com>
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
Remove the "DISTINCT not allowed" restriction.
Add DISTINCT to syntax.
Add an example showing usage of DISTINCT.
Change-Id: Ib7d4555a5bc4c4195fa1529d1c1bdf39f98e7346
Reviewed-on: http://gerrit.cloudera.org:8080/7016
Reviewed-by: Alex Behm <alex.behm@cloudera.com>
Tested-by: Impala Public Jenkins
Instead of default 0 switching to 1 for verbose, now the default
is 1 (named 'standard') and extended is 2.
Change-Id: Ib18cfbfa35a4e3b324e6744da62de2fad86c1e67
Reviewed-on: http://gerrit.cloudera.org:8080/6966
Reviewed-by: Alex Behm <alex.behm@cloudera.com>
Tested-by: Impala Public Jenkins
The writeup for sortby() was removed during the gerrit review
process. This bullet in the New Features list was left behind,
and is now being removed.
Change-Id: Ib0c32df2dcfbde47a16e4692e5953b31cb144bcc
Reviewed-on: http://gerrit.cloudera.org:8080/6965
Reviewed-by: Alex Behm <alex.behm@cloudera.com>
Tested-by: Impala Public Jenkins
Start with placeholder for 2.9 new features topic.
Initially just point to the changelog file.
Change-Id: I1f6cabc2427daf1243bd69dbed295c6923c4091b
Reviewed-on: http://gerrit.cloudera.org:8080/6954
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
Add CLUSTERED hint.
Update hint syntax in INSERT topic.
Also modernize the hint syntax as shown under INSERT
to include the -- and /* */ formats also. List
the [] style last since it is the least-preferred
option.
Switch to preferring /* */ syntax for hints
instead of using the [ ] notation by default.
Finally, take out references to the SORTBY hint because
it didn't actually make it in. Intent for future is to have a way
to get this behavior without using a hint.
Change-Id: Id3c1da9a87ace361b096fa73d8504b2f54e75bed
Reviewed-on: http://gerrit.cloudera.org:8080/5655
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Allow users to keep a longer history of queries if desired. I
personally find it useful to keep a long history of queries to
reference and want to bump this up to a very large value, but
keep the default reasonable. Also change the config loader
to not freak out over unknown parameters so as not to break
for users that end up with new options set running on older
shells.
Testing: Created .impalarc as follows, now getting more history saved.
Put broken things in .impalarc and make sure they are logged as
warnings.
[impala]
history_max=1000
Change-Id: Iaf65bbecb8fd7f1105aac62b6745d6125a603d7f
Reviewed-on: http://gerrit.cloudera.org:8080/6335
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
Add a note that idle_session_timeout and idle_query_timeout
might take up to 50% longer than the specified interval
before cancellation occurs.
Also rearrange the text a little to put QUERY_TIMEOUT_S
explanation adjacent to the idle_query_timeout explanation.
This results in an indentation change that makes the diff
look bigger than it really is. The <note> element is the
only actual added content.
Change-Id: I0b19912dac1df13bfcbcb67f0bd4ed0064ad8db9
Reviewed-on: http://gerrit.cloudera.org:8080/6463
Tested-by: Impala Public Jenkins
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Link to Apache Kudu docs for details of new security features.
Change-Id: I1266ad38468ef2e987aff5aaaa4db35e6cafdacc
Reviewed-on: http://gerrit.cloudera.org:8080/6634
Reviewed-by: Matthew Jacobs <mj@cloudera.com>
Tested-by: Impala Public Jenkins
The JIRA discusses a RANDOM_REPLICA query option but Impala only
has a SCHEDULE_RANDOM_REPLICA option. So I stated that the
RANDOM_REPLICA hint is the same as specifying
SCHEDULE_RANDOM_REPLICA=true. Please confirm.
Change-Id: I7284dd45c8173eef104ebd32789429e8c16c7bf2
Reviewed-on: http://gerrit.cloudera.org:8080/6631
Reviewed-by: Lars Volker <lv@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Currently unsupported, so the topic doesn't go into
detail about behavior.
Change-Id: I7a3bbd0d56da548d8d42e8ef3b71f2c014bc822d
Reviewed-on: http://gerrit.cloudera.org:8080/6596
Reviewed-by: Greg Rahn <grahn@cloudera.com>
Reviewed-by: Dan Hecht <dhecht@cloudera.com>
Tested-by: Impala Public Jenkins
In addition to switching URLs for individual JIRAs
to point to issues.apache.org, also construct alternative
URLs for JIRA reports (usually 1 per release, summarizing
the issues fixed in that release).
There is some inconsistency in which releases have associated
JIRA reports. For releases where we never published a link to
a JIRA report, I added a <keydef> tag that could be used to
construct a report in future, but didn't fill in any URL.
Some releases do have a link to a JIRA report in the release
notes, however the report is empty. Possibly there was some
strangeness around the release process for those, or there
could be some missing info in the JIRA system. I just
transcribed the links in those cases and didn't try to
reconstruct the history to debug the empty reports.
Change-Id: I007e634f9da57289674683dd5bf64e3e3ca8f525
Reviewed-on: http://gerrit.cloudera.org:8080/6515
Reviewed-by: Laurel Hale <laurel@cloudera.com>
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
Move docs/generatingImpalaDoc.md to docs/README.md. This will
automatically render the document inline at places like:
https://github.com/apache/incubator-impala/tree/master/docs
under the directory listing.
Fix existing markdown which wasn't always rendering properly. Remove
unneeded HTML and backslashes. Add a mention of make, and add one
troubleshooting tip. Wrap most lines at 90 chars. This does not change
how Github renders the markdown, and it makes reading the source easier
as well.
Explain how to get dita into PATH.
Emphasize make and remove some of the dita advanced usage.
Change-Id: I71ae79ecd346045697fe225140ee9a317c5a337f
Reviewed-on: http://gerrit.cloudera.org:8080/6512
Reviewed-by: Jim Apple <jbapple-impala@apache.org>
Tested-by: Michael Brown <mikeb@cloudera.com>
Hide a couple of assertions that someone should
go or view things online, on Cloudera-specific
github repos.
Blank out some Cloudera-specific URLs for
sample source files. This causes the relevant
links to disappear - what was linked text is
now just plain text. The user can still work
off the excerpts in the docs, just not see
the entire file.
Once an authoritative Apache-friendly location
is set up for UDF development, the URLs can be
filled in and the relevant links will reappear
in the doc output.
Change-Id: Id5f325c88c5e9f1a7cd64d13ba7aa23249838181
Reviewed-on: http://gerrit.cloudera.org:8080/6464
Reviewed-by: Tim Armstrong <tarmstrong@cloudera.com>
Reviewed-by: Jim Apple <jbapple-impala@apache.org>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Update all URLs in *keydefs* file that point to
issues.cloudera.org.
Update all <xref> tags in the doc source that point
to individual JIRA issues on issues.cloudera.org.
(Leave alone links pointing to JIRA reports; those
don't seem to be redirected currently.)
Change-Id: I9ad2725e4afedddedf8ba65963b217803f532dea
Reviewed-on: http://gerrit.cloudera.org:8080/6452
Reviewed-by: Laurel Hale <laurel@cloudera.com>
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Make the statement about who uses which ports for
Impala less specific w.r.t. the Cloudera ODBC driver.
Change-Id: Ida0fa4f25934eaebf095b427413f20944f1a4f71
Reviewed-on: http://gerrit.cloudera.org:8080/6440
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Remove the Cloudera-specific portion of the
Impala + ODBC page, leaving just the background
info about why to use ODBC. Defer to third parties
who supply ODBC drivers.
Change-Id: I302d23432d348aa0c9c2837c0f42bc4f2844f9b8
Reviewed-on: http://gerrit.cloudera.org:8080/6409
Reviewed-by: Jim Apple <jbapple-impala@apache.org>
Tested-by: Impala Public Jenkins
Re-enable an xref that was conditionalized out,
but make it produce plaintext instead of a link.
Change-Id: I11fcac18533ea07ef03013034d246b8273882c96
Reviewed-on: http://gerrit.cloudera.org:8080/6396
Reviewed-by: Laurel Hale <laurel@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
A couple of fleeting / invisible references to 'cm'.
Take 'em out to avoid false positives in our grep reports.
Change-Id: Ia510a1eb53eba2f1127f57fa1f8bfe39525e0613
Reviewed-on: http://gerrit.cloudera.org:8080/6391
Reviewed-by: Laurel Hale <laurel@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Leave behind a reference that says we got rid of all 'Cloudera Impala'
etc., but take out the wording that states this is an ongoing activity.
Change-Id: Ic3db9e1a9c1e4acf49ce072eceee2ba437590bf8
Reviewed-on: http://gerrit.cloudera.org:8080/6392
Reviewed-by: Laurel Hale <laurel@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
The impala_fixed_issues page included commented
lists of JIRAs including URLs of non-public
Google docs prepared by the CCE team. Take 'em out.
Also in one case where 'CDH' was intentionally left in
the topic of a subtitle, 'CDH' can still be removed from
the cause/workaround text.
Change-Id: I4383811dc25ebd1c326cbd1e12a985848da3abb5
Reviewed-on: http://gerrit.cloudera.org:8080/6390
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Remove some UDF-related URLs pointing to /cloudera/ github
from the XML source.
The HTML links still point to /cloudera/ URLs, but those can
be re-pointed easily without touching this same source file.
Also change some /user/cloudera/ references to an HDFS
user name.
Change-Id: Ia1aec8b2dbe1316c98a40f05ad537b8f173208d6
Reviewed-on: http://gerrit.cloudera.org:8080/6388
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Revise a couple of CM-specific paths shown in debugging example.
The edited paths are nonexistent, but that doesn't matter for
purposes of illustration.
Change-Id: If45f9c549e2a0d46a7eb43c4ce09673adaae9982
Reviewed-on: http://gerrit.cloudera.org:8080/6386
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Remove one Cloudera reference that's present in
one XML file and conref'ed into a different HTML page.
Change-Id: If7fa92412bda37510fa604a908c905709183d6bd
Reviewed-on: http://gerrit.cloudera.org:8080/6383
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Remove last few 'Cloudera recommends' plus
some obsolete/unused Llama text that mentioned CDH.
Change-Id: Ia8544830ad564e59c5eae9844ff3fc255f4ae533
Reviewed-on: http://gerrit.cloudera.org:8080/6381
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
One stray reference to 'CDH cluster' (split across
lines). Turn into substitution variable.
Change-Id: I28fc800c6652e45de0a95ca9448c99a28ab2072c
Reviewed-on: http://gerrit.cloudera.org:8080/6379
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
The verification job succeeded in merging gerrit #6345
despite the presence of a build error. Fixing the build
error in a separate gerrit because can't continue #6345
once it's merged.
Change-Id: I9bf8d11e06a68103f6760db72cedf372363f75f0
Reviewed-on: http://gerrit.cloudera.org:8080/6373
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Get rid of cloudera.com URLs within the topics/*.xml source files.
Abstract any that need to remain (e.g. blog posts) into impala_keydefs
file for easy examining and editing.
After this change, the number of source/artifact references to CDH and
Cloudera is small enough that we can enumerate exceptions and start the endgame:
Cleanup items remaining in XML source files:
grep -EiI "[^a-zA-Z]cm[^a-zA-Z]|cdh|cloudera" *.xml |
grep -v issues.cloudera.org | wc -l
282
Cleanup items remaining in HTML output files:
grep -EiI "[^a-zA-Z]cm[^a-zA-Z]|cdh|cloudera" ../build/html/topics/*.html |
grep -v issues.cloudera.org | wc -l
148
(These numbers will go down further when the 'installing' and 'updating'
edits land in master.)
Change-Id: I9e29c0feec7bd8e974d8a3d1eb84abe757514be7
Reviewed-on: http://gerrit.cloudera.org:8080/6345
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
A couple of Cloudera Manager references referred to
'CM-managed' clusters. Remove those.
Change-Id: I844abacb97ba089f54ef65039c79a80519928037
Reviewed-on: http://gerrit.cloudera.org:8080/6369
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Tested-by: Impala Public Jenkins
