cellery | Build run and manage code-first composites on Kubernetes | Microservice library

I solved the issue by changing the way I was testing and by changing the way I was importing the Celery configuration.

Initially, I was setting the configuration by importing a Django settings object:

There are several ways to set credentials. For more details aws/credentials.

For example, you can specify it by setting environment variables:

Basically what you want is to listen to the event of a cell become ready. You can register to the events in a cluster and act upon them. A good example can be found here

You are close to the solution. You can match the veggies in the first pattern. The where clause will remove not desired dishes.

The EXPLAIN and PROFILE options show the execution plan of the query.

They show the exact same execution plan for both queries (on an empty database).

So performance-wise, the two notations should be completely the same.

The first form seems to work well when you know the property value, but is there a way to use wildcards or a LIKE condition with it?

That's correct, WHERE gives you a lot more flexibility. Basically, the MATCH clause only allows you to check for equalities that could be written as WHERE a.prop1 = value1 AND a.prop2 = value2 AND .... Meanwhile, WHERE allows you a lot more: the AND/OR/XOR and NOT logical operators, checking for inequalities; using STARTS WITH, CONTAINS, ENDS WITH and regular expressions; checking for node types like WHERE (a:SomeLabel) or even checking if the variables of the match are part of a pattern like WHERE NOT (a)-[:SOME_REL]->(:SomeLabel).