Let's try this again; the formatting went haywire for some reason...
public class MetaDataUtils {
public static ExecutionConfig.GlobalJobParameters
createMetaData(ParameterTool parameterTool) {
Map metaData = new
HashMap<>(parameterTool.toMap());
setFromManifest(metaData,
For completeness sake, here's an example of what we're doing to add the
job arguments and some manifest entries to the global job parameters:
(Manifests is a class from jcabi-manifests)
public class MetaDataUtils {
public static ExecutionConfig.GlobalJobParameters
createMetaData(ParameterT
Thanks Chesnay for the tip.
I'll try to investigate the usage of GlobalJobParameters.
On Wed, Jul 15, 2020 at 2:51 PM Chesnay Schepler wrote:
> The more we strive towards a model where an application can submit
> multiple jobs it will become increasingly important to be able to attach
> meta dat
The more we strive towards a model where an application can submit
multiple jobs it will become increasingly important to be able to attach
meta data to a job/application to have any idea what is going on.
But I don't think the PackagedProgram/ProgramDescription is the way to
go; and I'd envis
Ok, it's not a problem for me if the community is not interested in pushing
this thing forward.
When we develop a Job is super useful for us to have the job describing
itself somehow (what it does and which parameters it requires).
If this is not in Flink I have to implement it somewhere else but I
I think no-one is interested to push this personally right now. We would need a
champion that is interested and pushes this forward.
Best,
Aljoscha
On Mon, Mar 30, 2020, at 12:45, Flavio Pompermaier wrote:
> I would personally like to see a way of describing a Flink job/pipeline
> (including its
I would personally like to see a way of describing a Flink job/pipeline
(including its parameters and types) in order to enable better UIs, then
the important thing is to make things consistent and aligned with the new
client developments and exploit this new dev sprint to fix such issues.
On Mon,
On 18.03.20 14:45, Flavio Pompermaier wrote:
what do you think if we exploit this job-submission sprint to address also
the problem discussed in https://issues.apache.org/jira/browse/FLINK-10862?
That's a good idea! What should we do? It seems that most committers on
the issue were in favour o
