[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-08-11 Thread Richard Ding (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Ding updated PIG-103:
-

Tags: documentation

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
>Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: conf_tmp_dir.patch, conf_tmp_dir_2.patch
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-08-09 Thread Richard Ding (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Ding updated PIG-103:
-

  Status: Resolved  (was: Patch Available)
Hadoop Flags: [Reviewed]
  Resolution: Fixed

The patch committed to the trunk. Thanks Niraj.

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
>Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: conf_tmp_dir.patch, conf_tmp_dir_2.patch
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-08-09 Thread niraj rai (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

niraj rai updated PIG-103:
--

Status: Patch Available  (was: Open)

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
>Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: conf_tmp_dir.patch, conf_tmp_dir_2.patch
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-08-09 Thread niraj rai (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

niraj rai updated PIG-103:
--

Attachment: conf_tmp_dir_2.patch

Implemented the review recommendations.

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
>Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: conf_tmp_dir.patch, conf_tmp_dir_2.patch
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-08-09 Thread niraj rai (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

niraj rai updated PIG-103:
--

Status: Open  (was: Patch Available)

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
>Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: conf_tmp_dir.patch
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-08-05 Thread niraj rai (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

niraj rai updated PIG-103:
--

Status: Patch Available  (was: Open)

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
>Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: conf_tmp_dir.patch
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-08-05 Thread niraj rai (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

niraj rai updated PIG-103:
--

Attachment: conf_tmp_dir.patch

This patch is to make the pig temp directory for the intermediate data 
configurable.

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
>Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: conf_tmp_dir.patch
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (PIG-103) Shared Job /tmp location should be configurable

2010-07-09 Thread Olga Natkovich (JIRA)

 [ 
https://issues.apache.org/jira/browse/PIG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olga Natkovich updated PIG-103:
---

Fix Version/s: 0.8.0

> Shared Job /tmp location should be configurable
> ---
>
> Key: PIG-103
> URL: https://issues.apache.org/jira/browse/PIG-103
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
> Environment: Partially shared file:// filesystem (eg NFS)
>Reporter: Craig Macdonald
> Fix For: 0.8.0
>
>
> Hello,
> I'm investigating running pig in an environment where various parts of the 
> file:// filesystem are available on all nodes. I can tell hadoop to use a 
> file:// file system location for it's default, by seting 
> fs.default.name=file://path/to/shared/folder
> However, this creates issues for Pig, as Pig writes it's job information in a 
> folder that it assumes is a shared FS (eg DFS). However, in this scenario 
> /tmp is not shared on each machine.
> So /tmp should either be configurable, or Hadoop should tell you the actual 
> full location set in fs.default.name?
> Straightforward solution is to make "/tmp/" a property in 
> src/org/apache/pig/impl/io/FileLocalizer.java init(PigContext)
> Any suggestions of property names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.