-
Notifications
You must be signed in to change notification settings - Fork 28
refactor: let connectors pipeline-based #549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Except for |
> Use `confluence` as a unique identifier, as it is a builtin connector. | ||
## Update coco-server's config | ||
> **Note**: Starting from version **0.4.0**, the Confluence connector uses a **pipeline-based architecture** for better performance and flexibility. The `processor` configuration is required for the connector to work properly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0.4 ->0.9
queue: | ||
name: indexing_documents | ||
interval: 5m | ||
Starting from version **0.4.0**, the Confluence connector uses a **pipeline-based architecture** instead of the legacy scheduled task approach. This provides: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here
### Architecture Design | ||
|
||
#### Refactored Architecture | ||
#### Refactored Architecture (v0.4.0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0.4?
} | ||
``` | ||
|
||
#### Plugin Implementation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These AI genereated sections should be removed.
> **Note**: Starting from version **0.4.0**, the Gitea connector uses a **pipeline-based architecture** for better performance and flexibility. The `processor` configuration is required for the connector to work properly. | ||
Below is an example configuration for enabling the Gitea Connector in coco-server: | ||
## Pipeline Architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need to repeat these pipeline arch and common pipeline configurations
What does this PR do
feishu/lark
connector UI problemconnector.tpl
to the connector pipeline-based and path hierarchyStandards checklist