That's quite strange. Because execution log shows exactly the same query that DBeaver tries to execute.
And I can't reproduce this issue because I don't have an access to a live Vertica server.
DBeaver uses LIMIT modifier in all SELECT statements which do not have LIMIT inside. In some cases it can lead to errors.
You can disable implicit LIMITs: turn off checkbox in Preferences->Common->Result Sets->Queries->"Use SQL to limit fetch size".