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/06/22 13:06:47 UTC
[jira] [Created] (NUTCH-1010) ContentLength not trimmed
ContentLength not trimmed
-------------------------
Key: NUTCH-1010
URL: https://issues.apache.org/jira/browse/NUTCH-1010
Project: Nutch
Issue Type: Bug
Components: indexer
Reporter: Markus Jelsma
Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
{code}
Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
SEVERE: java.lang.NumberFormatException: For input string: "32717 "
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Long.parseLong(Long.java:419)
at java.lang.Long.parseLong(Long.java:468)
{code}
This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NUTCH-1010) ContentLength not trimmed
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma resolved NUTCH-1010.
----------------------------------
Resolution: Fixed
Committed for 1.4 in rev. 1139307 and for trunk in rev. 1139308.
> ContentLength not trimmed
> -------------------------
>
> Key: NUTCH-1010
> URL: https://issues.apache.org/jira/browse/NUTCH-1010
> Project: Nutch
> Issue Type: Bug
> Components: indexer
> Affects Versions: 1.3, 1.4
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.4, 2.0
>
> Attachments: NUTCH-1010-1.4.patch, NUTCH-1010-2.0.patch
>
>
> Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
> {code}
> Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "32717 "
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:419)
> at java.lang.Long.parseLong(Long.java:468)
> {code}
> This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-1010) ContentLength not trimmed
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-1010:
---------------------------------
Attachment: NUTCH-1010-1.4.patch
Patch for 1.4.
> ContentLength not trimmed
> -------------------------
>
> Key: NUTCH-1010
> URL: https://issues.apache.org/jira/browse/NUTCH-1010
> Project: Nutch
> Issue Type: Bug
> Components: indexer
> Reporter: Markus Jelsma
> Attachments: NUTCH-1010-1.4.patch, NUTCH-1010-2.0.patch
>
>
> Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
> {code}
> Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "32717 "
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:419)
> at java.lang.Long.parseLong(Long.java:468)
> {code}
> This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-1010) ContentLength not trimmed
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-1010:
---------------------------------
Attachment: NUTCH-1010-2.0.patch
Patch for 2.0.
> ContentLength not trimmed
> -------------------------
>
> Key: NUTCH-1010
> URL: https://issues.apache.org/jira/browse/NUTCH-1010
> Project: Nutch
> Issue Type: Bug
> Components: indexer
> Reporter: Markus Jelsma
> Attachments: NUTCH-1010-1.4.patch, NUTCH-1010-2.0.patch
>
>
> Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
> {code}
> Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "32717 "
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:419)
> at java.lang.Long.parseLong(Long.java:468)
> {code}
> This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-1010) ContentLength not trimmed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056987#comment-13056987 ]
Hudson commented on NUTCH-1010:
-------------------------------
Integrated in Nutch-trunk #1530 (See [https://builds.apache.org/job/Nutch-trunk/1530/])
> ContentLength not trimmed
> -------------------------
>
> Key: NUTCH-1010
> URL: https://issues.apache.org/jira/browse/NUTCH-1010
> Project: Nutch
> Issue Type: Bug
> Components: indexer
> Affects Versions: 1.3, 1.4
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.4, 2.0
>
> Attachments: NUTCH-1010-1.4.patch, NUTCH-1010-2.0.patch
>
>
> Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
> {code}
> Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "32717 "
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:419)
> at java.lang.Long.parseLong(Long.java:468)
> {code}
> This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-1010) ContentLength not trimmed
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-1010:
---------------------------------
Affects Version/s: 1.4
1.3
Fix Version/s: 2.0
1.4
Assignee: Markus Jelsma
> ContentLength not trimmed
> -------------------------
>
> Key: NUTCH-1010
> URL: https://issues.apache.org/jira/browse/NUTCH-1010
> Project: Nutch
> Issue Type: Bug
> Components: indexer
> Affects Versions: 1.3, 1.4
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.4, 2.0
>
> Attachments: NUTCH-1010-1.4.patch, NUTCH-1010-2.0.patch
>
>
> Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
> {code}
> Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "32717 "
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:419)
> at java.lang.Long.parseLong(Long.java:468)
> {code}
> This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-1010) ContentLength not trimmed
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053239#comment-13053239 ]
Markus Jelsma commented on NUTCH-1010:
--------------------------------------
Any objections here?
> ContentLength not trimmed
> -------------------------
>
> Key: NUTCH-1010
> URL: https://issues.apache.org/jira/browse/NUTCH-1010
> Project: Nutch
> Issue Type: Bug
> Components: indexer
> Affects Versions: 1.3, 1.4
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.4, 2.0
>
> Attachments: NUTCH-1010-1.4.patch, NUTCH-1010-2.0.patch
>
>
> Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
> {code}
> Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "32717 "
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:419)
> at java.lang.Long.parseLong(Long.java:468)
> {code}
> This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (NUTCH-1010) ContentLength not trimmed
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma closed NUTCH-1010.
--------------------------------
> ContentLength not trimmed
> -------------------------
>
> Key: NUTCH-1010
> URL: https://issues.apache.org/jira/browse/NUTCH-1010
> Project: Nutch
> Issue Type: Bug
> Components: indexer
> Affects Versions: 1.3, 1.4
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.4, 2.0
>
> Attachments: NUTCH-1010-1.4.patch, NUTCH-1010-2.0.patch
>
>
> Somewhere in some component the ContentLength field is not trimmed. This allows a seemingly numeric field to be treated as a string by the indexer in cases one or more leading or trailing whitespace is added. The result is a hard to debug exception with no way to identify the bad document (amongst thousands) or the bad field.
> {code}
> Jun 22, 2011 1:03:42 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "32717 "
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:419)
> at java.lang.Long.parseLong(Long.java:468)
> {code}
> This can be quickly fixed in the index-more plugin by simply using the trim() when adding the field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira