Howard M. Lewis Ship

Have you signed a CLA? Normally, GitHub indicates that.

An interceptor is exactly what I was thinking and basic work to support looking up a parsed query by name, including a hash fingerprint.

Since we don't yet use this in the Walmart code, we don't have a good battle-tested solution for this. I'll bring it up internally ... I'd like to see some...

We've been interating on this internally; the concensus was to have yet another endpoint for stored queries. A full implementation also includes a restful POST endpoint for creating queries, but...

That doesn't look like it is supported using the provided interceptors and handlers.

Although Lacinia provides a timeout option on executing queries (both in-thread and async), this is not exposed by lacinia-pedestal (which bypasses com.walmartlabs.lacinia/execute in any case). This could be handled by...

I'm open to this and, yes, we don't actually use cheshire in production at Walmart so coming up with a pluggable way to replace it would be fine. I suspect...

Do we want to get to the point where we have macros to assist; e.g., a create-on-demand job who'se id is based on the current namespace?

Possibly this could be done as an additional SyncAPI protocol on the two status board implementations, and then it wouldn't matter as much; it could all be defined in the...

I'll be pleased to look at this, once the CLA is signed. Thanks so much!