[ 
https://issues.apache.org/jira/browse/CAMEL-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079018#comment-17079018
 ] 

Pauli Borodulin commented on CAMEL-12260:
-----------------------------------------

I don't argue against making breaking changes. But we should
 # identify these breaking changes and provide information to the users about 
them and
 # when possible, provide an easy migration path. A possibility to configure 
these default values for types would be a great solution.

As an example of no 1 is that this bug/change should be labeled as a breaking 
change -> ability to automatically provide users a list of changes that 
introduce a breaking change.

> Default value for String field results in null for CSV / Bindy
> --------------------------------------------------------------
>
>                 Key: CAMEL-12260
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12260
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-bindy
>    Affects Versions: 2.20.2
>            Reporter: Pauli Borodulin
>            Assignee: Dmitry Volodin
>            Priority: Minor
>             Fix For: 2.21.0
>
>
> **CAMEL-5018 added "support the set the default value on the field of bindy 
> CVS", which is nice, but the default value is useless for Strings, because 
> BindyCSVFactory turns the empty value to null even when defaultValue = "", see
> [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyCsvFactory.java#L230]
> and
> [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyAbstractFactory.java#L234]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to