mple have a random mix of different topics and that would mean
>>> that
>>> > RollingSink isn't able to respect the max flush size but keeps
>>> flushing the
>>> > files pretty much on every tuple.
>>> >
>>> > We've thought that we could implement a sink that internally creates
>>> and
>>> > handles multiple RollingSink instances as needed for partitions. But it
>>> > would be great to first hear any suggestions that you might have.
>>> >
>>> > If we have to extend RollingSink, it would be nice to make it take a
>>> > partitioning function as a parameter. The function would be called for
>>> each
>>> > tuple to create the output path.
>>> >
>>> >
>>> >
>>> > --
>>> > View this message in context:
>>> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Dynamic-partitioning-for-stream-output-tp7122.html
>>> > Sent from the Apache Flink User Mailing List archive. mailing list
>>> archive at Nabble.com <http://nabble.com>.
>>>
>>
>>
ut keeps flushing
>> the
>> > files pretty much on every tuple.
>> >
>> > We've thought that we could implement a sink that internally creates and
>> > handles multiple RollingSink instances as needed for partitions. But it
>> > would be great to first hear any suggestions that you might have.
>> >
>> > If we have to extend RollingSink, it would be nice to make it take a
>> > partitioning function as a parameter. The function would be called for
>> each
>> > tuple to create the output path.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Dynamic-partitioning-for-stream-output-tp7122.html
>> > Sent from the Apache Flink User Mailing List archive. mailing list
>> archive at Nabble.com <http://nabble.com>.
>>
>
>
ould implement a sink that internally creates and
> > handles multiple RollingSink instances as needed for partitions. But it
> > would be great to first hear any suggestions that you might have.
> >
> > If we have to extend RollingSink, it would be nice to make it take a
>
retty much on every tuple.
>> >
>> > We've thought that we could implement a sink that internally creates and
>> > handles multiple RollingSink instances as needed for partitions. But it
>> > would be great to first hear any suggestions that you might have.
>> >
>> > If we have to extend RollingSink, it would be nice to make it take a
>> > partitioning function as a parameter. The function would be called for
>> each
>> > tuple to create the output path.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Dynamic-partitioning-for-stream-output-tp7122.html
>> > Sent from the Apache Flink User Mailing List archive. mailing list
>> archive at Nabble.com.
>>
>
> > handles multiple RollingSink instances as needed for partitions. But it
> > would be great to first hear any suggestions that you might have.
> >
> > If we have to extend RollingSink, it would be nice to make it take a
> > partitioning function as a parameter. T
ould be called for each
> tuple to create the output path.
>
>
>
> --
> View this message in context:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Dynamic-partitioning-for-stream-output-tp7122.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at
> Nabble.com.
ive.2336050.n4.nabble.com/Dynamic-partitioning-for-stream-output-tp7122.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
