[
https://issues.apache.org/jira/browse/FLINK-36145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876532#comment-17876532
]
Gyula Fora commented on FLINK-36145:
------------------------------------
[~mateczagany] let's hold off on this for a little bit, I would like to ask 1-2
people just to get it right.
On a second thought, snapshotReference feels a little off.
Previously we had initialSavepointPath which was pretty straightforward.
Maybe initialStateReference is more descriptive. Or stateReference if we want
shorter but that may be a bit misleading given the behaviour.
[~thw] [~rmetzger] any thoughts?
> Change JobSpec.flinkStateSnapshotReference to snapshotReference
> ---------------------------------------------------------------
>
> Key: FLINK-36145
> URL: https://issues.apache.org/jira/browse/FLINK-36145
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Blocker
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.10.0
>
>
> To avoid redundant / verbose naming we should change this field name in the
> spec before it's released:
> JobSpec.flinkStateSnapshotReference -> JobSpec.snapshotReference or
> JobSpec.stateSnapshotReference
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
