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

Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2022/10/24 09:34:00 UTC

[GitHub] [nifi] mark-bathori commented on pull request #6565: NIFI-10516: PutORC with Java 17 fails when using SNAPPY Compression

mark-bathori commented on PR #6565:
URL: https://github.com/apache/nifi/pull/6565#issuecomment-1288733132

   Thanks @exceptionfactory for the review.
   First I wanted to upgrade the snappy version but it already use the latest version. After that I also checked the `bootstrap.conf` solution just didn’t know if it can be expected from the user to know that enabling this jvm parameter is required to use certain processor, that’s why I thought that the NiFi runner should do this automatically based on the jdk version.
   I was looking the oracle’s documentation for the jdk8+ migration: https://docs.oracle.com/en/java/javase/16/migrate/migrating-jdk-8-later-jdk-releases.html
   
   However as you mentioned, modifying the JVM’s behaviour for one processor doesn't seems to be the best solution.
   
   My question is, should I add any specific comment in the bootstrap.conf that reflects to the PutOrc processor?


-- 
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: issues-unsubscribe@nifi.apache.org

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