Search - how's ElasticSearch doing?

[medwards]

Search is high priority for us. I still need to dig into this one, haven’t had time quite yet. Some links I've collected and need to follow-up on:

https://github.com/designcreateplay/NodeBB/issues/142
https://github.com/designcreateplay/NodeBB/issues/786
https://github.com/designcreateplay/NodeBB/pull/789

Nodebb-plugin-elasticsearch by seti123

Can anybody provide a quick status summary on this? @seti123? Is it ready to go? Does it require mongo?

If not I’ll circle back and update this thread later on with what I find.

cnvo created this issue in designcreateplay/NodeBB

closed Search #142

seti123 created this issue in designcreateplay/NodeBB

closed Addional hooks for search plugin #786

seti123 created this issue in designcreateplay/NodeBB

closed Allowing to use alternative search functions (nodebb-elasticsearch-plugin) #789

[julian]

Right -- @seti123 I believe there are some issues that block you from completion -- let us know what those are, so we can expedite as 0.3.0 is now out

[medwards]

@julian So I forked and installed @seti123 's plugin. I had to make a few changes to the way it calls topics.getTopicsByTids() - it looks like the function signature may have changed.

At this point I appear to be getting legitimate search results from the long-form search url that's being installed:

http://localhost:8252/nodebb-plugins-elasticsearch/search/:term

I believe the standing question is:

Is there some way to override the built-in /api/search/:term route so the UI will process the elasticsearch results instead of the built-in REDS results?

I'll dive in and see if I can figure it out... let me know if you have any input.

Thanks!

[julian]

Hey @medwards -- Indeed, that's what we're hoping to do with search. Not everyone wants to use Reds, so I'm actually planning on divorcing Reds from core, and allowing third-party plugins to interface with the routes.