You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2018/12/18 00:23:08 UTC

[GitHub] milleruntime opened a new issue #834: Init with Crypto enabled should throw error

milleruntime opened a new issue #834: Init with Crypto enabled should throw error
URL: https://github.com/apache/accumulo/issues/834
 
 
   I am currently seeing this when running uno with the encryption plugin.  The package name is out of date for the instance.crypto.service property but no error gets printed in the log.  Everything intializes just fine but crypto is off.  I think initialize should fail if the configured crypto class is not found (aka your files are not being encrypted but you might think they are).
   
   I think this has something to do with the latest changes in CryptoServiceFactory.  An error is being thrown when using ClassloaderType.JAVA but not ClassloaderType.ACCUMULO.  Initialize uses ClassloaderType.ACCUMULO.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services