You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/01/26 01:28:00 UTC

[jira] [Updated] (IMPALA-8102) Impala/HBase recommendations need update

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

Tim Armstrong updated IMPALA-8102:
----------------------------------
    Target Version: Impala 3.2.0

> Impala/HBase recommendations need update
> ----------------------------------------
>
>                 Key: IMPALA-8102
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8102
>             Project: IMPALA
>          Issue Type: Documentation
>          Components: Docs
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>
> https://impala.apache.org/docs/build/html/topics/impala_hbase.html hasn't been updated for a while. The recommendations are a bit out of date - generally HBase is not the best format for analytic workloads yet that page seems to encourage using it.
> E.g.
> {quote}If you have join queries that do aggregation operations on large fact tables and join the results against small dimension tables, consider using Impala for the fact tables and HBase for the dimension tables.{quote}
> Assigning to myself to figure out what the best practice is, but I think we need to include:
> * A statement Kudu offers significantly better performance for analytical workloads with mutable data
> * A statement that HDFS tables are also preferable unless data is frequently mutated
> * A pointer to the Kudu docs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org