You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Abraham Fine (JIRA)" <ji...@apache.org> on 2015/09/29 18:47:04 UTC
[jira] [Created] (SQOOP-2591) Sqoop2: Is there a better way to
represent sensitive values in JSON responses from he server?
Abraham Fine created SQOOP-2591:
-----------------------------------
Summary: Sqoop2: Is there a better way to represent sensitive values in JSON responses from he server?
Key: SQOOP-2591
URL: https://issues.apache.org/jira/browse/SQOOP-2591
Project: Sqoop
Issue Type: Bug
Reporter: Abraham Fine
Priority: Minor
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)