(edit: if a moderator wants to move this post to the Siren Federate forum it might make more sense than here in the Investigate/UI section)
I have been exploring programmatic interaction from Python/Jupyter to Siren endpoints, and have seen some unexpected behavior with querying and projecting fields in the
/siren/<index>/_search endpoints. They may be bugs, or I may be misunderstanding the documentation. I put together a small repo that will start up Siren’s demo container and a single-user Jupyter environment via
docker-compose at GitHub - kafonek/siren: Demo and bug reporting for Jupyter Notebook interaction to Siren-Elasticsearch in case you want to reproduce the queries.
I’ve shown the raw RESTful queries for the bugs (?) in the
/notebooks/bugs directory. The first issue is that
project fields are not coming back in my result set.
The second issue is DSL parse errors while trying to include query terms for one index while also joining to another index. (Filtering by Both Indices explains how to do the boolean must query)
Any advice on those bug Notebooks is appreciated, thanks!