[jira] [Updated] (NUTCH-1562) Order of execution for scoring filters
[
https://issues.apache.org/jira/browse/NUTCH-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Nagel updated NUTCH-1562:
---
Attachment: NUTCH-1562-trunk.patch.v3
Order of execution for scoring filters
--
Key: NUTCH-1562
URL: https://issues.apache.org/jira/browse/NUTCH-1562
Project: Nutch
Issue Type: Bug
Components: documentation
Affects Versions: 1.6, 2.1
Reporter: Julien Nioche
Fix For: 2.3, 1.8
Attachments: NUTCH-1562-trunk.patch, NUTCH-1562-trunk.patch.v2,
NUTCH-1562-trunk.patch.v3
The documentation in nutch-default.xml states that :
{quote}
property
namescoring.filter.order/name
value/value
descriptionThe order in which scoring filters are applied.
This may be left empty (in which case all available scoring
filters will be applied in the order defined in plugin-includes
and plugin-excludes), or a space separated list of implementation
classes.
/description
/property
{quote}
however if no order is specified the filters are ordered randomly and not in
the order defined in plugin-includes.
The other *order parameters (e.g. urlfilter.order) have a different
documentation and are loaded and applied in system defined order which
corresponds to what the code does.
The patch attached is for 1.x and puts the code in accordance with the
documentation by ordering the filters according to the order of the plugins,
which gives users more control without having to specify the classes
explicitly in scoring.filter.order.
We could extend the same idea to the other *order params.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (NUTCH-1562) Order of execution for scoring filters
[
https://issues.apache.org/jira/browse/NUTCH-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Nioche updated NUTCH-1562:
-
Attachment: NUTCH-1562-trunk.patch.v2
New version which addresses the issue raised by Lufeng. Please give it a try.
Order of execution for scoring filters
--
Key: NUTCH-1562
URL: https://issues.apache.org/jira/browse/NUTCH-1562
Project: Nutch
Issue Type: Bug
Components: documentation
Affects Versions: 1.6, 2.1
Reporter: Julien Nioche
Fix For: 2.3, 1.8
Attachments: NUTCH-1562-trunk.patch, NUTCH-1562-trunk.patch.v2
The documentation in nutch-default.xml states that :
{quote}
property
namescoring.filter.order/name
value/value
descriptionThe order in which scoring filters are applied.
This may be left empty (in which case all available scoring
filters will be applied in the order defined in plugin-includes
and plugin-excludes), or a space separated list of implementation
classes.
/description
/property
{quote}
however if no order is specified the filters are ordered randomly and not in
the order defined in plugin-includes.
The other *order parameters (e.g. urlfilter.order) have a different
documentation and are loaded and applied in system defined order which
corresponds to what the code does.
The patch attached is for 1.x and puts the code in accordance with the
documentation by ordering the filters according to the order of the plugins,
which gives users more control without having to specify the classes
explicitly in scoring.filter.order.
We could extend the same idea to the other *order params.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-1562) Order of execution for scoring filters
[
https://issues.apache.org/jira/browse/NUTCH-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Nagel updated NUTCH-1562:
---
Fix Version/s: 1.8
Order of execution for scoring filters
--
Key: NUTCH-1562
URL: https://issues.apache.org/jira/browse/NUTCH-1562
Project: Nutch
Issue Type: Bug
Components: documentation
Affects Versions: 1.6, 2.1
Reporter: Julien Nioche
Fix For: 2.3, 1.8
Attachments: NUTCH-1562-trunk.patch
The documentation in nutch-default.xml states that :
{quote}
property
namescoring.filter.order/name
value/value
descriptionThe order in which scoring filters are applied.
This may be left empty (in which case all available scoring
filters will be applied in the order defined in plugin-includes
and plugin-excludes), or a space separated list of implementation
classes.
/description
/property
{quote}
however if no order is specified the filters are ordered randomly and not in
the order defined in plugin-includes.
The other *order parameters (e.g. urlfilter.order) have a different
documentation and are loaded and applied in system defined order which
corresponds to what the code does.
The patch attached is for 1.x and puts the code in accordance with the
documentation by ordering the filters according to the order of the plugins,
which gives users more control without having to specify the classes
explicitly in scoring.filter.order.
We could extend the same idea to the other *order params.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-1562) Order of execution for scoring filters
[
https://issues.apache.org/jira/browse/NUTCH-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Nioche updated NUTCH-1562:
-
Attachment: NUTCH-1562-trunk.patch
Patch for trunk
Order of execution for scoring filters
--
Key: NUTCH-1562
URL: https://issues.apache.org/jira/browse/NUTCH-1562
Project: Nutch
Issue Type: Bug
Components: documentation
Affects Versions: 1.6, 2.1
Reporter: Julien Nioche
Fix For: 1.7, 2.2
Attachments: NUTCH-1562-trunk.patch
The documentation in nutch-default.xml states that :
{quote}
property
namescoring.filter.order/name
value/value
descriptionThe order in which scoring filters are applied.
This may be left empty (in which case all available scoring
filters will be applied in the order defined in plugin-includes
and plugin-excludes), or a space separated list of implementation
classes.
/description
/property
{quote}
however if no order is specified the filters are ordered randomly and not in
the order defined in plugin-includes.
The other *order parameters (e.g. urlfilter.order) have a different
documentation and are loaded and applied in system defined order which
corresponds to what the code does.
The patch attached is for 1.x and puts the code in accordance with the
documentation by ordering the filters according to the order of the plugins,
which gives users more control without having to specify the classes
explicitly in scoring.filter.order.
We could extend the same idea to the other *order params.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
