Brad Baker

> Will dataloaders work if we set this graphql.GraphQL.Builder#doNotAddDefaultInstrumentations? No this will stop the `DataLoaderDispatcherInstrumentation` from loading and this is crucial to using DataLoaders in graphql-java, since it knows when...

@padmapreethi-902117 - It's great that you capture some thread stack traces but this is rarely enough to truly nail down where the CPU is being burnt. The stack trace above...

> override the completeValueForList method to execute the list items parallely This seems like an interesting approach - graphql-java itself would never do any threading (since threading is a concern...

Can you please give a more concrete example of the type of fetchers you are doing that require multiple data loaders. Psudeo java code is ok The data loader instrumentation...

Thanks for outlining more in detail. One of the challenges we have today in Java is knowing when to dispatch the data loaders. Today we track fields and levels and...

You can chain data loaders BUT you cant do it with ULTIMATE efficiency graphql-java tracks fields and hence how many dataLoader.dispatch() calls it needs to make if it does it...

@linqi - can you please provide more code examples on how you dispatch You said > Inside DataLoader implementation, we can choose to either invoke dispatch(), or simply use the...

Can you tell me how you build the schema? via SDL or via direct Schema object building we have this code in input field uniquness in SDL ``` private void...

@omavi - can you please give us an reproducible example in SDL format where this bug is happening. We never got one originally on this issue and if we need...

> If you set the default data fetcher in the code registry, schema introspection will resolve "__Field.type" with the new default fetcher. Sorry but its working as designed - the...