[ 
https://issues.apache.org/jira/browse/HIVE-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655194#comment-13655194
 ] 

Prasad Mujumdar commented on HIVE-4505:
---------------------------------------

[~owen.omalley] My concern was that the way session handle is constructed 
(userid+VMid+date), there's still a possibility of running into conflict. But 
still what we have is better than what's on trunk before. I am fine with 
Gunther's patch for that case. 
For CLI case, this might be a bit of problem to leave behind a new directory on 
each invocation. The users have a workaround of changing the configuration back 
to the old default. You might want to consider either restoring the default or 
just adding Sessionstate.close() for the -f case.

Anyway, I am fine with keeping Gunther's patch in the RC. If are going to 
commit that patch, then I can log a follow up ticket for 0.12.

Again, my apologies for not addressing the review comments sooner for the 
blocker issue.
                
> Hive can't load transforms added using 'ADD FILE'
> -------------------------------------------------
>
>                 Key: HIVE-4505
>                 URL: https://issues.apache.org/jira/browse/HIVE-4505
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.11.0
>            Reporter: Prasad Mujumdar
>            Assignee: Prasad Mujumdar
>            Priority: Blocker
>             Fix For: 0.11.0
>
>         Attachments: HIVE-4505-1.patch, HIVE-4505.2.patch, HIVE-4505-3.patch
>
>
> ADD FILE mangles name of the resource when copying to resource download 
> directory. As a results following doesn't work:
> {code:sql}
> ADD FILE test.py;
> SELECT TRANSFORM (id) USING 'python test.py' AS b FROM tab1;
> {code}
> The resource gets added with a different name every time which makes it 
> impossible to use transform in non-interactive mode.
> This seems to be due to HIVE-3431

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to