enable Flink SQL could also benefit from state TTL?
> > >
> > > Best
> > > Yun Tang
> > >
> > > On 11/25/19, 12:16 AM, "Chen Qin" wrote:
> > >
> > > Hi there,
> > >
> >
Qin" wrote:
> >
> > Hi there,
> >
> > We have use case of allowing ad hoc user submit a Flink job
> (mostly
> > SQL)
> > and user come back and verify results after period of time (eg
> 24hours)
>
se of allowing ad hoc user submit a Flink job (mostly
> SQL)
> and user come back and verify results after period of time (eg
24hours)
> without manual intervention. The idea is to have something like set
job
> level TTL configuration to 24hours. Jobmana
> We have use case of allowing ad hoc user submit a Flink job (mostly
> SQL)
> and user come back and verify results after period of time (eg 24hours)
> without manual intervention. The idea is to have something like set job
> level TTL configuration to 24hours. Job
We have use case of allowing ad hoc user submit a Flink job (mostly SQL)
and user come back and verify results after period of time (eg 24hours)
without manual intervention. The idea is to have something like set job
level TTL configuration to 24hours. Jobmanager will honor
Hi there,
We have use case of allowing ad hoc user submit a Flink job (mostly SQL)
and user come back and verify results after period of time (eg 24hours)
without manual intervention. The idea is to have something like set job
level TTL configuration to 24hours. Jobmanager will honor 24hours of
