[Hive] Use SQL to limit fetch size is not working
See original GitHub issueI am running Hive on Spark.
I need to use hive with option hive.fetch.task.conversion=none
. So all SQL commands will run within an Apache Spark application. Howerver, the Data Editor will run SELECT * FROM [table]
without LIMIT
clause and this take a long time to run this job.
Therefore, I have enabled Use SQL to limit fetch size
in Data Editor setting but the SELECT *
query still didn’t append LIMIT
clause. I think this is a bug of Dbeaver.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
HIVE: How does 'LIMIT' on 'SELECT * from' work under-the ...
Under the hood a "SELECT" in a hive issues a FETCH task instead of spawing a mapreduce task. Think of it like a...
Read more >hive select query with limit - Cloudera Community - 234636
I am trying to fetch results data stored in hive orc table , but when I run the query it gives results fast...
Read more >PI41136: HIVE JDBC ARRAY FETCH SIZE NEEDS ... - IBM
The java.sql.statement.setFetchSize parameter is fixed at 50 and is creating a performance bottle neck. Customer wants the.
Read more >Hive connector — Trino 403 Documentation
This works for very simple Hive views, but can lead to problems for more complex queries. For example, if a HiveQL function has...
Read more >error in fetching data from Hive table - SAS Communities
I am trying to read into SAS from a Hadoop Apache Hive table and facing ... and the use of DBSASTYPE to limit...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thanks for the bug report and clarification
verified