Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there any development progress of add a connector for Metabase? #4404

Closed
Lin-Aurora opened this issue Apr 18, 2022 · 6 comments
Closed

Is there any development progress of add a connector for Metabase? #4404

Lin-Aurora opened this issue Apr 18, 2022 · 6 comments
Labels
question The issue is a question. Please use Stack Overflow for questions.

Comments

@Lin-Aurora
Copy link

Hello,
I would like to know whether add a connector for metabase is in development progress?
Thanks!

@Lin-Aurora Lin-Aurora added the question The issue is a question. Please use Stack Overflow for questions. label Apr 18, 2022
@ovr
Copy link
Member

ovr commented Apr 22, 2022

Hello @Lin-Aurora ,

It worked with some limitations with SQL API via MySQL protocol. Right now we are working on two big things for SQL API which should unblock it: A new query engine & PostgreSQL protocol support.

Thanks

@Lin-Aurora
Copy link
Author

Thanks for your reply @ovr ,
Does this mean Metabase can only use REST API connections at present?
I refer to the metabase-cubejs-driver

@abdel-87
Copy link

abdel-87 commented Apr 23, 2022

@ovr why did Cubejs chose to mimic some SQL protocol instead of building connectors that generate Native Cube JSON queries instead of SQL? IMO it would be much cleaner, then trying to mimic a SQL protocol

@abdel-87
Copy link

By mimicing a SQL protocol, Cube JS would retrieve the SQL from the BI Tool, translate it to JSON and then translating it back to SQL? That naturally sounds as a big unnecessary workaround.

In the end Cube will anyway need to create and update all supported connectors, based on the updates of BI tools.

@paveltiunov
Copy link
Member

@abdel-87 This is a great question! The reason for it is we're aiming for support of most downstream data tools out there. There're hundreds of those if not thousands. It'd be not feasible for us to implement integration with each of those however supporting a subset of Postgres Analytical SQL is doable and it can be done in a centralized manner for all tools altogether.

@paveltiunov
Copy link
Member

Implementation progress is available here #3906

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question The issue is a question. Please use Stack Overflow for questions.
Projects
None yet
Development

No branches or pull requests

4 participants