THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- We does not change the current streaming and batch style sink API. So there is no compatibility issue to the existing sink implementation.
- In the long run we might need to deprecate the old streaming and batch style sink API.
- At first we plan to migrate the StreamingFileSink to this new api.
Rejected Alternatives
The only difference between the rejected version and accepted version is how to expose the state to the user. The accepted version could give the framework a greater opportunity to optimize the state handling.
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
/**
* The sink interface acts like a factory to create the {@link Writer} and {@link Committer}.
*
* @param <T> The type of the sink's input.
* @param <CommT> The type of the committable data.
*/
public interface Sink<T, CommT> extends Serializable {
/**
* Create a {@link Writer}.
* @param context the runtime context
* @return A new sink writer.
*/
Writer<T, CommT> createWriter(InitialContext context) throws Exception;
/**
* Create a {@link Committer}.
* @return A new sink committer
*/
Committer<CommT> createCommitter();
/**
* @return a committable serializer
*/
SimpleVersionedSerializer<CommT> getCommittableSerializer();
/**
* Providing the runtime information.
*/
interface InitialContext {
boolean isRestored();
int getSubtaskIndex();
OperatorStateStore getOperatorStateStore();
MetricGroup metricGroup();
}
}
|
...