The pre-commit hook that used to detect
and fix trailing spaces in doc XML files
seems to have bitrotted and some trailing
spaces made it into source files during the
initial upstream cleanup.
Change-Id: Ieeb6a7d557c37be981add8353cbd1756f2e1e423
Reviewed-on: http://gerrit.cloudera.org:8080/7373
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins
Per fe/src/test/java/org/apache/impala/analysis/AnalyzeExprsTest.java#L1593
Change-Id: I1e62f295efaa9084a6da682fd04bfb067ec5e4e8
Reviewed-on: http://gerrit.cloudera.org:8080/7342
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
A number of 'CDH' by itself were turned into substitution
variables resolving to 'Apache Hadoop'.
Also fixed some stray instances of CDH version numbers.
In some cases, 'CDH' or 'CDH 5' by itself was superfluous and was
just removed.
Change-Id: I979ea73ccaa5873d4108545f18f598072fb5e05f
Reviewed-on: http://gerrit.cloudera.org:8080/6352
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
For history and tracking purposes, there are many
instances of rev="CDH-1234" for various CDH- JIRA
numbers. This produces no visible output, it's just
FYI for the person editing the source. Removing all
these now from the upstream doc source, so as not
to have "CDH" all through the doc source files.
Change-Id: I29089e5a31cd72e876b2ccb8375d1c10693c6aba
Reviewed-on: http://gerrit.cloudera.org:8080/6349
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
For this change to land in master, the audience="hidden" code review
needs to be completed first. Otherwise, the doc build would still work
but the audience="hidden" content would be visible rather than hidden as
desired.
Some work happening in parallel might introduce additional instances of
audience="Cloudera". I suggest addressing those in a followup CR so this
global change can land quickly.
Since the changes apply across so many different files, but are so
narrow in scope, I suggest that the way to validate (check that no
extraneous changes were introduced accidentally) is to diff just the
changed lines:
git diff -U0 HEAD^ HEAD
In patch set 2, I updated other topics marked audience="Cloudera"
by CRs that were pushed in the meantime.
Change-Id: Ic93d89da77e1f51bbf548a522d98d0c4e2fb31c8
Reviewed-on: http://gerrit.cloudera.org:8080/5613
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
This now gives a clean RAT check with bin/check-rat-report.py, which
is one way for the Impala community to check compliance with ASF rules
on intellectual property.
Change-Id: I2ad06435f84a65ba126759e42a18fdaf52cd7036
Reviewed-on: http://gerrit.cloudera.org:8080/5232
Reviewed-by: Jim Apple <jbapple-impala@apache.org>
Tested-by: Impala Public Jenkins
Reviewed-by: John Russell <jrussell@cloudera.com>
These are refugees from doc_prototype. They can be rendered with the
DITA Open Toolkit version 2.3.3 by:
/tmp/dita-ot-2.3.3/bin/dita \
-i impala.ditamap \
-f html5 \
-o $(mktemp -d) \
-filter impala_html.ditaval
Change-Id: I8861e99adc446f659a04463ca78c79200669484f
Reviewed-on: http://gerrit.cloudera.org:8080/5014
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: John Russell <jrussell@cloudera.com>
