[
https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475235#comment-15475235
]
Hudson commented on PHOENIX-3228:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.8-HBase-1.2 #12 (See
[https://builds.apache.org/job/Phoenix-4.8-HBase-1.2/12/])
PHOENIX-3228 Index tables should not be configured with a custom/smaller
(larsh: rev 03e10054979e800acb72c362594fb18a5d3830f3)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
> Index tables should not be 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-remove.txt, 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)
