SEZ9 commented on issue #11007:
URL: https://github.com/apache/seatunnel/issues/11007#issuecomment-6538007082

   @erica1111-prog — thanks for posting the scope note, that covers most of 
what was asked. A few things before this slice is confirmed here:
   
   1. **Commit inspected**: "current latest `dev`" isn't trackable — please 
post the exact `dev` commit SHA you inspected so the slice can be pinned the 
same way as the others.
   2. **Mutual-exclusion rule**: the description reads as 
"`KEY_MEASUREMENT_RULE` bundled with optional `KEY_MEASUREMENT_FIELD` vs. 
standalone `KEY_MEASUREMENT_RULE`", which has `KEY_MEASUREMENT_RULE` on both 
sides. Could you restate precisely which options are in each exclusive group as 
you intend to encode them in `optionRule()`?
   3. **Test coverage**: `testSinkOptionRulesSuccess`, 
`testSinkOptionRuleMissingRequired` and `testSinkOptionRuleMutualExclusion` 
look good. The earlier ask also mentioned blank / padded values for the 
required options (`URL`, `DATABASES`) — please say whether you plan to cover 
those in `InfluxDBFactoryTest` or whether you're deliberately keeping them out 
of this slice (either is fine, just make it explicit).
   4. **Docs**: agreed that if EN/ZH already list these options with matching 
required/optional status, no contract change is needed — please just 
double-check the required/optional markers match what `optionRule()` will 
enforce.
   5. Your comment appears to be cut off at "zero runti" — please repost the 
last part so the full note is on record.
   
   Once those are in, the `connector-influxdb` sink slice can be confirmed here 
(no assignment change yet). Please keep the change limited to 
`InfluxDBSinkFactory` and `InfluxDBFactoryTest`, as you described.
   
   <!-- streview-comment:2159 -->


-- 
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]

Reply via email to