You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Rajeshbabu Chintaguntla (JIRA)" <ji...@apache.org> on 2018/02/08 10:02:00 UTC

[jira] [Created] (PHOENIX-4590) Reduce log level in BaseResultIterators#getStatsForParallelizationProp when parent table not found

Rajeshbabu Chintaguntla created PHOENIX-4590:
------------------------------------------------

             Summary: 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
             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)