lhofhansl edited a comment on pull request #1189:
URL: https://github.com/apache/phoenix/pull/1189#issuecomment-813118325


   It turns out that for large sets Trino is actually performing the topN 
faster, even though it has to pull in all the data. This is due to the final 
client merge work that Phoenix is doing.
   So it's less important now to fix this here, since I'm limiting topN 
pushdown in Trino now. Still wrong, though.


-- 
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:
[email protected]


Reply via email to