[
https://issues.apache.org/jira/browse/HADOOP-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682323#action_12682323
]
Enis Soztutar commented on HADOOP-5307:
---------------------------------------
bq. Neither of us has enough data to assert anything about the frequency of any
case because it's a public class. While my intuition matches yours,
"incompatible change" isn't a statistical definition, let alone one based on
our expectations.
Wish we had resolved HADOOP-5073, which will hopefully classify the "gray
areas" in the code.
bq. Not sure. Since this seems to be serializing an array in and out of
configs, I'm leaning towards the Stringifier work as a solution local to
DBConfiguration. Would that work?
I have opened HADOOP-5073, to fix the issue in DB context. I will close this
one as won't fix. If any other use case occurs for stringifying possible null
object(s), we can reopen this one.
> Fix null value handling in StringUtils#arrayToString() and #getStrings()
> ------------------------------------------------------------------------
>
> Key: HADOOP-5307
> URL: https://issues.apache.org/jira/browse/HADOOP-5307
> Project: Hadoop Core
> Issue Type: Bug
> Components: util
> Affects Versions: 0.21.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Attachments: h5307_v1.patch
>
>
> StringUtils#arrayToString() converts String array to a String of comma
> separated elements. If the String array includes null values, these are
> recovered as "null" (literal) from getStrings() method, which eventually
> causes configuration issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
