[
https://issues.apache.org/jira/browse/PHOENIX-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568291#comment-14568291
]
Hudson commented on PHOENIX-2012:
---------------------------------
SUCCESS: Integrated in Phoenix-master #775 (See
[https://builds.apache.org/job/Phoenix-master/775/])
PHOENIX-2012 RowKeyComparisonFilter logs unencoded data at DEBUG level
(ndimiduk: rev 9e686b758ff735fd9129430cd31fe36993b9711b)
*
phoenix-core/src/main/java/org/apache/phoenix/filter/RowKeyComparisonFilter.java
> RowKeyComparisonFilter logs unencoded data at DEBUG level
> ---------------------------------------------------------
>
> Key: PHOENIX-2012
> URL: https://issues.apache.org/jira/browse/PHOENIX-2012
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.4.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Minor
> Fix For: 5.0.0, 4.5.0, 4.4.1
>
> Attachments: PHOENIX-2012.00.patch
>
>
> Noticed this while running verification tests. Occasionally the printed tuple
> is interpreted by the shell and mangles the output for the rest of the test.
> IF we're going to log data at all, should really be passing values through
> some kind of ascii encoder. Also, don't print values, and or only do it at
> TRACE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)