graphql.execution.batched

Class UnbatchedDataFetcher

java.lang.Object

graphql.execution.batched.UnbatchedDataFetcher

All Implemented Interfaces:

BatchedDataFetcher, DataFetcher

Deprecated.

This has been deprecated in favour of using AsyncExecutionStrategy and DataLoaderDispatcherInstrumentation

@Deprecated
public class UnbatchedDataFetcher
extends java.lang.Object
implements BatchedDataFetcher

Given a normal data fetcher as a delegate, uses that fetcher in a batched context by iterating through each source value and calling the delegate.

Constructor Summary

Constructors

Constructor and Description
UnbatchedDataFetcher(DataFetcher delegate) Deprecated.

Method Summary

Modifier and Type	Method and Description
java.util.concurrent.CompletableFuture<java.util.List<java.lang.Object>>	get(DataFetchingEnvironment environment) Deprecated. This is called by the graphql engine to fetch the value.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

UnbatchedDataFetcher

public UnbatchedDataFetcher(DataFetcher delegate)

Deprecated.

Method Detail

get

public java.util.concurrent.CompletableFuture<java.util.List<java.lang.Object>> get(DataFetchingEnvironment environment)
                                                                             throws java.lang.Exception

Deprecated.

Description copied from interface: DataFetcher

This is called by the graphql engine to fetch the value. The DataFetchingEnvironment is a composite context object that tells you all you need to know about how to fetch a data value in graphql type terms.

Specified by:

get in interface DataFetcher

Parameters:

environment - this is the data fetching environment which contains all the context you need to fetch a value

Returns:

a value of type T. May be wrapped in a DataFetcherResult

Throws:

java.lang.Exception - to relieve the implementations from having to wrap checked exceptions. Any exception thrown from a DataFetcher will eventually be handled by the registered DataFetcherExceptionHandler and the related field will have a value of null in the result.