[
https://issues.apache.org/jira/browse/HIVE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788531#action_12788531
]
Namit Jain commented on HIVE-946:
---------------------------------
Looks good - but can you add few more tests.
1. Dont set the variable hive.script.operator.id.env.var - write a script which
actually uses $HIVE_SCRIPT_OPERATOR_ID
(not the select clause).
2.
<name>hive.script.operator.id.env.var</name>
297
<value>HIVE_SCRIPT_OPERATOR_ID</value>
298 <description> Name of the
environment variable within the script's process
that holds the unique script operator ID.
299 </description>
300 </property>
Add more description here.
It is the
Name of the environment variable that holds the unique script operator ID in
the user's transform function
(the custom mapper/reducer that the user has specified in the query)
> pass context to custom mapper/reducer
> -------------------------------------
>
> Key: HIVE-946
> URL: https://issues.apache.org/jira/browse/HIVE-946
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Paul Yang
> Attachments: HIVE-946.1.patch
>
>
> It might be useful to pass some context to custom mapper/reducer process -
> the requirement is to identify the transform uniquely if there are multiple
> transforms in the same task.
> For that, we can pass the operator id of the script operator in some
> environment variable.
> If anything else is useful, please add to the list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
