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/04/06 17:59:41 UTC

[jira] [Resolved] (IMPALA-3848) Decide if doc in some areas (performance tuning, troubleshooting) is vendor-specific

     [ https://issues.apache.org/jira/browse/IMPALA-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Russell resolved IMPALA-3848.
----------------------------------
    Resolution: Fixed

This will be something to look out for going forward. All the immediate / obvious material like this (FAQ, installation, upgrading, etc.) was already taken care of under other JIRAs.

> Decide if doc in some areas (performance tuning, troubleshooting) is vendor-specific
> ------------------------------------------------------------------------------------
>
>                 Key: IMPALA-3848
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3848
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Docs
>    Affects Versions: Impala 2.5.0
>            Reporter: John Russell
>            Assignee: John Russell
>            Priority: Trivial
>              Labels: asf
>
> There is Impala doc information that doesn't explicitly reference Cloudera but still might not be entirely generic. In particular, some advice about performance and scalability (things like calculating number of nodes to devote to Impala in a cluster) may reflect CDH-specific assumptions.
> This work item is to evaluate on a case-by-case basis whether claims or advice are not applicable to the core Apache Impala, and revise if so. I'll mark it as lower-than-usual priority because this type of thing is more subtle than explicit references to vendor or product names.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)