You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2021/05/24 14:29:00 UTC

[jira] [Closed] (TINKERPOP-2571) Remove actual arguments from exception message in JavaTranslator

     [ https://issues.apache.org/jira/browse/TINKERPOP-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Mallette closed TINKERPOP-2571.
---------------------------------------
    Resolution: Invalid

oops - looks like this change was already put in place as CTR: https://github.com/apache/tinkerpop/commit/8bdde85d5d743c0f70ec771cce1d4ead7324e0b6#diff-f6f59e8db09cfc8b3f247766f303b6eeaea3dfd158d27d3872d75e841c701584

> Remove actual arguments from exception message in JavaTranslator
> ----------------------------------------------------------------
>
>                 Key: TINKERPOP-2571
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2571
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.4.11
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Minor
>
> {{JavaTranslator}} currently generate exceptions with messages that display the values of arguments that failed to be called for a particular step. That's helpful to debugging but could share too much information to logs if those arguments contain some form of private data. Instead of including the argument values, instead output their types so that the debug information is still meaningful, but the data itself stays hidden.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)