FAQ
Usage Notes
This page collects common questions and answers from the community group. If you encounter an uncovered issue or discover a bug, you are welcome to submit an Issue. We will handle it promptly and continue improving the documentation.
Q: What is qData? Which scenarios is it suitable for?
**A: ** qData is an open-source, one-stop data middle-platform. It supports the full chain from data collection, governance, and development to services and visualization. It is suitable for enterprise scenarios such as data standardization construction, multi-system data integration, and unified data service output.
Q: What types of data sources does qData support?
**A: ** qData currently supports access to mainstream relational databases such as MySQL, Oracle, Dameng, and PostgreSQL, files such as Excel and CSV, APIs such as HTTP, and message queues such as Kafka and RabbitMQ.
Q: How does qData provide data services?
**A: ** The platform supports one-click encapsulation of data assets as API interfaces. It can configure permission control and data masking, and automatically records call logs so external systems can access data in a unified way.
Q: Can data development tasks be customized?
**A: ** Yes. qData supports task development through SQL scripts and provides a visual ETL process design tool to meet data processing needs at different levels.
Q: What is the difference between the commercial edition and the open-source edition?
**A: ** The open-source edition covers core functions and is suitable for evaluation and lightweight use. The commercial edition provides richer capabilities, supports more complex scheduling, monitoring, data modeling, security control, and more, and has been maturely implemented in multiple government and enterprise projects.
Q: What environments can qData be deployed in?
**A: ** qData can be deployed on Linux, Windows, and macOS. Docker containerized deployment is recommended, and physical deployment is also supported. Basic components such as JDK 1.8+, MySQL, and Redis must be installed in advance.
Q: Does it support multi-tenant or multi-project team collaboration?
**A: ** Yes. qData supports a workspace mechanism, which can assign tasks and resources to different project groups for management and enable front-office/back-office style collaboration.
Q: What should I do if task submission fails? How do I view logs?
**A: ** The platform has built-in task runtime logs and an error prompt interface. You can view log output in the task details to locate failure causes, such as SQL errors, unreachable data sources, abnormal permission configuration, and so on.
Q: Is there a user permission control mechanism?
**A: ** qData supports permission control for users, roles, menus, APIs, and more. It also supports fine-grained data access permission configuration to ensure secure and compliant data usage.
Q: How can I participate in co-building or submit issues?
**A: ** You can submit Issues and PRs through the GitHub or Gitee repository. You are also welcome to join our community group to participate in discussions and co-building.
Q: Are the code on Gitee and GitHub and the functions after local deployment the same as the demo environment? Thanks!
**A: ** Yes. The code in the open-source repository is consistent with the demo environment in functionality. After local deployment, you can experience the complete functions. If there are environment differences or issues, you are welcome to provide feedback through Issues.
Q: Are some functions still unfinished? I saw some modules marked as "in development".
**A: ** Yes. qData is still being continuously iterated. Some functions are under development and optimization, and will be released gradually in the open-source edition. Please stay tuned.
Q: I cannot find some common functions in the system. Have they not been implemented yet?
**A: ** Some functions may still be under development, or may not be in the current planning scope for the moment. If you have good suggestions or actual requirements, you are very welcome to tell us through Submit Requirements. We will evaluate them carefully and give priority to features with general value in future versions.