- Simplifies job submission by providing an intuitive command-line interface
- Automates monitoring with real-time status updates and progress tracking
- Provides comprehensive logging with automatic log retrieval
- Supports configuration management through YAML files for reusable job templates
- Integrates seamlessly with Spark History Server and YuniKorn queue management
- You enter an input through the command-line tool or a YAML file.
- Kyuubi-submit merges that input with its configuration.
- The request goes to the Kyuubi REST API.
- Kyuubi submits the job to Spark on Kubernetes.
- You monitor the run and review the logs.
kyuubi-submit.py vs nx1 kyuubi
The core difference betweenkyuubi-submit.py and the nx1 kyuubi command is the execution environment and
the resources it can access.
kyuubi-submit.pyruns outside the cluster and interacts with Kyuubi remotely through the REST API. It requires an external network access to the Kyuubi server running in NexusOne, and handles the uploading of Kyuubi resources, such as JARs, files, or data from your local machine to the cluster.nx1 kyuubiruns inside the Kubernetes cluster, specifically within the NexusOne JupyterHub app. It communicates with Kyuubi over internal cluster networking and assumes that all Kyuubi resources are already accessible within the cluster.
Additional resources
- For more information about Apache Kyuubi in NexusOne, refer to Kyuubi in NexusOne.
- For more information about the
nx1 kyuubisupported flags and how to use them, refer to the nx1 command line reference page.