You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Markus Jelsma (JIRA)" <ji...@apache.org> on 2011/04/05 16:58:06 UTC
[jira] [Created] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
SolrMappingReader uses hardcoded configuration parameter name for mapping file
------------------------------------------------------------------------------
Key: NUTCH-977
URL: https://issues.apache.org/jira/browse/NUTCH-977
Project: Nutch
Issue Type: Bug
Affects Versions: 1.2, 1.3, 2.0
Reporter: Markus Jelsma
Assignee: Markus Jelsma
Fix For: 1.3, 2.0
Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-977:
--------------------------------
Attachment: NUTCH-977-trunk.patch
Fix for trunk
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch, NUTCH-977-trunk.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Julien Nioche (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017379#comment-13017379 ]
Julien Nioche commented on NUTCH-977:
-------------------------------------
Shouldn't MAPPING_FILE be added to SOLRContants as well?
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch, NUTCH-977-trunk.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma resolved NUTCH-977.
---------------------------------
Resolution: Fixed
Committed for trunk in rev. 1092090 for 1.3 in rev. 1092091.
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch, NUTCH-977-trunk.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017387#comment-13017387 ]
Markus Jelsma commented on NUTCH-977:
-------------------------------------
It was added but https://issues.apache.org/jira/browse/NUTCH-976 seems to contain an old patch, i'll update the patch.
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch, NUTCH-977-trunk.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-977:
--------------------------------
Attachment: NUTCH-977-1.3.patch
Fix for 1.3
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma closed NUTCH-977.
-------------------------------
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch, NUTCH-977-trunk.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-977:
--------------------------------
Patch Info: [Patch Available]
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch, NUTCH-977-trunk.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-977) SolrMappingReader uses hardcoded
configuration parameter name for mapping file
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016324#comment-13016324 ]
Markus Jelsma commented on NUTCH-977:
-------------------------------------
Any objections devs? Everythings is working fine with these patches.
> SolrMappingReader uses hardcoded configuration parameter name for mapping file
> ------------------------------------------------------------------------------
>
> Key: NUTCH-977
> URL: https://issues.apache.org/jira/browse/NUTCH-977
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.2, 1.3, 2.0
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.3, 2.0
>
> Attachments: NUTCH-977-1.3.patch, NUTCH-977-trunk.patch
>
>
> Because the SolrMappingReader uses a hard coded value for the name of the mapping file configuration parameter it actually works. It should rely on SolrConstants instead of using a hard coded value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira