Details

    • 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:
      None

      Description

      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.

        Activity

        Hide
        lv Lars Volker added a comment -

        I'm changing the "Fix Version/s" to 2.9 as part of a bulk edit. If you think this is wrong, please set the version to the correct one.

        Show
        lv Lars Volker added a comment - I'm changing the "Fix Version/s" to 2.9 as part of a bulk edit. If you think this is wrong, please set the version to the correct one.
        Hide
        jrussell John Russell added a comment -

        All the version number references are gone. The final few instances of 'cloudera' or 'cdh' are from different contexts.

        Show
        jrussell John Russell added a comment - All the version number references are gone. The final few instances of 'cloudera' or 'cdh' are from different contexts.

          People

          • Assignee:
            jrussell John Russell
            Reporter:
            jrussell John Russell
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development