[
https://issues.apache.org/jira/browse/NUTCH-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830749#comment-17830749
]
ASF GitHub Bot commented on NUTCH-3032:
---------------------------------------
CatChullain opened a new pull request, #810:
URL: https://github.com/apache/nutch/pull/810
This is the initial code for an arbitrary indexing filter, NUTCH-3032.
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/[email protected]/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.
Ideally a solution to NUTCH-585 would work at parse time, but this index
time code still has potential uses for any kind of look-ups or calculations
that depend on values in the document where the need to manipulate data exceeds
what something like Jexl filter can do easily, or where outside data is worth
incorporating into the document for use after indexing.
Thanks for your contribution to [Apache Nutch](https://nutch.apache.org/)!
Your help is appreciated!
Before opening the pull request, please verify that
* there is an open issue on the [Nutch issue
tracker](https://issues.apache.org/jira/projects/NUTCH) which describes the
problem or the improvement. We cannot accept pull requests without an issue
because the change wouldn't be listed in the release notes.
* the issue ID (`NUTCH-XXXX`)
- is referenced in the title of the pull request
- and placed in front of your commit messages surrounded by square
brackets (`[NUTCH-XXXX] Issue or pull request title`)
* commits are squashed into a single one (or few commits for larger changes)
* Java source code follows [Nutch Eclipse Code Formatting
rules](https://github.com/apache/nutch/blob/master/eclipse-codeformat.xml)
* Nutch is successfully built and unit tests pass by running `ant clean
runtime test`
* there should be no conflicts when merging the pull request branch into the
*recent* master branch. If there are conflicts, please try to rebase the pull
request branch on top of a freshly pulled master branch.
* if new dependencies are added,
- are these dependencies licensed in a way that is compatible for
inclusion under [ASF
2.0](https://www.apache.org/legal/resolved.html#category-a)?
- are `LICENSE-binary` and `NOTICE-binary` updated accordingly?
We will be able to faster integrate your pull request if these conditions
are met. If you have any questions how to fix your problem or about using Nutch
in general, please sign up for the [Nutch mailing
list](https://nutch.apache.org/mailing_lists.html). Thanks!
> 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
> Attachments: NUTCH-3032.patch
>
>
> 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/[email protected]/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)
