adoroszlai commented on pull request #2856: URL: https://github.com/apache/ozone/pull/2856#issuecomment-981547768
> The NPE occurs only due to configuration. MiniOzoneCluster has many config keys set by default. That is the reason error did not appear before. I can create a new jira for testing functionality with minimum configurations? I can reproduce the NPE by explicitly setting these config keys to `null` in the config being passed to MiniOzoneCluster, e.g. in `TestOzoneFileSystem`. So I think adding a test case (in another test class) should be simple. I was looking for some config and steps that would trigger the NPE in a real/pseudo cluster (e.g. Docker Compose-based). -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
