[IMPALA-3411] Rework Impala data management / governance info to be generic

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Impala 2.5.0
• Fix Version/s: Impala 2.9.0
• Component/s: Docs
• Labels: doc_cleanup
• Assignee: Ambreen Kazi
• Reporter: John Russell
• Created: 22/Apr/16 20:20
• Updated: 08/Jun/17 18:52
• Resolved: 23/Feb/17 22:07

Description

This work item primarily affects one file, impala_lineage.xml. The emphasis on that page is on how the lineage data is consumed by one particular client application (Cloudera Navigator). The information applicable to Impala itself is in the subsection "Lineage Data for Impala". Most of the rest of the page should be removed, with a couple of introductory sentences rewritten to say that the purpose of the lineage info is to be consumed by governance-focused components.

Also any stray references to Cloudera Navigator should be handled under this JIRA so that they're treated consistently.

$ grep -l "Cloudera Navigator" *.xml ../shared/*.xml
impala_auditing.xml
impala_lineage.xml
impala_security.xml

Under impala_auditing.xml, there's a comment mentioning Cloudera Navigator that can go, and a couple of procedure steps that mention Cloudera Navigator and Cloudera Manager that can also go.

There's a very brief mention under impala_security.xml that can be replaced with a generic statement that audit data generated by Impala is intended to be consumed and acted upon using non-Impala components.