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

Carl Steinbach updated HIVE-99:
-------------------------------

      Component/s: Serializers/Deserializers
    Fix Version/s:     (was: 0.6.0)
                   0.3.0

> serde fails when field name starts with underscore
> --------------------------------------------------
>
>                 Key: HIVE-99
>                 URL: https://issues.apache.org/jira/browse/HIVE-99
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>            Reporter: Michi Mutsuzaki
>            Priority: Minor
>             Fix For: 0.3.0
>
>
> (Not sure if this is a metastore bug or serde bug)
> For the query:
> select count(1) from table
> HiveInterface.getSchema() returns:
> struct result { string _c0}
> DynamicSerDe.initialize() raises a lexical error:
>     [junit] Lexical error at line 1, column 24.  Encountered: "_" (95), after 
> : ""
>     [junit] org.apache.hadoop.hive.serde2.dynamic_type.TokenMgrError: Lexical 
> error at line 1, column 24.  Encountered: "_" (95), after : ""
>     [junit]   at 
> org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammarTokenManager.getNextToken(thrift_grammarTokenManager.java:1457)
>     [junit]   at 
> org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.jj_consume_token(thrift_grammar.java:2233)
>     [junit]   at 
> org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.Field(thrift_grammar.java:1547)
>     [junit]   at 
> org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.FieldList(thrift_grammar.java:1501)
>     [junit]   at 
> org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.Struct(thrift_grammar.java:1171)
>     [junit]   at 
> org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.TypeDefinition(thrift_grammar.java:497)
>     [junit]   at 
> org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.Definition(thrift_grammar.java:439)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to