apache/seatunnel

PR-I: Add dedicated knowledge sources

Open

#10,921 opened on May 19, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (1,432 forks)batch import
featurehelp wanted

Repository metrics

Stars
 (6,897 stars)
PR merge metrics
 (Avg merge 19d 8h) (124 merged PRs in 30d)

Description

Scope

Add dedicated knowledge sources after the unified document contract is stable.

Candidate sources include Confluence, Google Drive, and SharePoint.

Deliverables

  • Add Confluence source proposal.
  • Add Google Drive source proposal.
  • Add SharePoint source proposal.
  • Ensure each source follows the unified document contract.
  • Prefer source-native version as DocumentHash priority 1 where available.

Acceptance Criteria

  • Dedicated sources emit or project the standard Knowledge Sync metadata.
  • Connector-specific logic stays inside connector modules.
  • Source-native versioning is used when available.
  • Sources integrate with the existing identity, parse, chunk, embedding, and lifecycle sink path.

Contributor guide

Research direction
Study the unified document contract and existing connectors. Implement a new connector module for each source (Confluence, Google Drive, SharePoint) following the same pattern. Use source native versioning as DocumentHash priority 1.
Tech stack
java
Domain
backenddata
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60