[
https://issues.apache.org/jira/browse/OOZIE-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512017#comment-14512017
]
Rohini Palaniswamy commented on OOZIE-1899:
-------------------------------------------
[~rkanter],
We should get rid of fs.glob.max instead of documenting it - OOZIE-1682. To
throw an error after globbing and getting all paths is meaningless. HDFS-985
ensures that NN does not have any problems with large listings. The memory
pressure on Oozie is still there, but throwing an error after fetching all the
paths will not avoid an OOM.
> Improve the documentation for the FS action's glob feature
> ----------------------------------------------------------
>
> Key: OOZIE-1899
> URL: https://issues.apache.org/jira/browse/OOZIE-1899
> Project: Oozie
> Issue Type: Sub-task
> Components: docs
> Affects Versions: trunk, 4.0.0
> Reporter: Robert Kanter
> Fix For: trunk
>
>
> We should add some more detail to the documentation on the FS action's glob
> feature. It currently just says this:
> {quote}
> In case of move , delete , chmod and chgrp commands, a glob pattern can also
> be specified instead of an absolute path. For move , glob pattern can only be
> specified for source path and not the target.
> {quote}
> The user has no idea how to specify a glob pattern after reading this. An
> example would be nice too.
> Also, {{oozie.action.fs.glob.max}} in oozie-site/default is supposed to let
> you specify how many files can be matched against the glob pattern. This
> isn't mentioned anywhere in the documentation and isn't even in oozie-site or
> oozie-default. It should be added to oozie-default.xml and mentioned in the
> docs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
