DanielLeens commented on issue #9813: URL: https://github.com/apache/seatunnel/issues/9813#issuecomment-4736892472
Thanks for raising this. I checked the current tree and do not see a native NebulaGraph connector in SeaTunnel today, so this is a real feature gap rather than a configuration problem. The main thing that still needs to be tightened is scope. As written, this bundles both read and write support, graph-model mapping, and broad version compatibility into one issue. That is probably too large for a first implementation if we want the work to stay claimable and reviewable. A better first milestone would be to clarify: 1. whether the first delivery is source-only, sink-only, or both 2. which NebulaGraph objects must be supported first (`vertex`, `edge`, or a narrower subset) 3. which stable client/API path the connector should use 4. how NebulaGraph 3.x compatibility will be validated If someone wants to contribute this, a narrower first slice will make review much easier. Source-only or sink-only is usually a better starting point than trying to land both directions in one go. -- 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]
