Skip to main content

udata search service

Project description

udata-search-service

A search service for udata. The idea is to have search service separated from the udata MongoDB. The indexation update is made using real-time messages with Kafka.

See the following architecture schema: Udata Search Service architecture schema

Getting started

You can follow this recommended architecture for your code:

$WORKSPACE
├── fs
├── udata
│   ├── ...
│   └── setup.py
│		└── udata.cfg
├── udata-front
│   ├── ...
│   └── setup.py
└── udata-search-service
    ├── ...
    └── pyproject.toml

Clone the repository:

cd $WORKSPACE
git clone git@github.com:opendatateam/udata-search-service.git

Start the different services using docker-compose:

cd udata-search-service
docker-compose up

This will start:

  • an elasticsearch
  • a kafka broker
  • a zookeper
  • a kafka consumer
  • a search app

Initialize the elasticsearch indices on setup.

# Locally
udata-search-service init-es

# In the docker context
docker-compose run --entrypoint /bin/bash web -c 'udata-search-service init-es'

You can feed the elasticsearch by publishing messages to Kafka. Using udata, when you modify objects, indexation messages will be sent and will be consumed by the kafka consumer. If you want to reindex your local mongo base in udata, you can run:

cd $WORKSPACE/udata/
source ./venv/bin/activate
udata search index

After a reindexation, you'll need to change the alias by using the following command:

# Locally
udata-search-service set-alias <index-suffix>

# In the docker context
docker-compose run --entrypoint /bin/bash web -c 'udata-search-service set-alias <index-suffix>'

You can query the search service with the search service api, ex: http://localhost:5000/api/1/datasets/?q=toilettes%20à%20rennes

Development

You can create a virtualenv, activate it and install the requirements with the following commands.

python3 -m venv venv
source venv/bin/activate
make deps
make install

You can start the Elasticsearch and Kafak broker and zookeper using the docker compose. You can start the consumer locally with the following command:

udata-search-service consume-kafka

You can start the web search service with the following command:

udata-search-service run

Troubleshooting

  • If the elasticsearch service exits with an error 137, it is killed due to out of memory error. You should read the following points.
  • If you are short on RAM, you can limit heap memory by setting ES_JAVA_OPTS=-Xms750m -Xmx750m as environment variable when starting the elasticsearch service.
  • If you are on MAC and still encounter RAM memory issues, you should increase Docker limit memory to 4GB instead of default 2GB.
  • If you are on Linux, you may need to double the vm.max_map_count. You can set it with the following command: sysctl -w vm.max_map_count=262144.
  • If you are on Linux, you may encounter permissions issues. You can either create the volume or change the user to the current user using chown.

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

udata-search-service-0.0.0.dev85.tar.gz (46.1 kB view details)

Uploaded Source

Built Distribution

udata_search_service-0.0.0.dev85-py2.py3-none-any.whl (17.8 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file udata-search-service-0.0.0.dev85.tar.gz.

File metadata

File hashes

Hashes for udata-search-service-0.0.0.dev85.tar.gz
Algorithm Hash digest
SHA256 faef771ab93a9ff2a1d78201ec836ca2fefc7f4a9dcb813621905ec685f3c471
MD5 c3d41dd0ae21223aa1454c9e4556677e
BLAKE2b-256 4011ce3cb1801277130824506075e2d92f525e964bb3a0c31b258376744a4ffc

See more details on using hashes here.

File details

Details for the file udata_search_service-0.0.0.dev85-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for udata_search_service-0.0.0.dev85-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 6a188ca9deaf4bf3d383003a041868c2ec7b10fd66adee178d459b3320c024e0
MD5 08eb5410db860b648180030f17b5d66a
BLAKE2b-256 542ef5e56b9d911487b928848902079f62c8508f256ce4ecd94a4be3c8937241

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page