Thanks Till, your solution worked perfectly.
Arpith
On Wed, Feb 17, 2021 at 12:53 AM Arvid Heise wrote:
> Hi Arpith,
>
> The operator test harness is more meant for use cases where you implement
> your own operator (quite advanced).
>
> If you just want to test your AsyncFunction, I'd strongly
Hi Arpith,
The operator test harness is more meant for use cases where you implement
your own operator (quite advanced).
If you just want to test your AsyncFunction, I'd strongly recommend
building a small ITCase like [1] and then you don't have to fiddle with
these things anymore. The tests run
Hi Arpith,
looking at the definition of the GetMetadataAsyncProcess function you need
to specify the TypeSerializer for a Tuple1>>. What
you could try in order to not create the serializer manually is to use:
TypeInformation.of(new TypeHint>>>(){}).createSerializer(new ExecutionConfig())
This sh
Hi,
I tried mocking the Async operator which takes Tuple1, Tuple3 as Input &
Output but while creating a test harness I couldn't find the right
TupleSerializer. Can anyone help me on this?
public class GetMetadataAsyncProcess extends
RichAsyncFunction>>,
Tuple3>, Map,
List>>> {
...
}
private
