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

James Taylor commented on PHOENIX-1322:
---------------------------------------

I'm going to tweak the name to match SQL Server. I think it's a little more 
clear on what the command is doing, plus we need options to update the stats 
for the table, indexes, or both (which the UPDATE STATISTICS supports through a 
COLUMNS, INDEX, or ALL option).

So the command will be:
{code}
UPDATE STATISTICS <tableName> [COLUMNS, INDEX, ALL]
{code}
with the default being ALL which analyzes the table and all indexes. The 
COLUMNS option would only analyze the table and the INDEX option would only 
analyze the indexes.

> Add documentation for UPDATE STATISTICS command
> -----------------------------------------------
>
>                 Key: PHOENIX-1322
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1322
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: ramkrishna.s.vasudevan
>
> Four places need to be updated:
> - Add a new webpage and add the webpage to the Using menu 
> (/site/source/src/site/site.xml). The webpage can talk about the new ANALYZE 
> <table> command and give a couple of examples. It'd be good to document that 
> stats are updated automatically during splits and compaction. Also, mention 
> the new property values you added to control - number of bytes before 
> guidepost put in, min time before another analyze may be done. Don't talk 
> about implementation, though, other than the "why" we're doing this (i.e. to 
> improve parallelization).
> - Add the new ANALYZE call with a short explanation to 
> ./phoenix-docs/src/docsrc/help/phoenix.csv. This will cause it to appear 
> here: http://phoenix.apache.org/language/index.html
> - Add an item at the top for Statistics Collection with a short explanation 
> here: site/source/src/site/markdown/recent.md
> - Remove the first item from Cost-based Query Optimization, or change the 
> font to strike through with a note that it's implemented in 3.2/4.2) here: 
> site/source/src/site/markdown/roadmap.md



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

Reply via email to