Open bruno-castro-precision opened 2 months ago
If you are interested in working on this issue, please provide go ahead and provide PR for that. We'd be happy to review it and merge it. If this is the first time you are contributing a Pull Request to Cube, please check our contribution guidelines. You can also post any questions while contributing in the #contributors channel in the Cube Slack.
Hi @bruno-castro-precision 👋
Thanks for raising this! Would you like to contribute these changes yourself? In that case, these instructions might be helpful: https://github.com/cube-js/cube/blob/master/CONTRIBUTING.md#contributing-database-drivers
Dremio has evolved on past years, adopting project and catalog perspectives such as a lakehouse platform. This create a need for a new connector in cube that help to connect to Dremio Cloud, using the new and improved API's.
Dremio Cloud has a different documentation over Dremio Core and concepts such as
username
anddatabase
are not used in this solution. Also some ports are a bit different if compared to Dremio Core.Describe the solution you'd like There is a need for changing the Dremio Driver and Dremio Query components to adjust to new dremio capabilities. On older versions of Dremio Core there was a
username
that was used to authenticate on APIs. This information does not exists for Dremio Cloud, and the connection to Dremio SQL API and Dremio Jobs API is authenticated by project id and PAT.Here is a snippet of code using python language for the newest jobs API:
As you can see, the only keys used are
project_id
andpersonal_access_token
.Describe alternatives you've considered The most interesting way to fix this problem is updating the code related to driver and query components adapting it to the newest docuementation of Dremio Cloud.
Additional context [Older API Documentation - Currently used in Cube Cloud]() Newest API Documentation for Dremio Cloud