Re: [Wikitech-l] Search Flow using ES/CirrusSearch in MW 1.25?

I have no idea. Flow’s search API should be able to provide all the data that is needed, but I haven’t looked into how it could be integrated into normal searches yet (if at all) Matthias > On 03 Dec 2015, at 18:09, James Montalvo wrote: > > Any estimate on the

Re: [Wikitech-l] Search Flow using ES/CirrusSearch in MW 1.25?

Hi Daren, I don’t think the Flow search index scripts rely on any specific 1.26 code, Running it on 1.25 will be fine, I guess (though I haven’t tried it) I’m not sure those scripts do what you’d expect them to do, though. Running the Flow index scripts won’t add Flow’s data into the existing

Re: [Wikitech-l] Search Flow using ES/CirrusSearch in MW 1.25?

Any estimate on the amount of work required to integrate Flow searches into normal content searches? On Thu, Dec 3, 2015 at 10:45 AM, Matthias Mullie wrote: > > So it sounds like there's no way to search Flow content through > > Special:Search (or any other interface a

Re: [Wikitech-l] Search Flow using ES/CirrusSearch in MW 1.25?

> So it sounds like there's no way to search Flow content through > Special:Search (or any other interface a normal user would have). Is that > right? Correct, there is currently no UI. > > It looks like ApiFlowSearch.php was added in REL1_26 [1] (I don't see it in > REL1_25 [2]). I'll tinker

Re: [Wikitech-l] Search Flow using ES/CirrusSearch in MW 1.25?

So it sounds like there's no way to search Flow content through Special:Search (or any other interface a normal user would have). Is that right? It looks like ApiFlowSearch.php was added in REL1_26 [1] (I don't see it in REL1_25 [2]). I'll tinker around with a 1.26 setup and see if I can figure

[Wikitech-l] Search Flow using ES/CirrusSearch in MW 1.25?

I'm referencing [1] in an attempt to get Cirrus Search (Elasticsearch) to search and return results from Flow boards in MW 1.25. Some of the scripts like FlowSearchConfig.php don't seem to be in REL1_25, but they do seem to be in REL1_26. Does this mean I won't be able to get this to work in 1.25