[
https://issues.apache.org/jira/browse/HDFS-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556425#comment-14556425
]
Allen Wittenauer commented on HDFS-8382:
----------------------------------------
bq. I think the solution will be like having a separate maven repo for each
jenkins project to avoid the collisions, even though results in duplicate
contents of repo.
This is on my list of things to do, but it's going to be a while.
HADOOP-11933 and HADOOP-11929 take first priority since they have much bigger
impacts. (In fact, we pretty much can't do separate maven repos in any sort of
sane way until HADOOP-11933 anyway, without a ton of extra gymnastics in
test-patch.sh)
> Remove chunkSize parameter from initialize method of raw erasure coder
> ----------------------------------------------------------------------
>
> Key: HDFS-8382
> URL: https://issues.apache.org/jira/browse/HDFS-8382
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Kai Zheng
> Attachments: HDFS-8382-HDFS-7285-v1.patch,
> HDFS-8382-HDFS-7285-v2.patch, HDFS-8382-HDFS-7285-v3.patch,
> HDFS-8382-HDFS-7285-v4.patch, HDFS-8382-HDFS-7285-v5.patch,
> HDFS-8382-HDFS-7285-v6.patch
>
>
> Per discussion in HDFS-8347, we need to support encoding/decoding variable
> width units data instead of predefined fixed width like {{chunkSize}}. Have
> this issue to remove chunkSize in the general raw erasure coder API. Specific
> coder will support fixed chunkSize using hard-coded or specific schema
> customizing way if necessary, like HitchHiker coder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
