You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:19:22 UTC

[jira] [Resolved] (PHOENIX-373) Performance of salted table?

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

Gabriel Reid resolved PHOENIX-373.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Performance of salted table?
> ----------------------------
>
>                 Key: PHOENIX-373
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-373
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Raymond Liu
>
> If I have key_part1, key_part2, key_part3 as combined key. And I do want to get all kv that key_part1 = k1.
> Since the table is salted and thus scattered, it seems to me that it will need to scan full table and load all data from disk to get all kv with key_part1 = k1?
> while if I do not use salted table, then only the block with key_part1 = k1 need to scan and load related data from disk?
> Seems under this condition, salted table is not a good choice?



--
This message was sent by Atlassian JIRA
(v6.2#6252)