snazy commented on PR #1589:
URL: https://github.com/apache/polaris/pull/1589#issuecomment-2890546526

   > > > @flyrain just to confirm, we are not planning to remove the individual 
distributions for server and tool, are we?
   > > 
   > > Good question. We will remove the individual distribution once the 
single binary distribution is ready. Their jar file will still be published 
individually though.
   > 
   > Are we sure about this? I assume that most people downloading the 
distribution would be interested in the server, not the tool. Imposing the 
combined distribution would mean for them to download a bunch of jars they 
don't need. And the opposite is true as well: if I only need the tool, why 
would I need to download 200Mb of server jars?
   
   I second @adutra's concern. Polaris server and admin-tool are separate 
things. You deploy the _server_ and let it run in k8s (or whatever). 
Bootstrapping happens rarely and is rather performed from an administrator's 
machine, whereas the servers run elsewhere. So server and admin-tool are run in 
very different ways.
   
   The admin-tool is (at best) just overhead in a server and increases the size 
of the image + container. Playing devil's advocate here, having the admin-tool 
executable accessible from the server gives easy access to the purge 
functionality. So if you're (in whatever way) able to instruct the Polaris 
server container to start an arbitrary executable, it could nuke existing data.


-- 
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-unsubscr...@polaris.apache.org

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

Reply via email to