[
https://issues.apache.org/jira/browse/SQOOP-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651008#comment-14651008
]
Yibing Shi commented on SQOOP-2440:
-----------------------------------
Thanks, [~jarcec]!
I have checked the attached unit test output and found the failed test is
{{testNonstandardCharactersInColumnName}}. The error is as below:
{noformat}
/home/jenkins/jenkins-slave/workspace/Sqoop-ant-jdk-1.6-hadoop200/build/test/data/sqoop-jenkins/compile/ffa4f8aee4b803bc92379142a8409d8a/IMPORT_TABLE_1.java:41:
';' expected
private Integer AVRO?1;
^
/home/jenkins/jenkins-slave/workspace/Sqoop-ant-jdk-1.6-hadoop200/build/test/data/sqoop-jenkins/compile/ffa4f8aee4b803bc92379142a8409d8a/IMPORT_TABLE_1.java:42:
';' expected
public Integer get_AVRO?1() {
^
{noformat}
In the source code of {{TestAvroImport.testNonstandardCharactersInColumnName}},
we can find below lines:
{code}
String [] names = { "avro\uC3A11" };
String [] types = { "INT" };
String [] vals = { "1987" };
createTableWithColTypesAndNames(names, types, vals);
{code}
It looks like that somehow Jenkins/HSQLDB somehow changes the unicode char
{{\uC3A1}} to {{?}} (question mark), which is a Java reserved key word and thus
make the whole column name invalid.
I will look further into this.
> Fix the unit test failure caused by the changes from SQOOP-1094
> ---------------------------------------------------------------
>
> Key: SQOOP-2440
> URL: https://issues.apache.org/jira/browse/SQOOP-2440
> Project: Sqoop
> Issue Type: Bug
> Components: build
> Reporter: Yibing Shi
> Assignee: Yibing Shi
> Attachments: TEST-com.cloudera.sqoop.TestAvroImport.txt
>
>
> After SQOOP-1094 is committed to trunk, Jenkins build fails, although {{ant
> test}} succeeds on local boxes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
