You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "lokeshj1703 (via GitHub)" <gi...@apache.org> on 2023/03/23 06:19:21 UTC

[GitHub] [hudi] lokeshj1703 commented on pull request #8152: [HUDI-5740] Refactor Deltastreamer and schema providers to use HoodieConfig/ConfigProperty

lokeshj1703 commented on PR #8152:
URL: https://github.com/apache/hudi/pull/8152#issuecomment-1480657709

   > can you think how we can ensure we don't make any mistakes on config key (string) while doing this refactoring? for eg, 
   is it possible to compare config keys prior to this patch to config keys w/ this patch and ensure they match 1 on 1.
   
   I do not know of a good way to do this. Ideally if we had a hudi-site.xml or sth like that we could compare the new configs and the old configs. Is there a good way of achieving this?


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org