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

Posted to dev@phoenix.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2016/08/29 16:44:20 UTC

[jira] [Created] (PHOENIX-3217) Phoenix sets MAX_FILESIZE table attribute for index tables

Andrew Purtell created PHOENIX-3217:
---------------------------------------

             Summary: Phoenix sets MAX_FILESIZE table attribute for index tables
                 Key: PHOENIX-3217
                 URL: https://issues.apache.org/jira/browse/PHOENIX-3217
             Project: Phoenix
          Issue Type: Bug
            Reporter: Andrew Purtell


Phoenix appears to set the HBase table attribute MAX_FILESIZE for index tables. We should discuss this. This setting is a user tunable that impacts splitting decisions. It should be set in conjunction with a split policy not in isolation. Is it necessary to do this for index tables? Because this is an important user tunable, overriding the value is likely to lead to surprise and unexpected cluster behavior. 



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