SEZ9 commented on issue #9866:
URL: https://github.com/apache/seatunnel/issues/9866#issuecomment-5155771789
Thanks for the report. Could you share your (sanitized) job config for the
MongoDB-CDC source, and the output of
`db.getSiblingDB('config').collections.find({_id: '<db>.<collection>'})` and a
sample from `config.chunks` for that namespace? ShardedSplitStrategy reads the
shard key ('key' field) from the config metadata, so we need to see what those
documents actually look like in your cluster.
Please confirm whether the collection being synced is actually sharded, and
whether it was ever dropped/resharded (which can leave stale or schema-variant
entries in config.collections/config.chunks). Also confirm the user connects
via mongos with read access to the 'config' database.
As a possible workaround while this is investigated, you can try setting the
split strategy away from sharded splitting (e.g. use the sample/split-vector
based strategy if supported by your setup) to unblock the snapshot phase. If it
works, that would help confirm the issue is isolated to ShardedSplitStrategy's
metadata parsing.
<!-- streview-comment:34 -->
--
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]
