[
https://issues.apache.org/jira/browse/FLINK-30590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655414#comment-17655414
]
Nicholas Jiang edited comment on FLINK-30590 at 1/6/23 11:54 AM:
-----------------------------------------------------------------
[~zjureel], IMO, it's needed for users to reduce the user-defined
configurations, for example, setting `scan.timestamp-millis` means that the
scan mode is FROM_TIMESTAMP, not the default value `DEFAULT` of the scan mode.
The manual `CoreOptions.setDefaultValues` helps users to set the default value
of the certain configuration. What default value may cause wrong error
information?
`
was (Author: nicholasjiang):
[~zjureel], IMO, it's needed for users to reduce the user-defined
configurations, for example, setting `scan.timestamp-millis` means that the
scan mode is FROM_TIMESTAMP. The manual `CoreOptions.setDefaultValues` helps
users to set the default value of the certain configuration. What default value
may cause wrong error information?
`
> Remove set default value manually for table options
> ---------------------------------------------------
>
> Key: FLINK-30590
> URL: https://issues.apache.org/jira/browse/FLINK-30590
> Project: Flink
> Issue Type: Improvement
> Components: Table Store
> Affects Versions: table-store-0.4.0
> Reporter: Shammon
> Priority: Major
>
> Remove set default value manually in `CoreOptions.setDefaultValues` which may
> cause wrong error information and it's not needed anymore
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
