You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. In regarding of proof of concept, Is there a way to test the AI API against our self-hosted cube server ?
I tried to connect to our host with the cubejs-api/v1/ai/query/completions, it gives 404
I also tried using cube cloud via following:
Using my git account and, select our cube repo, added some ENV VARs under setting, But can't make it connect to either my local cubejs server or our dev environment cubejs server, as it keeps failing with:
I guess it is due to the fact that it doesn't connect to our cube server, instead, it connects the one created by cube cloud:
Proof of this can be found in the running log:
Which is different from the version we are using Cube API server (1.1.18).
We really would like to invest on this if this API looks promising with our cube data and query requirement
2. If we decide to use a different LLM, e.g., OpenAI, train it with our own cube meta data, would it work ? any guidance on this ?
The text was updated successfully, but these errors were encountered:
Problem
1. In regarding of proof of concept, Is there a way to test the AI API against our self-hosted cube server ?
I tried to connect to our host with the

cubejs-api/v1/ai/query/completions
, it gives404
I also tried using cube cloud via following:

Using my git account and, select our cube repo, added some ENV VARs under

setting
, But can't make it connect to either my local cubejs server or our dev environment cubejs server, as it keeps failing with:I guess it is due to the fact that it doesn't connect to our cube server, instead, it connects the one created by cube cloud:
Proof of this can be found in the running log:
Which is different from the version we are using
Cube API server (1.1.18)
.We really would like to invest on this if this API looks promising with our cube data and query requirement
2. If we decide to use a different LLM, e.g., OpenAI, train it with our own cube meta data, would it work ? any guidance on this ?
The text was updated successfully, but these errors were encountered: