Security Data Engineer at a pharma/biotech company with 5,001-10,000 employees
Real User
Top 20
2024-01-16T09:37:05Z
Jan 16, 2024
Dremio's interface is good, but it has a few limitations. I cannot do a lot of things with ANSI SQL or basic SQL. I cannot use the recursive common table expression (CTE) in Dremio because the support page says it's currently unsupported. The use case I am working on requires building trees and hierarchical structures. Most of the time, it requires complex nested data structures to be made simpler for end users. It would be good if Dremio could provide a way to create trees just like Oracle does using commands like CONNECT BY and NO CYCLE. You can use a few languages to simplify complicated JSON and XML. It would be very helpful if Dremio could provide a solution to simplify building trees and building meaningful data from complex data.
We've faced a challenge with integrating Dremio and Databricks, specifically regarding authentication. It is not shaking hands very easily. We had to set up two different VMs and execute them in a different manner and integrate them.
They have an automated tool for building SQL queries, so you don't need to know SQL. That interface works, but it could be more efficient in terms of the SQL generated from those things. It's going through some growing pains. There is so much value in tools like these for people with no SQL experience. Over time, Dermio will make these capabilities more accessible to users who aren't database people.
One of the areas of improvement is that a table does not break and shows errors. When the 23rd version was released, I had to contact Dermio customer support, and they suggested I update the database to run the table. Sometimes you face common errors like tables running strictly and taking time to run. I think Dermio can improve this part. An additional feature can be a feature where everyone can see the tables.
Dremio doesn't support the Delta connector. Dremio writes the IT support for Delta, but the support isn't great. There is definitely room for improvement. The community version lacks information or documentation. If you want to create a more dynamic scaling policy for your cluster, it's always a problem because you need an additional custom code to be sure that Dremio shuts down gracefully and does not get interrupted. The support of the Delta I/O connector could be improved because the current support is very basic and the performance isn't great.
Dremio is a data lake query engine tool that creates PDSs and VDSs on top of S3 buckets. It is used for managing simple ad-hoc queries and as a greater layer for ad-hoc queries. The most valuable features of Dremio include its ability to sit on top of any data storage, generate refresh reflections and create visuals, manage changes effectively through data lineage and data providence capabilities, use open-source, and address the problem of data transfer when working with large datasets. The...
Dremio's interface is good, but it has a few limitations. I cannot do a lot of things with ANSI SQL or basic SQL. I cannot use the recursive common table expression (CTE) in Dremio because the support page says it's currently unsupported. The use case I am working on requires building trees and hierarchical structures. Most of the time, it requires complex nested data structures to be made simpler for end users. It would be good if Dremio could provide a way to create trees just like Oracle does using commands like CONNECT BY and NO CYCLE. You can use a few languages to simplify complicated JSON and XML. It would be very helpful if Dremio could provide a solution to simplify building trees and building meaningful data from complex data.
We've faced a challenge with integrating Dremio and Databricks, specifically regarding authentication. It is not shaking hands very easily. We had to set up two different VMs and execute them in a different manner and integrate them.
They have an automated tool for building SQL queries, so you don't need to know SQL. That interface works, but it could be more efficient in terms of the SQL generated from those things. It's going through some growing pains. There is so much value in tools like these for people with no SQL experience. Over time, Dermio will make these capabilities more accessible to users who aren't database people.
One of the areas of improvement is that a table does not break and shows errors. When the 23rd version was released, I had to contact Dermio customer support, and they suggested I update the database to run the table. Sometimes you face common errors like tables running strictly and taking time to run. I think Dermio can improve this part. An additional feature can be a feature where everyone can see the tables.
Dremio doesn't support the Delta connector. Dremio writes the IT support for Delta, but the support isn't great. There is definitely room for improvement. The community version lacks information or documentation. If you want to create a more dynamic scaling policy for your cluster, it's always a problem because you need an additional custom code to be sure that Dremio shuts down gracefully and does not get interrupted. The support of the Delta I/O connector could be improved because the current support is very basic and the performance isn't great.