[jira] [Resolved] (HADOOP-1994) Variable names generated by Record I/O should not clash with user fields

["Harsh J (JIRA)" <ji...@apache.org>]

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

Harsh J resolved HADOOP-1994.
-----------------------------

    Resolution: Won't Fix

Record IO has been deprecated with the advent of Avro.

Please see HADOOP-6155

Resolving as Won't Fix.

> Variable names generated by Record I/O should not clash with user fields
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-1994
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1994
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Vivek Ratan
>            Assignee: Vivek Ratan
>
> The code (Java and C++) spit out by the Record I/O compiler contains variables. We need to make sure these variable names don't clash with names used by users in the DDL, otherwise the generated code will not compile. Variable names such as 'a', 'peer', etc, are used. We need better names. For example, if I have a DDL of the form
> {code}
> class s1 {
>   int a;
>   boolean peer;
>   int a_;
> }
> {code}
> Both the Java and C++ code will not compile. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira