exceptionfactory commented on PR #9452: URL: https://github.com/apache/nifi/pull/9452#issuecomment-2441373223
Thanks for the feedback @joewitt, @arpadboda, and @mark-bathori. Regarding removing a component versus removing a NAR, it is important to note that the `HiveCatalogService` is a separate Controller Service, distinct from the other implementations. Although the existing module layout placed this service together with the others, it could be repackaged in a separate NAR bundle for better isolation from the other implementations. From that perspective, I'm not quite following the concern regarding the complexity of removing a component versus removing a NAR. Regarding the timing, I realize that Hive 4 is fairly new and that the decision to declare Hive 3 EOL is also fairly recent. As we have an opportunity to provide a cleaner baseline for NiFi 2.0, that is the reason for raising this right now. We could revisit this after the NiFi 2.0 release, and consider this an acceptable change given that Hive 3 is no longer receiving updates. Anyone who needs Hive 3 Catalog support could continue to use the 2.0.0-M4 release version, with the understanding that it is not supported from either NiFi or Hive. I think there is actually more confusion from releasing the current version, because it implies support from the NiFi project, which we are not able to provide, given that Hive 3 is EOL. @mark-bathori Do you have a rough idea of what would be involved in implementing support for Hive 4? @arpadboda For clarification, if the current Hive 3 version of `HiveCatalogService` were in its own NAR, would you be in favor of removing it? I could see an intermediate change to first decouple that implementation to its own NAR, and then removing it if that is your primary concern. -- 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]
