Search Fundamentals is a two week class taught by Grant Ingersoll and Daniel Tunkelang and is focused on helping students quickly get up to speed on search by teaching the basics of search like indexing, querying, faceting/aggregations, spell checking, typeahead autocomplete and highlighting.
The class is a hands-on project-driven course where students will work with real data and the Opensearch/Elasticsearch ecosystem.
For our class, we have two weekly projects. Each project is a standalone Python Flask application that interacts with an OpenSearch server (and perhaps other services).
You will find these four projects in the directories below them organized in the following way:
- Week 1:
- week1 -- The unfinished template for the week's project, annotated with instructions.
- Week 2:
- week2 -- The unfinished template for the week's project, annotated with instructions.
Our instructor annotated results for each project will be provided during the class.
Please note, these represent our way of doing the assignment and may differ from your results,
as there is often more than one way of doing things in search.
You will also find several supporting directories and files for Docker and Gitpod.
You can also use the included Makefile
to interact with the project, including running pyenv, Flask, and re-indexing the data. Run all make
commands at the root of the repo so Makefile can pick them up, i.e. /workspace/search-fundamentals
.
- For this class, you will need a Kaggle account and a Kaggle API token.
- No prior search knowledge is required, but you should be able to code in Python or Java (all examples are in Python)
- You will need a Gitpod account.
-
Fork this repository.
-
Launch a new Gitpod workspace based on this repository. This will automatically start OpenSearch and OpenSearch Dashboards.
- Note: it can take a few minutes for OpenSearch and the dashboards to launch.
-
You should now have a running Opensearch instance (port 9200) and a running Opensearch Dashboards instance (port 5601)
-
Login to the dashboards at
https://5601-<$GITPOD_URL>/
with default usernameadmin
and passwordadmin
. This should popup automatically as a new tab, unless you have blocked popups. Also note, that in the real world, you would change your password. Since these ports are blocked if you aren't logged into Gitpod, it's OK.$GITPOD_URL is a placeholder for your ephemeral Gitpod host name, e.g. silver-grasshopper-8czadqyn.ws-us25.gitpod.io
-
Run the install Kaggle API token script and follow the instructions:
./install-kaggle-token.sh
-
Accept all of the kaggle competition rules then run the download data script:
./download-data.sh (or `make download`)
-
Verify your data is in the right location:
ls /workspace/datasets
-
You should see:
popular_skus.py product_data test.csv train.csv
- Login to OpenSearch and point your browser at
https://5601-<$GITPOD_URL>/app/opensearch_dashboards_overview#/
- Click the "Add sample data" link
- Click the "Add Data" link for any of the 3 projects listed. In the class, we chose the "Sample flight data", but any of the three are fine for exploration.
At the command line, do the following steps to run the example.
- Activate your Python Virtual Environment. We use
pyenv
Pyenv website andpyenv-virtualenv
Pyenv Virtualenv, but you can use whatever you are most comfortable with. A.pyenv activate search_fundamentals
-- Activate that Virtualenv. - Run Flask: run
make week1
ormake week2
depending on which week you need A. Open the Flask APP athttps://3000-<$GITPOD_URL>/
(or whatever port you choose) - Or run
ipython
To run locally, you will need a few things:
- Pyenv and Pyenv-Virtualenv with Python 3.9.7 installed
- Docker
- A Git client
Note: these have only been tested on a Mac running OS 12.2.1. YMMV. Much of what you will need to do will be similar to what's in .gitpod.Dockerfile
pyenv install 3.9.7
pip install
all of the libraries you see in.gitpod.Dockerfile
- Setup your weekly python environments per the "Weekly Project" above.
- Run OpenSearch:
A.
cd docker
B.docker-compose up
- Note: most of the scripts and projects assume the data is in
/workspace/datasets
, but have overrides to specify your own directories. You will need to download and plan accordingly. - Do your work per the Weekly Project