[
https://issues.apache.org/jira/browse/NIFI-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580857#comment-14580857
]
Mark Payne commented on NIFI-642:
---------------------------------
Hi Tim,
Thanks for contributing this. Can you explain the motivation here? My guess is
that the intent is to allow arbitrary compression mechanisms that were not
originally part of the Allowable Values?
The problem that I have with this approach is that the user now has to know the
fully qualified classname of the desired compression codec. This might be okay
for a hadoop developer, but many of the users of NiFi are not developers at all
but have more sys admin/operations types of roles. I don't know if requiring
the user to come up with the appropriate classname is worth the tradeoff. It is
easy enough to simply update the Allowable Values to include new compression
codecs as needed.
Do others have thoughts on this?
Thanks
-Mark
> Eliminate hardcoded HDFS compression codec classnames.
> ------------------------------------------------------
>
> Key: NIFI-642
> URL: https://issues.apache.org/jira/browse/NIFI-642
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Tim Reardon
> Priority: Minor
> Fix For: 0.2.0
>
>
> Available HDFS compression codec classes were hardcoded as part of NIFI-600.
> This ticket will allow PutHDFS to discover the available codecs via
> CompressionCodecFactory, and allow GetHDFS to choose the codec to use based
> on file extension.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
