HADOOP: fix 'occured' -> 'occurred' typos in 3 files#8439
Conversation
- hadoop-hdfs-native-client/.../thread_local_storage.h: two struct field comments in the libhdfs thread-local-storage header. - hadoop-aws/.../AbstractS3ACommitter.java: @throws Javadoc tag on maybeSaveSummary. - hadoop-mapreduce-client-core/.../ManifestCommitter.java: @throws Javadoc tag on maybeSaveSummary. No functional changes. Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
Thanks for your contribution. Only CI failure was |
|
@ajfabbri, do we want to accept minor changes such as this PR without a JIRA ticket, like |
|
Great question. I wondered the same thing. Do we have an official prefix that we like to use for trivial commits like these? It's not worth filing an issue over but would like to be consistent. |
|
I was asked to create a JIRA ticket for even a minor change in hadoop project, but other projects usually allow |
You are correct. I started a [discuss] thread on common-dev. Thanks for the reminder! |
Trivial spelling fix in three source files —
occured→occurred.All occurrences are in code comments / Javadoc:
hadoop-hdfs-native-client/.../libhdfs/os/thread_local_storage.h— two struct field comments describing the last exception stack trace / root cause.hadoop-aws/.../AbstractS3ACommitter.java—@throws IOExceptionJavadoc onmaybeSaveSummary.hadoop-mapreduce-client-core/.../ManifestCommitter.java—@throws IOExceptionJavadoc onmaybeSaveSummary.No functional changes.