SEZ9 commented on issue #9866:
URL: https://github.com/apache/seatunnel/issues/9866#issuecomment-5140457515
Thanks for the report. The stack trace shows ShardedSplitStrategy.split
(line 87) reading a 'key' sub-document from the config database metadata that
is absent for your cluster. Could you run
`db.getSiblingDB('config').collections.find({_id:
'<yourDb>.<yourCollection>'})` and share the (sanitized) output so we can see
what fields are present?
Please also share your (sanitized) SeaTunnel job config for the MongoDB-CDC
source, confirm the exact MongoDB version (4.4.x), and whether the target
collection is actually sharded. If the collection is unsharded or its
config.collections entry lacks the shard key, the split strategy may need a
fallback to the sample/single split strategy instead of failing.
As a possible workaround while this is investigated, verify the connecting
user has read access to the `config` database and that the collection's entry
in `config.collections` is not marked `dropped: true` (stale metadata from a
dropped/recreated collection can cause the 'key' field to be missing on MongoDB
4.4).
<!-- streview-comment:11 -->
--
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]
