Hi,

First of all, the ticket reports a bug (or improvement or feature
suggestion) such that others are aware of the problem and understand its
cause.

At some point it might be picked up and implemented. In general, there is
no guarantee whether or when this happens, but the Flink community is of
course eager to fix bugs and it's a rather important problem.
So it might be addressed soon. However, I cannot promise for which release
it will be fixed.

You can of course help the community (and yourself) and contribute a fix
for this problem.
Scratching your own itch is a good way to get started in contributing to
open source projects ;-).

Best, Fabian


2018-07-25 10:23 GMT+02:00 Averell <lvhu...@gmail.com>:

> Thank you Fabian for the guide to implement the fix.
>
> I'm not quite clear about the best practice of creating JIRA ticket. I
> modified its priority to Major as you said that it is important.
> What would happen next with that issue then? Someone (anyone) will pick it
> and create a fix, then include that in the following release?
>
> Thanks!
>
>
>
> --
> Sent from: http://apache-flink-user-mailing-list-archive.2336050.
> n4.nabble.com/
>

Reply via email to