[
https://issues.apache.org/jira/browse/HADOOP-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429747#comment-15429747
]
Chris Nauroth commented on HADOOP-13528:
----------------------------------------
This came up in the context of a discussion on Spark populating the caller
context. I advised against that value using spaces. (Comment pasted below.)
Space is one example of a character that can make machine parsing of the audit
log more difficult. This JIRA should explore the topic in more detail, define
acceptable characters and any other expectations, describe it in JavaDocs, and
enforce it with validation logic in the code.
{quote}
>From the HDFS perspective, we recommend against using spaces in the value of
>the caller context. The HDFS audit log frequently gets parsed by
>administrators using ad-hoc scripting. Spaces in the fields can make this more
>challenging for them. For example, if they used an awk script that parsed $NF
>expecting to find the callerContext, then the "on Spark" at the end would
>cause it to return "Spark" instead of the full caller context.
{quote}
> Define acceptable grammar for values of caller context and enforce validation
> in code.
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-13528
> URL: https://issues.apache.org/jira/browse/HADOOP-13528
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Reporter: Chris Nauroth
>
> The caller context is a value supplied by applications and included in HDFS
> audit log entries. The scope of this issue is to define a constrained
> grammar for those values and enforce it with validation logic in the code.
> Since the values reach the HDFS audit log, there is an expectation that the
> values need to be easily machine parseable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
