[
https://issues.apache.org/jira/browse/NUTCH-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825855#comment-17825855
]
Joe Gilvary edited comment on NUTCH-3032 at 3/12/24 11:06 PM:
--
I have the code cleaned up and a few Junit tests. When I follow the
instructions at https://github.com/apache/nutch/tree/master for contributing,
git tells me it doesn't recognize 'fork' ('is not a git command'). Before I do
something gittish that will be difficult to remedy, I figured I'd ask for
advice. :) Do I just push now, or is there some other version of fork I should
be using?
was (Author: JIRAUSER304553):
I have the code cleaned up and a few Junit tests. When I follow the
instructions at https://github.com/apache/nutch/tree/master for contributing,
git tells me it doesn't recognize 'fork' is not a git command. Before I do
something gittish that will be difficult to remedy, I figured I'd ask for
advice. :) Do I just push now, or is there some other version of fork I should
be using?
> Indexing plugin as an adapter for end user's own POJO instances
> ---
>
> Key: NUTCH-3032
> URL: https://issues.apache.org/jira/browse/NUTCH-3032
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
>Reporter: Joe Gilvary
>Priority: Major
> Labels: indexing
>
> It could be helpful to let end users manipulate information at indexing time
> with their own code without the need for writing their own indexing plugin. I
> mentioned this on the dev mailing list
> (https://www.mail-archive.com/dev@nutch.apache.org/msg31190.html) with some
> description of my work in progress.
> One potential use is to address some of the same concerns that NUTCH-585
> discusses regarding an alternative approach to picking and choosing which
> content to index, but this approach would allow making index time decisions,
> rather than setting the configuration for all content at the start of the
> indexing run.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
