You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Adam Kramer (JIRA)" <ji...@apache.org> on 2011/07/27 01:13:11 UTC
[jira] [Created] (HIVE-2311) TRANSFORM statements should come with
their own ROW FORMATs.
TRANSFORM statements should come with their own ROW FORMATs.
------------------------------------------------------------
Key: HIVE-2311
URL: https://issues.apache.org/jira/browse/HIVE-2311
Project: Hive
Issue Type: Improvement
Components: Serializers/Deserializers
Reporter: Adam Kramer
Sometimes Hive tables contain tabs and/or other characters that could easily be misinterpreted by a transformer as a delimiter. This can break many TRANSFORM queries.
The solution is to have a ROW FORMAT semantics that can be attached to an individual TRANSFORM instance. It would have the same semantics as table creation, but during serialization it would ensure that any formal delimiter characters that did not indicate an actual break between columns would be escaped.
At the very least, it is a bug that TRANSFORM statement deserialization does not backslash out literal tabs in the current implementation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2311) TRANSFORM statements should come with
their own ROW FORMATs.
Posted by "Adam Kramer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Kramer updated HIVE-2311:
------------------------------
Priority: Minor (was: Major)
Issue Type: Bug (was: Improvement)
> TRANSFORM statements should come with their own ROW FORMATs.
> ------------------------------------------------------------
>
> Key: HIVE-2311
> URL: https://issues.apache.org/jira/browse/HIVE-2311
> Project: Hive
> Issue Type: Bug
> Components: Serializers/Deserializers
> Reporter: Adam Kramer
> Priority: Minor
>
> Sometimes Hive tables contain tabs and/or other characters that could easily be misinterpreted by a transformer as a delimiter. This can break many TRANSFORM queries.
> The solution is to have a ROW FORMAT semantics that can be attached to an individual TRANSFORM instance. It would have the same semantics as table creation, but during serialization it would ensure that any formal delimiter characters that did not indicate an actual break between columns would be escaped.
> At the very least, it is a bug that TRANSFORM statement deserialization does not backslash out literal tabs in the current implementation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira