[
https://issues.apache.org/jira/browse/PHOENIX-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376225#comment-14376225
]
Samarth Jain commented on PHOENIX-1746:
---------------------------------------
Looks good to me. One question, if a 4.3.1 client connects to 4.3.0 server,
then will UPDATE STATS SET GUIDEPOST_WIDTH be a no-op? If that is the case
then is it an OK behavior to have considering we support backward and forward
compatibility with patch releases.
> Pass through guidepost config params on UPDATE STATISTICS call
> --------------------------------------------------------------
>
> Key: PHOENIX-1746
> URL: https://issues.apache.org/jira/browse/PHOENIX-1746
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Assignee: James Taylor
> Labels: 4.3.1
> Attachments: PHOENIX-1746.patch
>
>
> We should pass through the properties from the client-side that drive the
> guidepost width when UPDATE STATISTICS is manually invoked. That'll allow
> easier experimentation without requiring a config change plus rolling restart.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
