You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 4, 2019. It is now read-only.
The real issue is that the coupling of boolean searches and the range operators should be separated in some way. Not sure if you guys have run into the same issue.
I tried to make the conditions confirm to the CakePHP ORM as much as possible, but at some point this breaks down because SQL supports different functionality than ElasticSearch.
The idea is that you should be able to very easily switch data sources with as few changes as possible.
Based on that principle, I'd probably use = and !=, and perhaps even <> for should not (or something similar).
I ran into some issues with boolean matches against fileds mapped as range (integers in particular).
This is a temp fix for this
https://github.com/ryantology/CakePHP-Elastic-Search-DataSource/commit/3badc2d14e65d6334106696529c320c9703e0925
The real issue is that the coupling of boolean searches and the range operators should be separated in some way. Not sure if you guys have run into the same issue.
The patch allows this query to work:
The text was updated successfully, but these errors were encountered: