FAQ
Last updated
Last updated
This page contains some frequently asked questions. You can also check the details response under the subpages.
If your database is deployed in an internal network which is not accessible for external connection request, you can:
Use to export the database metadata file.
Create sqlflow job by .
Use version.
Check for more details.
Yes, you can delete your account. Check for how to do that.
Note: your data will be deleted with your account together
You can archive this using one of the following two approaches:
If you are using SQLFlow UI, change the SQLFlow UI settings and download the data lineage as CSV.
You can make REST api request to get the desired CSV data.
Try to check the metadata.json to see whether there's a ORA-01000 error.
Alter the open_cursors value to fix this issue .
No.
To facilitate team working with data lineage, one of the premium account privilege is to create shareable link for the data lineage result generated by SQLFlow.
However, in case of the expiration of your premium account, the link used for sharing will expire together with your account even if they were generated before the account's expiration. So please remember to renew in time if these links are still being used.
There are various possible reasons to cause this issue:
Poor network quality
Cross-domain issue between the server and the client
Wrong Nginx config
Certificate problem for HTTPS
Insufficient server disk space
...
Yon can check your browser console to see the error details (F12 for chrome)
Please contact us and send us the error details to support@gudusoft.com. Our support team will help you to solve out this issue.
Windows users may have following issue when trying to start the sqlflow backend:
This might be due to the lack of memory. SQLFlow needs at least 32G RAM available. Please check if you have enough RAM available.
To assign more memory to SQLFlow, please edit the sqlservice.bat file under sqlflow\backend\bin, add the following line of code after line 16:
set heapsize=4G
The more RAM you assign to SQLFlow, the more complex SQL it would be able to deal with and your host server should have enough RAM to assign.
If you have installed SQLFlow On-Premise but when going to your local SQLFlow UI and see this error:
It is probably due to the lack of disk space. You can confirm that by checking the log files under
You need to clean your disk and prepare more disk space to launch the SQLFlow backend.
If your network is protected by some email protectors, you may get the dismatch license failure.
The root cause of this issue is that some email system could mistakenly rewrite the license file when we send it to you via email:
Our license file is a text file and some network protectors will trat the license file like part of the email body for scanning purposes. Please reach out to us if you find the license file you receive does not work.
If you need to check the detailed local Swagger Doc (http://<yourIp>/api/gspLive_backend/doc.html?lang=en), please add one extra config flag in the gspLive.sh/gspLive.bat:
Add --swagger.enable=true to the execution command nohup to turn on the Swagger Doc.
In case the SQLFlow jobs end failure for any memory issues, you may try the following approaches:
Assigning more memory to SQLFlow
Restricting memory usage
Update the gudu_sqlflow.conf file:
The smaller above values ​​are, the slower the job execution will be.
Enable parallel mode
Turning on the parallel mode makes each SQL statement be executed separately which reduces memory usage.
Check to get more details.
Check to get more details.
The local API doc is turned off by default for the security reasons and the API doc is available at:
Please check this page for the detail:
