Hi devs, I'd like to start a discussion on FLIP-292: Support configuring state TTL at operator level for Table API & SQL programs [1].
Currently, we only support job-level state TTL configuration via 'table.exec.state.ttl'. However, users may expect a fine-grained state TTL control to optimize state usage. Hence we propose to serialize/deserialize the state TTL as metadata of the operator's state to/from the compiled JSON plan, to achieve the goal that specifying different state TTL when transforming the exec node to stateful operators. Look forward to your opinions! [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240883951 Best Regards, Jane Chan
