[
https://issues.apache.org/jira/browse/SQOOP-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693256#comment-14693256
]
Hudson commented on SQOOP-2451:
-------------------------------
SUCCESS: Integrated in Sqoop2 #866 (See
[https://builds.apache.org/job/Sqoop2/866/])
SQOOP-2451: Sqoop2: Findbugs: Add explicit charset to client ResourceRequest
class (rzhou1:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=9e4c1b671c119e15bf5585423fd0bc2c67cbe4f5)
* client/src/main/java/org/apache/sqoop/client/request/ResourceRequest.java
> Sqoop2: Findbugs: Add explicit charset to client ResourceRequest class
> ----------------------------------------------------------------------
>
> Key: SQOOP-2451
> URL: https://issues.apache.org/jira/browse/SQOOP-2451
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2451.patch
>
>
> I feel that this one is quite valid concern - we're not explicitly specifying
> what encoding we're using when serializing/deserializing data. We're
> depending on the default UTF-8 being set, which is not optimal as some users
> can change that and then things will break.
> I'll attach class to fix this in the {{client}} module and will fix other
> module as I'll get to them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
