Scott,
I should have read your original post in more detail. I was assuming
you were just trying to get the root directory of the plugin, not
loading resources during a MR job. I would have to agree with Andrzej
approach if this were to be used during a MR job. Sorry for the confusion.
Scott Green wrote:
Thanks Dennis! Your methond should work.
And I really hope there is one directly method say getPluginRootDir()
in the plugin implementation.
I'd recommend taking path shown by Andrzej because IMO it's bad design
to depend on plugin system from a plugin.
--
Sami Siren
Hi Sami
On 1/16/07, Sami Siren [EMAIL PROTECTED] wrote:
Scott Green wrote:
Thanks Dennis! Your methond should work.
And I really hope there is one directly method say getPluginRootDir()
in the plugin implementation.
I'd recommend taking path shown by Andrzej because IMO it's bad design
to
Scott Green wrote:
Hi Sami
On 1/16/07, Sami Siren [EMAIL PROTECTED] wrote:
Scott Green wrote:
Thanks Dennis! Your methond should work.
And I really hope there is one directly method say getPluginRootDir()
in the plugin implementation.
I'd recommend taking path shown by Andrzej because IMO
On 1/16/07, Andrzej Bialecki [EMAIL PROTECTED] wrote:
Scott Green wrote:
Hi Sami
On 1/16/07, Sami Siren [EMAIL PROTECTED] wrote:
Scott Green wrote:
Thanks Dennis! Your methond should work.
And I really hope there is one directly method say getPluginRootDir()
in the plugin
Scott Green wrote:
Well, why should all resources needed to be packed?
Because when you run Nutch on a Hadoop cluster, Hadoop requires that all
job resources be packed into a job JAR, which is then submitted to each
tasktracker as a part of the job. So, if you want to run in non-local
mode
Andrzej Bialecki wrote:
The reason is that if you pack this file into your job JAR, the job jar
would become very large (presumably this 40MB is already compressed?).
Job jar needs to be copied to each tasktracker for each task, so you
will experience performance hit just because of the size
Thanks Andrzej and Doug!
I will try both in my later work and evaluate them.
On 1/17/07, Doug Cutting [EMAIL PROTECTED] wrote:
Andrzej Bialecki wrote:
The reason is that if you pack this file into your job JAR, the job jar
would become very large (presumably this 40MB is already
Can someone give a answer? I dont think it is good idea we put all
configuration/resources under conf dir.
On 1/15/07, Scott Green [EMAIL PROTECTED] wrote:
Hi,
I need to load some resources from mine plugin's sub-directory. Any
avaiable method to get the specified plugin's root directory now?
Scott Green wrote:
Can someone give a answer? I dont think it is good idea we put all
configuration/resources under conf dir.
On 1/15/07, Scott Green [EMAIL PROTECTED] wrote:
Hi,
I need to load some resources from mine plugin's sub-directory. Any
avaiable method to get the specified plugin's
You can get the PluginRepository and then from there get the plugin
descriptor and its path. From there resources inside the plugin folder.
Change out parse-html with your plugin id.
Configuration conf = NutchConfiguration.create();
PluginRepository rep =
Hi,
I want to propose a bit clean plugin directory structure:
xxx-plugin
`-- lib
`-- conf
`-- src
`-- web (only for web plugin)
`-- plugin.xml
`-- build.xml
Take urlfilter-regex plugin as example, the
Thanks Dennis! Your methond should work.
And I really hope there is one directly method say getPluginRootDir()
in the plugin implementation.
On 1/16/07, Dennis Kubes [EMAIL PROTECTED] wrote:
You can get the PluginRepository and then from there get the plugin
descriptor and its path. From
Hi,
I need to load some resources from mine plugin's sub-directory. Any
avaiable method to get the specified plugin's root directory now?
thanks
- scott
14 matches
Mail list logo