Sylvain Lebresne

> neither of them worked and resulted a composition error that because name field marked as external but not being in use (cuz federation doesn't recognize it) in @provides. What...

> In https://github.com/apollographql/federation/issues/336, implementation of an interface is not available in a subgraph, here I'm trying to implement an interface in two different subgraphs. For what it's worth, I created...

Is this creating an issue for you? In general, there is no real guarantees that the fetch in the query plan maps exactly to the syntax of the original query...

Is the question regarding not having to re-define the input type in all the subgraphs that use that input type? If so, there is no federation specific feature to do...

I generally agree that we can and should improve our handling of fragments. In particular, there is cases where we ought to be able to reuse existing fragments but we...

@AneethAnand: very sorry I wasn't able to get to this earlier. I did just now leave some comment, though one thing that happened since my last comment is #2497: the...

Hi. Federation is no tailor made support for appsync per-se, but you can declare whichever scalar you want in our subgraphs, so I'd assume that you'd just need to add...

Some technical details on the changes here for reviewers sake. The core of the changes of this patch is `IndexDescriptor`, which handles the SAI components for an sstable, but that...

> Is this correct ? Yes.

As mentioned on slack, the code moved to use the TOC as a mean to find the current generation of SAI components to use, and this to avoid having to...