Qubole Reviews in June 2026: User Ratings, Pros & Cons

"Flexible but hard to debug"

What do you like best? Ability to execute queries against various databases (Hive, Presto, Spark, etc) What do you dislike? Error messages are often opaque and do not help with debugging. What problems are you solving with the product? What benefits have you realized? I generally used it to test ETL code.

"Client success Manager"

What do you like best about Qubole? easy to interpret data, digestible, good display What do you dislike about Qubole? slow load times, crashes, bugs, sometimes modules collapse and i cannot get them back What problems is Qubole solving and how is that benefiting you? pulling data from mobile marketing campaign and advertising products

"Good product with some quirks"

What do you like best about Qubole? Easy to get development code up-and-running on a cluster What do you dislike about Qubole? Notebooks UI is clunky and hard to use. Prefer Jupyter to Zeppelin What problems is Qubole solving and how is that benefiting you? Blazingly fast ETL

"Review of Qubole"

What do you like best? - I LOVE and now depend on the history section of qubole. I like that I don't have to think about potentially losing my old work. I also enjoy the share-ability of qubole. The sharing of links was definitely not intuitive in the beginning but now I really enjoy it. I like the the potential of notebooks. What do you dislike? Initial impression of qubole was honestly not that great because of the UI being not intuitive. The scheduling UI is still awful, I have to keep ...

"Terrible for query iterations, good for historical record"

What do you like best? You can find past queries and results pretty easily if they are within a recent timeframe, this is good for having a record of your work and being able to see what you ran if you are not good about keeping your own documentation of your projects. It is also nice that qubole when paired with a datalake allows for the use of partitions, so you may store lots of historical data and be able to query a smaller timeframe without it taking forever. This feature is not ...

"Flexible but hard to debug"

What do you like best about Qubole? Ability to execute queries against various databases (Hive, Presto, Spark, etc) What do you dislike about Qubole? Error messages are often opaque and do not help with debugging. What problems is Qubole solving and how is that benefiting you? I generally used it to test ETL code.

"Terrible for query iterations, good for historical record"

What do you like best about Qubole? You can find past queries and results pretty easily if they are within a recent timeframe, this is good for having a record of your work and being able to see what you ran if you are not good about keeping your own documentation of your projects. It is also nice that qubole when paired with a datalake allows for the use of partitions, so you may store lots of historical data and be able to query a smaller timeframe without it taking forever. This feature ...

"Great tool to see and play around with the data"

What do you like best about Qubole? It was very easy to use and figure around and find my way. Scripting and running queries was failry basic as a person who was completely new to cloud platform! What do you dislike about Qubole? When i would run my code overnight, The socket would crash and stop the code. It was a little annoying. What problems is Qubole solving and how is that benefiting you? I am trying to find patterns in available data to figure trends and performance in old cases.

"Good nto great"

What do you like best? Queries run quickly, detailed logs. Lots of advanced options when needed. What do you dislike? It requires high level of technical knowledge to work it. It's a busy interface. What problems are you solving with the product? What benefits have you realized? Running bigger queries

"Overall pretty smooth experience"

What do you like best? 1) every extensive set of functions and tools 2) Easy to setup and use 3) Spend is reasonable What do you dislike? Updating dependencies is a pain. Setup permission across different AWS account is a blocking issue of productivity. Recommendations to others considering the product: take it if you want less hassle on using spark or other big data tools. What problems are you solving with the product? What benefits have you realized? spark-related development hive table ...