Several instances of things to revise on this page.
For example, com/cloudera in paths, -cdh570 in
filenames, and cloudera in github URLs.
There will still be some cloudera github URLs in the
HTML output after this change, but the source of the
CREATE FUNCTION page itself will be clean. (The URLs
in question will be edited in impala_keydefs.ditamap
as part of the endgame to revise various github URLs
related to UDF development.
Change-Id: I42fc2c59e744e43504ad92dc94f6659a59f49bd2
Reviewed-on: http://gerrit.cloudera.org:8080/6371
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
Genericize 3-part version numbers in "known issues".
Genericize CDH version numbers in 'ports' topic.
Genericize 'Cloudera' and hostnames in 'Tables' topic.
Genericize the version numbers in 'added in' blurbs.
Remove lots of CDH / Impala notices from release notes.
Remove obsolete conref'able elements that weren't
actually being called from anywhere, that contained
CDH version number wording.
Reword 'Cloudera recommends'.
Remove more hidden or commented material with
Cloudera-specific wording.
Remove obsolete CDH references from 'incompatible changes'.
Change 'cloudera' HDFS username for LOAD DATA examples.
Remove material related to big lists of CDH fixed JIRAs.
Genericize some CDH-related language.
Change-Id: Iaa5db6c20f4d010972ade4945a3ea59b32ef95de
Reviewed-on: http://gerrit.cloudera.org:8080/6267
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>
