You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "John Russell (JIRA)" <ji...@apache.org> on 2017/03/16 17:44:41 UTC
[jira] [Resolved] (IMPALA-3402) Remove CDH version number
dependencies from doc source
[ https://issues.apache.org/jira/browse/IMPALA-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Russell resolved IMPALA-3402.
----------------------------------
Resolution: Fixed
All the version number references are gone. The final few instances of 'cloudera' or 'cdh' are from different contexts.
> Remove CDH version number dependencies from doc source
> ------------------------------------------------------
>
> Key: IMPALA-3402
> URL: https://issues.apache.org/jira/browse/IMPALA-3402
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
> Affects Versions: Impala 2.5.0
> Reporter: John Russell
> Assignee: John Russell
> Priority: Minor
>
> There are many instances where we list CDH version numbers and corresponding Impala version numbers right next to each other, e.g. "In CDH 5.5 / Impala 2.3 and higher, you can use such-and-such a feature". Probably we will set up a substitution variable so that in the ASF docs these references can resolve to just the Impala version number, while in vendor-specific docs it can be changed to the right naming/numbering for that vendor if they republish the same content.
> There are also some contexts where space is at a premium, e.g. in headings, where we only reference the CDH version number. For example, "FOO Data Type (CDH 5.5 or higher only)". These could be handled by a second substitution variable, or perhaps folded into the first substitution variable if it was appropriate for vendor-specific docs to avoid repeating Impala version numbers all over the place.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)