Categories
be2 prihlasit se

On node protect, next, we both blogged a node to the Elasticsearch machine (if it ended up being published)

On node protect, next, we both blogged a node to the Elasticsearch machine (if it ended up being published)

or removed it from the host (if unpublished); Elasticsearch manages updating a current record or removing a non-existent record without concern. Before writing out the node, however, we modified it a great deal. We necessary to cleaning a lot of the information, restructure they, merge sphere, eliminate unimportant areas, an such like. All of that ended up being completed in the travel whenever creating the nodes off to Elasticsearch.

Another note about this: for results grounds, in order to abstain from battle ailments when saving nodes, we deferred the specific processing to Drupal’s waiting line program. That perfectly avoided race problems around accessing nodes during node salvage and held an individual user interface smooth and responsive.

There is another requirement: ever since the incoming data ended up being typically partial we necessary to furthermore transfer facts from RottenTomatoes.com. For that we developed a two level system: One is an universal PHP package by using the Guzzle collection that conveyed Rotten Tomatoes content as PHP things, as the more after that bridges that program to generate Drupal nodes populated from Rotten Tomatoes facts. We after that matched up Rotten Tomatoes videos and feedback using the client’s provider facts and allowed editors to elect to use information from Rotten Tomatoes in favor of their particular where appropriate.