phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-2762) Phoenix creating global index tables with MAX_FILESIZE of 11994435 (11.99 MB) when creating index on one column in a wide table.
Date Sat, 12 Mar 2016 21:33:03 GMT
Anil Gupta created PHOENIX-2762:
-----------------------------------

             Summary: Phoenix creating global index tables with MAX_FILESIZE of 11994435 (11.99
MB) when creating index on one column in a wide table.
                 Key: PHOENIX-2762
                 URL: https://issues.apache.org/jira/browse/PHOENIX-2762
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.6.0, 4.5.0, 4.4.0, 4.7.0
            Reporter: Anil Gupta
            Priority: Minor


We have set default MAX_FILESIZE=8GB on our cluster.
Main table has around 1100 columns. I create an index on one column. Max_filesize in secondary
index table is set to 11.99MB ( i.e. (1/1100)*8GB) approximately . 
This leads to excessive splitting of regions and a lot of regions for secondary index table.
So, i think, we need to set a lower bound on region size of secondary index tables in Phoenix.


I propose to have a Phoenix property(phoenix.global.index.maxfilesize.min)  to set lower bound
of max_filesize of secondary index table. 

Please refer to this http://search-hadoop.com/m/9UY0h2DNmug2BAMko for details.



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

Mime
View raw message