Can you post the code you’re using for the query with the SDK or the parameters you’re using in the UI? There’s a nice little URL you can click on in the UI and if you right click it, you can paste it here and we can see all the params.
I have a suspicion about what it may be. Can you make the endkey [“K”] and see if it works properly? I have a suspicion there may be a bug with inclusive_end, which I just observed recently but need to verify.
There is no way to do so at the moment with views. The best method is to filter it at the client side at the moment. If you’re using the Java client, the RxJava interface makes this pretty straightforward.
N1QL (in 4.0 dev preview) will have more filtering options at the cluster side.
I agree it’s not ideal, but if the query is likely to match many of the results it’s not always bad (this is sort of the selectivity on an index) and you can fetch the underlying documents after the filter, as the view is effectively the the index and the underlying documents are the result.