0

I am using ElasticSearch in Moqui. DataDocument and Feed documents are set, everything is working. Except for the situation when I restart the server. I need to run the org.moqui.search.SearchServices.index#DataFeedDocuments service. Does this means that the indices are stored in-memory? And I have to restore them by running the service?

I also set up the Real-time Service Push [DTFDTP_RT_PUSH] service for MantleProduct. Does this service only take care of refreshing when individual entities are modified?

mrovnanik
  • 123
  • 9

1 Answers1

0

Yes, a real-time push DataFeed is just for that purpose, ie to generate a new 'document' (JSON document, though internally nested Map and List objects) based on the DataDocument definitions associated with the DataFeed and call the service on the DataFeed with them. The indexing service then takes those and indexes them in ElasticSearch. Other services can be used for different things such as sending notifications.

The index documents are persisted in ElasticSearch unless you delete its files. If something in the way you are restarting the server deletes the ElasticSearch files then you'll have to use the Data Document Index screen in the System app to tell it to re-index all documents based on database records.

David E. Jones
  • 1,721
  • 1
  • 9
  • 8
  • It works well, thanks for the guidance. Is there any chance I can specify which documents the service is going to index? I can see the index#DataFeedDocuments service accepts **fromUpdateStamp** and **thruUpdateStamp** parameters that are used to filter the documentList. But I cannot find a way how to set those two. – mrovnanik Aug 12 '17 at 22:02
  • In the the documentation (Making Apps with Moqui) there is an example with **HiveMind.SearchServices.indexAndNotify#HiveMindDocuments** service. Is that the way to go? – mrovnanik Aug 12 '17 at 22:23