phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4735) Improve defaults for out of the box configuration
Date Fri, 11 May 2018 00:03:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471302#comment-16471302
] 

Josh Elser commented on PHOENIX-4735:
-------------------------------------

I like all of the ideas you listed out. Let me think about some other 2ndary index things....

> Improve defaults for out of the box configuration
> -------------------------------------------------
>
>                 Key: PHOENIX-4735
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4735
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Priority: Major
>
> There are a number of features that require being enabled to use. I think it'd make sense
to update some of these for 5.0 release (and perhaps for 4.x releases too).
>  * *phoenix.default.update.cache.frequency* sets UPDATE_CACHE_FREQUENCY for newly created
tables to prevent an RPC per query to RS hostingĀ  SYSTEM.CATALOG. A default value of 5000
(5 seconds) would be good.
>  * *phoenix.use.stats.parallelization* determines if we use statistics to further parallelize
a query. A default value of false would be good default as clusters can become overloaded
if the guidepost width is set too low. We'd still parallelize by region.
>  * *phoenix.costbased.optimizer.enabled* determines if optimizer decisions should use
statistics. We should set this to true by default as it improves decisions made by the optimizer.
>  * *phoenix.autoupgrade.enabled* determines if an upgrade is automatically triggered
when the first new client connects to a newer server. We should set the default value to be
false and force users to run the {{EXECUTE UPGRADE}} command so that upgrades are more explicit.
>  * *phoenix.schema.isNamespaceMappingEnabled* determines if schemas map to namespaces
in HBase. We should turn this on by default.
>  * *phoenix.schema.mapSystemTablesToNamespace* same as above, but for SYSTEM schema.
We should turn this on by default as well



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message