-
Notifications
You must be signed in to change notification settings - Fork 11
Desktop Install
sudo apt install python3 python3-pip openjdk-8-jre xdg-utils
pip3 install setuptools wheel
if openjdk-8-jre
is not available, you can use openjdk-11-jre
For best results install Java JDK-8. If you have a later JDK installed, you'll get an IllegalAccessException warning on startup, and Apache Arrow support will not work.
brew install python
pip3 install setuptools wheel
sudo port install py37-pip
pip3 install setuptools wheel
Enable Windows Subsystem for Linux
sudo apt install python3 openjdk-8-jre-headless
ln -s /usr/bin/python3 /usr/local/bin/python
curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python get-pip.py
Using coursier
coursier install vizier --channel https://vizierdb.info/coursier.json
You may need to add your user bin directory (typically ~/.local/bin
) to your PATH
environment variable
wget https://maven.mimirdb.info/info/vizierdb/vizier
chmod +x vizier
if [ -d /usr/local/bin ] ; then sudo cp vizier /usr/local/bin/vizier; else sudo cp vizier /usr/bin/vizier; fi
(The last line installs vizier into /usr/local/bin
if it exists and /usr/bin
otherwise. Adjust the last line as needed if you prefer your binaries elsewhere)
vizier
coursier uninstall vizier
rm -r ~/.cache/coursier
Spark, which we use for most data processing, has only limited support for Java JRE 9 or later. Vizier is generally usable on Java9+, with a few exceptions (Tested on Java 11):
- Apache Arrow support in Python (i.e., Pandas/Vizier integration via
vizierdb.get_dataframe
) does not work in Java 9+ - Running on a v9+ JVM, Vizier dumps out an
IllegalArgumentException
. This is just a warning, you can continue to use Vizier normally.
If necessary, you can download Java JRE 8 from here. Note that Java does allow you to have multiple JREs installed at the same time by setting the JAVA_HOME
environment variable.
We're working on it.
Spark has limited support for Java JRE 9 or later. This message is only a warning and can usually be ignored, however see above as to why we do not support Java 11.
WSL2 runs a separate TCP stack that is NAT-bridged to the main windows environment. See here for a possible workaround (make sure to include port 5000
in the list in the script).