[
https://issues.apache.org/jira/browse/FLINK-34389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels updated FLINK-34389:
---------------------------------------
Fix Version/s: kubernetes-operator-1.9.0
(was: kubernetes-operator-1.8.0)
> JdbcAutoscalerStateStore explicitly writes update_time
> ------------------------------------------------------
>
> Key: FLINK-34389
> URL: https://issues.apache.org/jira/browse/FLINK-34389
> Project: Flink
> Issue Type: Improvement
> Components: Autoscaler
> Affects Versions: kubernetes-operator-1.8.0
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.9.0
>
>
> JdbcAutoscalerStateStore explicitly writes update_time instead of relying on
> the database to update.
> Some databases doesn't support update the timestamp column automatically. For
> example, Derby doesn't support update the update_time automatically when we
> update any data. It's hard to do a general test during I developing the test
> for JdbcAutoscalerEventHandler.
>
> As the common&open source service, in order to support all databases well,
> it's better to handle it inside of the service.
>
> In order to unify the design for JdbcAutoscalerEventHandler and
> JdbcAutoscalerStateStore, we update the design of JdbcAutoscalerStateStore in
> this JIRA.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
