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
Followup from Laurel's code reviews, to physically
remove references to Cloudera Manager that were hidden.
Remove a few stray instances of Cloudera Manager that I found
still remaining in the source.
Fix up trailing spaces introduced during earlier
Cloudera Manager-related edits.
Also remove stray 'Cloudera' references, or stale/commented
Cloudera-specific info, noticed near other spots being edited.
Change-Id: Ifc4a84527ae42c39b3717190b6cf669e17fff04b
Reviewed-on: http://gerrit.cloudera.org:8080/6325
Reviewed-by: Ambreen Kazi <ambreen.kazi@cloudera.com>
Reviewed-by: John Russell <jrussell@cloudera.com>
Tested-by: Impala Public Jenkins
This is part 1 of the changes being made to the Impala authorization
topics. References to CDH and Cloudera Manager docs/products have been
either 'hidden' or removed completely.
Examples with Sentry have been made more generic. Instances of
Cloudera-specific folders or filenames have been removed.
Change-Id: Ie5c4431f3236b18fc282343ed98513f0e578130e
Reviewed-on: http://gerrit.cloudera.org:8080/5931
Reviewed-by: Jim Apple <jbapple-impala@apache.org>
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
Initial experiment to see how the doc looks & builds when the biggest,
most obvious pieces of Cloudera Manager-related content are suppressed:
- Primarily entire subtopics.
- In some cases, individual notes, paragraphs, and list items.
- Also the CM reference in the reused "cancel" text which showed up
many times throughout the SQL syntax section.
Just hiding in the output for now, rather than removing from source,
because we might find there's generic material we need to hoist out of
the CM-related subtopics.
Was planning to use audience="hidden" to hide, but since that CR hasn't
landed in master yet, still using audience="Cloudera" for the moment,
and will switch attribute values later.
A little rewording of titles and suppressing smaller elements such as
paragraphs where the CM aspect didn't apply to the entire subtopic.
Change-Id: Ic799f77bc758a1cf40c53fa412bf02d852901a69
Reviewed-on: http://gerrit.cloudera.org:8080/5607
Reviewed-by: Jim Apple <jbapple-impala@apache.org>
Tested-by: John Russell <jrussell@cloudera.com>
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>
