You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Venky Iyer (JIRA)" <ji...@apache.org> on 2009/03/14 00:38:50 UTC
[jira] Created: (HIVE-348) Provide type information to custom
mappers and reducers.
Provide type information to custom mappers and reducers.
--------------------------------------------------------
Key: HIVE-348
URL: https://issues.apache.org/jira/browse/HIVE-348
Project: Hadoop Hive
Issue Type: Improvement
Reporter: Venky Iyer
Either by setting an environment variable with the schema, or (ideally), configurably passing JSON data to custom mappers/reducers. This would be more data to pump into the pipe on each mapper/reducer, but it would be generated on the mapper/reducer, and it may mean much less processing for the custom script (using a fast json library compared to casting each column that needs casting based on the schema).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HIVE-348) Provide type information to custom
mappers and reducers.
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang reassigned HIVE-348:
-------------------------------
Assignee: Ning Zhang
> Provide type information to custom mappers and reducers.
> --------------------------------------------------------
>
> Key: HIVE-348
> URL: https://issues.apache.org/jira/browse/HIVE-348
> Project: Hadoop Hive
> Issue Type: Improvement
> Reporter: Venky Iyer
> Assignee: Ning Zhang
>
> Either by setting an environment variable with the schema, or (ideally), configurably passing JSON data to custom mappers/reducers. This would be more data to pump into the pipe on each mapper/reducer, but it would be generated on the mapper/reducer, and it may mean much less processing for the custom script (using a fast json library compared to casting each column that needs casting based on the schema).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HIVE-348) Provide type information to custom
mappers and reducers.
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang reassigned HIVE-348:
-------------------------------
Assignee: (was: Ning Zhang)
> Provide type information to custom mappers and reducers.
> --------------------------------------------------------
>
> Key: HIVE-348
> URL: https://issues.apache.org/jira/browse/HIVE-348
> Project: Hadoop Hive
> Issue Type: Improvement
> Reporter: Venky Iyer
>
> Either by setting an environment variable with the schema, or (ideally), configurably passing JSON data to custom mappers/reducers. This would be more data to pump into the pipe on each mapper/reducer, but it would be generated on the mapper/reducer, and it may mean much less processing for the custom script (using a fast json library compared to casting each column that needs casting based on the schema).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-348) Provide type information to custom
mappers and reducers.
Posted by "Zheng Shao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733835#action_12733835 ]
Zheng Shao commented on HIVE-348:
---------------------------------
I think we should pass type information in the environment variable.
> Provide type information to custom mappers and reducers.
> --------------------------------------------------------
>
> Key: HIVE-348
> URL: https://issues.apache.org/jira/browse/HIVE-348
> Project: Hadoop Hive
> Issue Type: Improvement
> Reporter: Venky Iyer
>
> Either by setting an environment variable with the schema, or (ideally), configurably passing JSON data to custom mappers/reducers. This would be more data to pump into the pipe on each mapper/reducer, but it would be generated on the mapper/reducer, and it may mean much less processing for the custom script (using a fast json library compared to casting each column that needs casting based on the schema).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.