[
https://issues.apache.org/jira/browse/HADOOP-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628944#action_12628944
]
Ashish Thusoo commented on HADOOP-4085:
---------------------------------------
Yes. we should be checking for valid character sets at SemanitcAnalysis and not
at parse. By encoding charSetName as a list of char sets we are gauranteeing
that in future we will have to change the parse code as we add more
characterset support. That does not scale. In my opinion, parse should just
encode rules on what can be construed as a valid characterset name (valid by
construction). Checking on the actual list of names that we support should be
done at semantic analysis time.
> internationalization support and sort order (ascedning/descending) support in
> create table
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-4085
> URL: https://issues.apache.org/jira/browse/HADOOP-4085
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hive
> Reporter: Namit Jain
> Assignee: Namit Jain
> Attachments: patch1
>
>
> User cannot specify utf8 strings in the query, both for selection and
> filtering. Mysql syntax should be followed:
> select _utf8 'string' from <TableName>
> select <selectExpr> from <TableName> where col = _utf8 0x<HexValue>
> To start with, utf8 strings should be supported. Support for other character
> sets can be added in the future on demand.
> The identifiers (table name/column name etc.) cannot be utf8 strings, it is
> only for the data values.
> Although, in create table, the user has the option of specifying sorted
> columns, he does not have the option of specifying whether they are ascending
> or descending.
> Create Table syntax should be enhanced to support that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
