FT.AGGREGATE query matches no results

76 views
Skip to first unread message

Paul

unread,
May 13, 2019, 9:38:39 AM5/13/19
to redisearch
Hello,
I am seeing this error when issuing an FT.AGGREGATE that returns no results, FT.SEARCH on the other hand just returns 0. 

Is returning this error the the desired behavior, and is there a way to have FT.AGGREGATE also return 0? I am using version 1.4.2

Thank you,
Paul

Meir Shpilraien

unread,
May 13, 2019, 2:47:05 PM5/13/19
to redisearch
Currently this is the API we provide, we are working on combining FT.SEARCH and FT.AGGREGATE to a single command and then we might consider changing it.

Άγγελος Δημόπουλος

unread,
Mar 28, 2020, 10:59:33 AM3/28/20
to RediSearch Discussion Forum
Hello,
Is there any plan where would this merge be available? I am very interested in having one command to support both functionalities.
I have seen also this github issues https://github.com/RediSearch/RediSearch/issues/689.

For now playing with 1.6.10, i am a little confused about what is supported from each command? Documentation is not that clear.

Pieter Cailliau

unread,
Mar 28, 2020, 7:56:15 PM3/28/20
to RediSearch Discussion Forum
Hi,

The documentation is up to date and reflects which features are currently supported.  We're working on versioned documentation to make it even more clear, but right now the docs reflect best the 1.6 release.  

With supported, we mean that we have the tests in place to avoid regression, the correctness of execution, take this API up in performance tests etc...

One of the major items we tackled when developing 1.6 was unifying the code between FT.AGGREGATE and FT.SEARCH to be better maintainable. As a consequence, certain functionality that is not documented - and hence not supported - got exposed.  They are some of those unsupported easter eggs and we recommend not using them since 
1. we don't know if they are working correctly
2. we can't guarantee that we will maintain this "hidden" API in future release.

That said.  We do still envision to unify the two API's, albeit we can't commit on a timeline yet.

If you have a specific question on how to solve your specific search query, we're more than happy to help, but I suggest to move that to another thread.

Pieter

Άγγελος Δημόπουλος

unread,
Mar 29, 2020, 9:42:09 AM3/29/20
to RediSearch Discussion Forum
Thank you very much. Your answer was more than enough!
Reply all
Reply to author
Forward
0 new messages