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

Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2016/08/30 23:32:21 UTC

[jira] [Assigned] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

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

Lars Hofhansl reassigned PHOENIX-3228:
--------------------------------------

    Assignee: Lars Hofhansl

> Index table are configured with a custom/smaller MAX_FILESIZE
> -------------------------------------------------------------
>
>                 Key: PHOENIX-3228
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3228
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 4.9.0, 4.8.1
>
>         Attachments: 3228.txt
>
>
> I do not think we should do this. The default of 10G is chosen to keep HBase happy. For smaller tables or initially until the index gets large it might lead to more index regions and hence be able to utilize more region server, but generally, this is not the right thing to do.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)