[
https://issues.apache.org/jira/browse/NUTCH-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832471#comment-17832471
]
ASF GitHub Bot commented on NUTCH-3032:
---------------------------------------
lewismc commented on PR #810:
URL: https://github.com/apache/nutch/pull/810#issuecomment-2028304406
@CatChullain thanks for your patience whilst we work this one 👍
> … I wonder where might be good spots for INFO level messages
The reason I suggested that the log level be revised from `INFO` to `DEBUG`
was that any logging needs to make sense in the context of the entire log. Said
another way, plugin logging needs to complement the core crawler tasks.
That being said, if you want to include `INFO` for the following scenarios
then please go ahead.
* recording the count value, and
* indicating when overwrite is true
Your rationale is sound.
> 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/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)
