...
inQuiry BB has multiple components like assessment-service and Flink jobs spread across multiple GitHub repositories. The objective is to decouple the inQuiry specific code from KP (Knowledge-Platform) Git Repos and bring it under the inQuiry BB space in GitHub.
Current Code Structure:
Expand | ||
---|---|---|
| ||
/knowledge-platform/assessment-api ( /assessment-api/ assessment-service ( /assessment-api/ assessment-actors ( /assessment-api/ qs-hierarchy-manager ( /knowledge-platform/ontology-engine ( /ontology-engine/graph-common /ontology-engine/graph-core_2.11 /ontology-engine/graph-dac-api /ontology-engine/graph-engine_2.11 /ontology-engine/parseq /knowledge-platform/platform-core ( /platform-core/actor-core /ontology-engine/schema-validator /ontology-engine/platform-telemetry /ontology-engine/platform-common /ontology-engine/platform-common /ontology-engine/cassandra-connector /ontology-engine/kafka-client /knowledge-platform/platform-modules ( /platform-modules/import-manager /platform-modules/mimetype-manager /platform-modules/url-manager |
Expand | ||
---|---|---|
| ||
/knowledge-platform-jobs/jobs-core ( /knowledge-platform-jobs/auto-creator-v2 ( /knowledge-platform-jobs/publish-pipeline /publish-pipeline/publish-core ( /publish-pipeline/questionset-publish ( |
Dependency with Knowlg BB:
Currently, all common modules are part of knowlg BB and are tightly coupled with knowlg/inQuiry services/jobs.
inQuiry uses below api’s
...