[ https://issues.apache.org/jira/browse/IMPALA-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Tauber-Marshall resolved IMPALA-6821. -------------------------------------------- Resolution: Fixed > Push down limits into Kudu > -------------------------- > > Key: IMPALA-6821 > URL: https://issues.apache.org/jira/browse/IMPALA-6821 > Project: IMPALA > Issue Type: Improvement > Components: Backend > Reporter: Andrew Wong > Assignee: Thomas Tauber-Marshall > Priority: Major > Labels: kudu, perf > > The progress made in KUDU-16 introduced a way to impose limits on Kudu > scanners, potentially reducing the number of RPCs sent per scan, CPU used for > scanner evaluation on the tablet server, etc. It would be nice if Impala > could make use of this new behavior. > I put up an admittedly clunky [patch|https://gerrit.cloudera.org/c/9923/] > that implements limits on a per-token basis. I'm no Impala expert, so there > may be an API missing in Kudu that would make Impala's life easier in > implementing this. Maybe it's as easy as adjusting the limit after > re-hydrating the token into a scanner. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org