nchammas commented on PR #57313: URL: https://github.com/apache/spark/pull/57313#issuecomment-5040186225
I think there is a misunderstanding of what I am proposing. Let me try to clear that up before I address some of your other concerns. > So not like ./bin/spark (this can't be used when you pip install) I think this is the source of some confusion. My point was to show the commands that would be supported, not the executable's path. I am working with a prototype and currently have the executable under `bin/`. My goal, however, is to place `spark` on the user's path so they can call it just like they call the current executables like `spark-sql`, `spark-submit`, etc. I will edit the PR description to clear up this point of confusion. > I want the cli to be part of pyspark. Could you elaborate on why you want the CLI to be part of PySpark? To me, the CLI is independent of any language runtime. Users use it to manage various servers, submit applications, and launch shells. There is nothing about it that seems like it should be tied specifically to PySpark. -- 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]
