Problem when uploading a java flink program to aws lambda

[Kulasangar]

I have created a java application using flink api and table api. I can
provide the source code if needed.

The application works perfectly locally. But when I tried to upload the
created jar in aws lambda and execute it I'm being thrown with the following
error:

reference.conf: 804: Could not resolve substitution to a value:
${akka.stream.materializer}:
com.typesafe.config.ConfigException$UnresolvedSubstitution
com.typesafe.config.ConfigException$UnresolvedSubstitution: reference.conf:
804: Could not resolve substitution to a value: ${akka.stream.materializer}
at
com.typesafe.config.impl.ConfigReference.resolveSubstitutions(ConfigReference.java:87)
at
com.typesafe.config.impl.ResolveSource.resolveCheckingReplacement(ResolveSource.java:110)

I have posted only the first few lines of the exception. Has anyone come
across this typa error?

Any help would be appreciated.

Regards.



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

[Aljoscha Krettek]

Could you please post your build setup. Pom file? And maybe also the contents of your Jar file.

Best,
Aljoscha

> On 22. Feb 2018, at 10:39, Kulasangar <[hidden email]> wrote:
>
> I have created a java application using flink api and table api. I can
> provide the source code if needed.
>
> The application works perfectly locally. But when I tried to upload the
> created jar in aws lambda and execute it I'm being thrown with the following
> error:
>
> *reference.conf: 804: Could not resolve substitution to a value:
> ${akka.stream.materializer}:
> com.typesafe.config.ConfigException$UnresolvedSubstitution
> com.typesafe.config.ConfigException$UnresolvedSubstitution: reference.conf:
> 804: Could not resolve substitution to a value: ${akka.stream.materializer}
> at
> com.typesafe.config.impl.ConfigReference.resolveSubstitutions(ConfigReference.java:87)
> at
> com.typesafe.config.impl.ResolveSource.resolveCheckingReplacement(ResolveSource.java:110)*
>
> I have posted only the first few lines of the exception. Has anyone come
> across this typa error?
>
> Any help would be appreciated.
>
> Regards.
>
>
>
> --
> Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/