[jira] [Created] (FLINK-21138) KvStateServerHandler is not invoked with user code classloader
Maciej Prochniak created FLINK-21138: Summary: KvStateServerHandler is not invoked with user code classloader Key: FLINK-21138 URL: https://issues.apache.org/jira/browse/FLINK-21138 Project: Flink Issue Type: Bug Components: Runtime / Queryable State Affects Versions: 1.11.2 Reporter: Maciej Prochniak When using e.g. custom Kryo serializers user code classloader has to be set as context classloader during invocation of methods such as TypeSerializer.duplicat() KvStateServerHandler does not do this, which leads to exceptions like ClassNotFound etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLINK-10165) JarRunHandler/JarRunRequestBody should allow to pass program arguments as escaped json list
Maciej Prochniak created FLINK-10165: Summary: JarRunHandler/JarRunRequestBody should allow to pass program arguments as escaped json list Key: FLINK-10165 URL: https://issues.apache.org/jira/browse/FLINK-10165 Project: Flink Issue Type: Improvement Components: REST Affects Versions: 1.6.0 Reporter: Maciej Prochniak Currently program arguments are parsed from plain string: [https://github.com/apache/flink/blob/master/flink-runtime-web/src/main/java/org/apache/flink/runtime/webmonitor/handlers/JarRunHandler.java#L106] It doesn't allow to put quotes or new lines in arguments - in particular it's difficult to pass json as argument. I think it would be good to pass arguments as json list - then jackson would handle escaping. It'd be a bit more problematic for query string parameters... WDYT [~Zentol]? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-4782) log4j & slf4j-log4j are present in jar-with-dependencies artifacts
Maciej Prochniak created FLINK-4782: --- Summary: log4j & slf4j-log4j are present in jar-with-dependencies artifacts Key: FLINK-4782 URL: https://issues.apache.org/jira/browse/FLINK-4782 Project: Flink Issue Type: Bug Components: Metrics Affects Versions: 1.1.2 Reporter: Maciej Prochniak Priority: Minor This makes it more difficult to use dropwizard metrics with e.g. logback It's because they are declared in parent pom as compile scope dependencies. I don't clearly understand why is it this way - I'd rather have them provided (as they are still specified in dist) but maybe there are some good reasons for that? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FLINK-4619) JobManager does not answer to client when restore from savepoint fails
Maciej Prochniak created FLINK-4619: --- Summary: JobManager does not answer to client when restore from savepoint fails Key: FLINK-4619 URL: https://issues.apache.org/jira/browse/FLINK-4619 Project: Flink Issue Type: Bug Affects Versions: 1.1.1 Reporter: Maciej Prochniak When savepoint used is incompatible with currently deployed process, the job manager never returns (jobInfo.notifyClients is not invoked in one of try-catch blocks) -- This message was sent by Atlassian JIRA (v6.3.4#6332)