No such file or directory: 'blazingsql-orchestrator': 'blazingsql-orchestrator'

[blazingdb]

No such file or directory: 'blazingsql-orchestrator': 'blazingsql-orchestrator'

[bordie]

FWIW - I am trying the conda install and do not have this issue. I show the same versions of all blazing* as above.

[ivenzor]

Thanks for the reply.
These are my steps:

source /home/ec2-user/anaconda3/etc/profile.d/conda.sh
sudo mkdir /blazingsql
sudo chown ec2-user /blazingsql
conda create --name rapids_blazing python=3.7
conda activate rapids_blazing

conda install -c rapidsai -c nvidia -c numba -c conda-forge -c anaconda -c rapidsai/label/xgboost -c blazingsql/label/cuda10.0 -c blazingsql blazingsql-calcite blazingsql-orchestrator blazingsql-ral blazingsql-python "rapidsai/label/xgboost::xgboost=>0.9" cudf=0.9 cuml=0.9 cugraph=0.9 dask-cudf=0.9 python=3.7 ipykernel boto3 "PyYAML>=3.10,<4.3" "urllib3<1.25,>=1.21" "idna<2.8,>=2.5" boto s3fs dask anaconda::cudatoolkit=10.0

pip install flatbuffers sagemaker
ipython kernel install --user --name=rapids_blazing

After that I go to Jupyter Lab and open the notebook. I import the packages but got the error when I try to bc = BlazingContext()

[felipeblazing]

Is the notebook running inside of the conda environment rapids_blazing?

[ivenzor]

Jupyter Lab is already running in other env before I create rapids_blazing env. After rapids+blazingsql intallation I register the rapids_blazing kernel. Once in JupyterLab I change the kernel to rapids_blazing and start using everything I installed.

[ivenzor]

I think I have found the issue. It was a silly thing. I will test more and will let you know.

[aucahuasi]

@ivenzor thanks for reporting this, I think the issue is that you need to run BlazingSQL and Jupyter with the same conda env.

[ivenzor]

The fix was just to specify the kernel to be conda_rapids_blazing instead of rapids_blazing.