You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2017/09/20 17:17:00 UTC

[jira] [Resolved] (IMPALA-3822) In IMPALA_KUDU, What are the best practices to avoid I/O transfers

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

Tim Armstrong resolved IMPALA-3822.
-----------------------------------
    Resolution: Invalid

Not a bug

> In IMPALA_KUDU,  What are the best practices to avoid I/O transfers
> -------------------------------------------------------------------
>
>                 Key: IMPALA-3822
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3822
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Kudu_Impala
>         Environment: Cloudera manager 5.4.7
>            Reporter: Ravi sharma
>            Priority: Minor
>             Fix For: Impala 1.4.2
>
>
> Hi 
> We are planning to have dimension tables in impala and fact tables in Kudu.
> What are the best practices to avoid unnecessary I/O transfers ??
> Thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)