[jira] [Updated] (HUDI-2544) Use standard builder pattern to refactor ConfigProperty
[ https://issues.apache.org/jira/browse/HUDI-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Sumit updated HUDI-2544: -- Fix Version/s: 0.12.1 (was: 0.12.0) > Use standard builder pattern to refactor ConfigProperty > --- > > Key: HUDI-2544 > URL: https://issues.apache.org/jira/browse/HUDI-2544 > Project: Apache Hudi > Issue Type: Improvement > Components: code-quality, configs >Reporter: Yann Byron >Assignee: Yann Byron >Priority: Minor > Fix For: 0.12.1 > > > I notice that currently define a ConfigProperty object by non-standard > builder pattern. Only `defaultValue` and `noDefaultValue` methods are > executed in `PropertyBuilder`. > > And when call `withAlternatives`, `sinceVersion`, `deprecatedAfter`, > `withInferFunction` methods, will create another ConfigProperty object even > that will be collected by jvm later. > > So, is it necessary to minor-refactor this? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-2544) Use standard builder pattern to refactor ConfigProperty
[ https://issues.apache.org/jira/browse/HUDI-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-2544: - Priority: Minor (was: Major) > Use standard builder pattern to refactor ConfigProperty > --- > > Key: HUDI-2544 > URL: https://issues.apache.org/jira/browse/HUDI-2544 > Project: Apache Hudi > Issue Type: Improvement > Components: code-quality, configs >Reporter: Yann Byron >Assignee: Yann Byron >Priority: Minor > Fix For: 0.12.0 > > > I notice that currently define a ConfigProperty object by non-standard > builder pattern. Only `defaultValue` and `noDefaultValue` methods are > executed in `PropertyBuilder`. > > And when call `withAlternatives`, `sinceVersion`, `deprecatedAfter`, > `withInferFunction` methods, will create another ConfigProperty object even > that will be collected by jvm later. > > So, is it necessary to minor-refactor this? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HUDI-2544) Use standard builder pattern to refactor ConfigProperty
[ https://issues.apache.org/jira/browse/HUDI-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-2544: - Component/s: code-quality Epic Link: HUDI-1239 > Use standard builder pattern to refactor ConfigProperty > --- > > Key: HUDI-2544 > URL: https://issues.apache.org/jira/browse/HUDI-2544 > Project: Apache Hudi > Issue Type: Improvement > Components: code-quality, configs >Reporter: Yann Byron >Assignee: Yann Byron >Priority: Major > Fix For: 0.12.0 > > > I notice that currently define a ConfigProperty object by non-standard > builder pattern. Only `defaultValue` and `noDefaultValue` methods are > executed in `PropertyBuilder`. > > And when call `withAlternatives`, `sinceVersion`, `deprecatedAfter`, > `withInferFunction` methods, will create another ConfigProperty object even > that will be collected by jvm later. > > So, is it necessary to minor-refactor this? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-2544) Use standard builder pattern to refactor ConfigProperty
[ https://issues.apache.org/jira/browse/HUDI-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-2544: - Fix Version/s: 0.12.0 (was: 0.11.0) > Use standard builder pattern to refactor ConfigProperty > --- > > Key: HUDI-2544 > URL: https://issues.apache.org/jira/browse/HUDI-2544 > Project: Apache Hudi > Issue Type: Improvement > Components: configs >Reporter: Yann Byron >Assignee: Yann Byron >Priority: Major > Fix For: 0.12.0 > > > I notice that currently define a ConfigProperty object by non-standard > builder pattern. Only `defaultValue` and `noDefaultValue` methods are > executed in `PropertyBuilder`. > > And when call `withAlternatives`, `sinceVersion`, `deprecatedAfter`, > `withInferFunction` methods, will create another ConfigProperty object even > that will be collected by jvm later. > > So, is it necessary to minor-refactor this? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-2544) Use standard builder pattern to refactor ConfigProperty
[ https://issues.apache.org/jira/browse/HUDI-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen updated HUDI-2544: - Fix Version/s: (was: 0.10.0) > Use standard builder pattern to refactor ConfigProperty > --- > > Key: HUDI-2544 > URL: https://issues.apache.org/jira/browse/HUDI-2544 > Project: Apache Hudi > Issue Type: Improvement > Components: configs >Reporter: Yann Byron >Priority: Major > Fix For: 0.11.0 > > > I notice that currently define a ConfigProperty object by non-standard > builder pattern. Only `defaultValue` and `noDefaultValue` methods are > executed in `PropertyBuilder`. > > And when call `withAlternatives`, `sinceVersion`, `deprecatedAfter`, > `withInferFunction` methods, will create another ConfigProperty object even > that will be collected by jvm later. > > So, is it necessary to minor-refactor this? -- This message was sent by Atlassian Jira (v8.20.1#820001)
