[SQOOP-2591] Sqoop2: Is there a better way to represent sensitive values in JSON responses from he server?

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 1.99.8
• Assignee: Unassigned
• Reporter: Abraham Fine
• Created: 29/Sep/15 16:46
• Updated: 28/Jul/16 00:13

Description

Currently, if an input is declared sensitive we leave out the "value" field when building the JSON that represents the input.

If the input is a map that has sensitive fields (a feature that was added with SQOOP-2549), we replace the values of sensitive fields with an empty string. This could be confusing from the perspective of the user because the actual value of a field could be the empty string.

It may be clearer to have some placeholder that we use when a value has been redacted due to sensitivity.