DanielCarter-stack commented on issue #10358: URL: https://github.com/apache/seatunnel/issues/10358#issuecomment-3764260414
<!-- code-pr-reviewer --> Thanks for the feature request. I've verified that a HubSpot connector does not currently exist in the repository (search for `HubSpot|hubspot` returned no results). This request is reasonable given SeaTunnel's existing HTTP connector framework: - `/seatunnel-connectors-v2/connector-http/connector-http-base/` - Provides `HttpSource`/`HttpSourceReader` with retry, JSON parsing, and cursor-based pagination that aligns with HubSpot API v3 - `/seatunnel-connectors-v2/connector-http/connector-http-jira/` - Reference implementation for SaaS API connectors with custom auth For a quick workaround, you can use the generic HTTP connector directly. For a dedicated connector, the `connector-http-jira` module shows the pattern: inherit `HttpSourceFactory`, add HubSpot-specific authentication (private app/OAuth), and extend `HttpSource`. Two clarifications needed to finalize the design: 1. The issue mentions "multi-object configuration" and "CDC mode," but current HTTP connectors follow a single-request architecture. Should the implementation support multiple parallel `Source` instances or require a new design? 2. HubSpot's cursor pagination uses `paging.next.after`—does this map directly to `HttpPaginationType.CURSOR`, or are customizations needed? Labeling as `help wanted` for community contribution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
