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

Rajeshbabu Chintaguntla commented on PHOENIX-4590:
--------------------------------------------------

ping [~samarthjain] [~jamestaylor].

> Reduce log level in BaseResultIterators#getStatsForParallelizationProp when 
> parent table not found
> --------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4590
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4590
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>            Priority: Minor
>             Fix For: 4.14.0
>
>
> Currently when we check whether to use stats for parallelisation or not we 
> check with parent table   if the index table doesn't have stats. In this case 
> if parent table not present at connection meta. When we directly scan(which 
> is not a valid case but sometimes we may scan index directly) then we see 
> this log all the time. I think we can reduce the log level to debug or trace 
> as usually we can have parent table in the connection meta so it should be 
> very rare.
> {noformat}
>             } catch (TableNotFoundException e) {
>                 logger.warn("Unable to find parent table \"" + 
> parentTableName + "\" of table \""
>                         + table.getName().getString()
>                         + "\" to determine USE_STATS_FOR_PARALLELIZATION",
>                     e);
>             }
> {noformat}



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

Reply via email to