Frequently Asked Questions

Usage Instructions

This page compiles common questions and answers from community discussions. If you encounter any issues not covered here or discover a bug, please feel free to submit an Issue. We will address it promptly and continuously improve the platform.

❓ What is qData, and what scenarios is it suitable for?

Answer: qData is an open-source, all-in-one data mid-end platform that supports a complete data workflow including data ingestion, governance, development, service delivery, and visualization. It is ideal for enterprise-level scenarios such as standardized data construction, integration of multi-system data, and unified data service provisioning.

❓ What types of data sources does qData support?

Answer: Currently, qData supports mainstream relational databases (e.g., MySQL, Oracle, DM (Dameng), PostgreSQL), files (e.g., Excel, CSV), APIs (HTTP), and message queues (e.g., Kafka, RabbitMQ).

❓ How does qData provide data services?

Answer: The platform allows data assets to be packaged into API interfaces with one click. It supports configurable access control, data masking, and automatically logs API calls, enabling unified and secure data access for external systems.

❓ Can I customize data development tasks?

Answer: Yes. qData supports task development via SQL scripts and provides a visual ETL workflow design tool to meet diverse data processing needs.

❓ What is the difference between the commercial and open-source versions?

Answer: The open-source version includes core functionalities and is suitable for evaluation and light usage. The commercial version offers richer features, including advanced scheduling, monitoring, data modeling, and enhanced security controls, and has been successfully deployed in multiple government and enterprise projects.

❓ On what environments can qData be deployed?

Answer: qData can be deployed on Linux, Windows, and macOS. Containerized deployment using Docker is recommended. It also supports physical machine deployment. Prerequisites include pre-installed components such as JDK 1.8+, MySQL, and Redis.

❓ Does qData support multi-tenancy or multi-project team collaboration?

Answer: Yes. qData supports a "workspace" mechanism, allowing tasks and resources to be assigned to different project teams, enabling front-end and back-end collaborative workflows.

❓ What should I do if a task submission fails? How can I view logs?

Answer: The platform includes built-in task execution logs and error messages. You can view log outputs and error details in the task details interface to identify failure causes, such as SQL errors, unreachable data sources, or permission configuration issues.

❓ Is there a user permission control mechanism?

Answer: Yes. qData supports comprehensive permission controls for users, roles, menus, and APIs, including fine-grained data access permissions to ensure secure and compliant data usage.

❓ How can I contribute or report issues?

Answer: You can submit Issues or Pull Requests (PRs) via our GitHub or Gitee repositories. You are also welcome to join our discussion groups to participate in community development.

❓ Are the features of the code on Gitee and GitHub the same as the demo environment after local deployment? Thanks!

Answer: Yes, the code in the open-source repositories matches the functionality of the demo environment. After local deployment, you can experience the full feature set. If you encounter any discrepancies or issues, please report them via an Issue.

❓ Are some features still under development? I noticed some modules are labeled as "In Development."

Answer: Yes, qData is currently under continuous iteration. Some features are still being developed and optimized, and will be gradually released in future open-source versions. Stay tuned!

❓ I can't seem to find some common features in the system. Are they not implemented yet?

Answer: Some features might still be under development, or may not be included in the current roadmap. If you have suggestions or specific requirements, we warmly welcome you to submit them via Feature Request. We will carefully evaluate them and prioritize features with broad applicability for future releases.