cern-search-rest-api issueshttps://gitlab.cern.ch/webservices/cern-search/cern-search-rest-api/-/issues2019-09-13T16:13:35+02:00https://gitlab.cern.ch/webservices/cern-search/cern-search-rest-api/-/issues/1Add support for nested queries2019-09-13T16:13:35+02:00Pablo Panero VazquezAdd support for nested queriesThe REST API allows users to query through [query_string](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/query-dsl-query-string-query.html). However, it does not support ``nested`` objects, there is a related issue in [inven...The REST API allows users to query through [query_string](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/query-dsl-query-string-query.html). However, it does not support ``nested`` objects, there is a related issue in [invenio-search](https://github.com/inveniosoftware/invenio-search/issues/155). Since the mappings are known before hand a custom filter can be set up in ``invenio-records-rest``. This is done in asclepias-broker: [filter](https://github.com/asclepias/asclepias-broker/blob/82dbc20e42e079520f33bf4e32078e3a88eac5f6/asclepias_broker/search.py#L62-L81) [config](https://github.com/asclepias/asclepias-broker/blob/82dbc20e42e079520f33bf4e32078e3a88eac5f6/asclepias_broker/config.py#L201-L223).
For now all composed objects will be treated as ``object``, using the ``include_in_parent = true`` propertie of the element. However, this property might be [deprecated](https://github.com/elastic/elasticsearch/issues/12461) in the future.https://gitlab.cern.ch/webservices/cern-search/cern-search-rest-api/-/issues/59edms: index backward slash2019-09-13T16:12:26+02:00Pablo Panero Vazquezedms: index backward slash- When querying all special characters must be escaped [docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#_reserved_characters).
- When indexing, they just need to be encoded.
Howeve...- When querying all special characters must be escaped [docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#_reserved_characters).
- When indexing, they just need to be encoded.
However, \ breaks the indexing. There is an strange case when putting quotes right after (e.g. "field":"value \""), but the indexed value will also contain that quote.
Needs debugging.https://gitlab.cern.ch/webservices/cern-search/cern-search-rest-api/-/issues/64edms: issues with bulk indexing2019-09-13T16:11:38+02:00Pablo Panero Vazquezedms: issues with bulk indexinguWSGI get slow in bulk indexing, then nginx closes the connection. Generating an error mentioned [here](https://github.com/unbit/uwsgi/issues/1623)
Maybe related with [this](https://github.com/cernopendata/opendata.cern.ch/pull/2428/com...uWSGI get slow in bulk indexing, then nginx closes the connection. Generating an error mentioned [here](https://github.com/unbit/uwsgi/issues/1623)
Maybe related with [this](https://github.com/cernopendata/opendata.cern.ch/pull/2428/commits) issue of CERN OpenDatahttps://gitlab.cern.ch/webservices/cern-search/cern-search-rest-api/-/issues/87global: expose health status2019-11-06T10:51:34+01:00Pablo Panero Vazquezglobal: expose health statusExpose health status to the outside. This would allow clients to check if their search instance is up and running.
Need to aggregate the `/health/{es,db,uwsig}` (web app) + `/ping` (nginx) endpoint responses.Expose health status to the outside. This would allow clients to check if their search instance is up and running.
Need to aggregate the `/health/{es,db,uwsig}` (web app) + `/ping` (nginx) endpoint responses.