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

ASF GitHub Bot commented on DRILL-7222:
---------------------------------------

kkhatua commented on issue #1779: DRILL-7222: Visualize estimated and actual 
row counts for a query
URL: https://github.com/apache/drill/pull/1779#issuecomment-491922589
 
 
   @arina-ielchiieva the feature allows an advanced user to compare estimated 
rows with the actual rowcounts for the query. Since the estimates are part of 
the Logical Plan Text , but in a scientific format, we need to parse it to 
represent it as a whole number with proper formatting (i.e. use of comma as a 
1000s separator). I used a Github snippet since that had the most references 
and usage, rather than look for a (possible?) Javascript library for this 
feature. 
   @sohami could you take a look as well?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Visualize estimated and actual row counts for a query
> -----------------------------------------------------
>
>                 Key: DRILL-7222
>                 URL: https://issues.apache.org/jira/browse/DRILL-7222
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Web Server
>    Affects Versions: 1.16.0
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>            Priority: Major
>              Labels: doc-impacting, user-experience
>             Fix For: 1.17.0
>
>
> With statistics in place, it would be useful to have the *estimated* rowcount 
> along side the *actual* rowcount query profile's operator overview.
> We can extract this from the Physical Plan section of the profile.



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

Reply via email to