Passing objects instead of classes to JobGraph (JobVertex)

[Gyula Fóra]

Hello,

Is there any way to pass objects when constructing a JobVertex instead of passing classes?

This would allow the user to give paramaters to a constructor. For example:

What we would like to have:

final JobInputVertex source = new JobInputVertex(sourceName, jobGraph);

source.setInputClass(new StreamSource(someparam));

instead of:

source.setInputClass( StreamSource.class );

Thank you!

Gyula

[Stephan Ewen]

Hi!

There is not at the moment. The lower layers take classes and configurations. On the higher layers, we have build support for passing objects.

You can do something similar: Have a generic task that reads serialized objects from the config and then invokes them.

We are planning to change this as part of the lower layers cleanup, but I will probably not happen in the next month.

Stephan

--
You received this message because you are subscribed to the Google Groups "stratosphere-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stratosphere-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/stratosphere-dev.
For more options, visit https://groups.google.com/d/optout.

[Gyula Fóra]

Hey,

So I checked your UserCodeObjectWrapper and it seems like the user can only define operators that contain no non-serializable fields? This seems to be kind of restricting.

Gyula

[Robert Metzger]

Hi,

I think you can make the field "transient" if you don't want it to be serialized. Our UserCodeObjectWrapper should not throw an exception for non-serializable, transient fields.

Robert