eye-gu commented on issue #18350: URL: https://github.com/apache/dolphinscheduler/issues/18350#issuecomment-4834524293
@zhongjiajie Thanks for the feedback. 1. The primary use case is read-only consumption. The intended scenario is that users modify their shell/SQL scripts through their own CI pipeline, and DolphinScheduler consumes the repository as read-only. In this mode there's no write path in DS at all. 2. Writes (when enabled) go through the REST API regardless of cache and conflict. When writes are performed in DS (create/update/delete), they always go through the Git REST API — whether or not caching is enabled. The result is deterministic: either success or failure. A "conflict" (e.g. HTTP 409 when the blob SHA has changed, SHA can be seen as an optimistic lock) is just one kind of failure, handled by standard retry (re-GET the SHA, re-PUT). It does not introduce complex conflict-handling logic. -- 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]
