How o19s/solr-tmdb works
Project type and purpose
• This is a specialized search indexing project, not a typical full-stack app. Its sole purpose is to ingest The Movie Database (TMDB) JSON data, configure an Apache Solr core, and expose a searchable index. It’s used in training as part of the “Think Like a Relevancy Engineer” curriculum.
File structure
• Top-level scripts:
• docker.sh / docker.ps1 & docker/ folder → Dockerized Solr setup
• index.sh / index.ps1 → Shell/PowerShell wrappers that POST the TMDB JSON into Solr
• solr_home/ → All Solr configuration for the “tmdb” core (schema.xml, solrconfig.xml, stopwords, synonyms, etc.)
• docker/lib/ → External JARs (Querqy filters) mounted into Solr via configuration
• housekeeping/ → Python scripts (createSolrTmdbDataset.py, tmdbMovies.py) to fetch or transform data and testing scripts
• solr-postman-collection.json → Postman collection for interactive API calls
README for additional insights
• The README confirms Docker is the recommended deployment, but manual Solr install can also be used.
• It lays out the workflows: download, start Solr, index data, confirm via queries, optionally use Postman.
Components
a. Data Sources
• TMDB JSON file (external data file)
b. Data-Preparation Layer
• Python scripts in housekeeping/create_dataset (fetch/transform → intermediate JSON)
c. Indexing Layer
• index.sh / index.ps1 → invokes HTTP POST to Solr’s /tmdb/update endpoint
d. Search Engine
• Solr server running inside Docker (or locally if not containerized)
• Docker container with mounted volumes:
– solr_home/tmdb/conf (core configuration)
– docker/lib JARs (Querqy extensions)
e. Client & Testing
• Postman (solr-postman-collection.json) or direct CURL/HTTP clients
• housekeeping/testing scripts for validation
Relationships & interactions
• Solr container shows two mounted volumes: configuration and extension libraries
• Clients (Postman, test scripts) query Solr’s HTTP GET/POST endpoints and receive JSON responses
Architectural patterns and principles
• Separation of concerns: data ingestion, indexing, search
• Containerization: isolated Solr environment for reproducibility
• Config-as-Code: all schema and config files versioned in solr_home
• Extensibility: custom filters (Querqy) loaded from docker/lib