You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (Jira)" <ji...@apache.org> on 2020/08/17 14:55:00 UTC
[jira] [Commented] (NUTCH-2823) IllegalStateException in
IndexWriters.describe() when validating url param for SolrIndexer
[ https://issues.apache.org/jira/browse/NUTCH-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179042#comment-17179042 ]
Sebastian Nagel commented on NUTCH-2823:
----------------------------------------
There is a bug in the calculation of the column width(s) when the index writer params are shown as table: if the first or third columns occupy too much space the calculated length of the second column can become negative. I'll open a PR to fix this. Thanks, [~JoeGilvary] for reporting this issue!
> IllegalStateException in IndexWriters.describe() when validating url param for SolrIndexer
> ------------------------------------------------------------------------------------------
>
> Key: NUTCH-2823
> URL: https://issues.apache.org/jira/browse/NUTCH-2823
> Project: Nutch
> Issue Type: Bug
> Components: indexer, plugin
> Affects Versions: 1.16, 1.17
> Reporter: Joe Gilvary
> Assignee: Sebastian Nagel
> Priority: Minor
> Fix For: 1.18
>
>
> The string validation for the IndexWriters.describe() fails when the value in index-writers.xml is too long.
> I encountered the exception when using three comma-separated URL values in a config that worked for Nutch 1.15.The schema doesn't allow multiple values, but the documentation says a comma-separated list works.
> Indexing ran without the exception when I changed to use only one host's URL (Solr Cloud). Sebastian duplicated the error with a long string value for the param, so it's not directly due to the comma separated values.
> While googling I found this thread in the archives where Markus encountered it going from 1.15 to 1.16:
> mail-archives.apache.org/mod_mbox/nutch-user/201910.mbox/<05...@googlemail.com>
> I also found a change in 1.16 that might be relevant: NUTCH-2602
> https://issues.apache.org/jira/browse/NUTCH-2602
> My stack trace:
> {{java.lang.Exception: java.lang.IllegalStateException: text width is less than 1, was <-26>}}
> \{{ at org.apache.hadoop.mapred.LocalJobRunner$Job.runTasks(LocalJobRunner.java:492)}}
> \{{ at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:559)}}
> {{Caused by: java.lang.IllegalStateException: text width is less than 1, was <-26>}}
> \{{ at org.apache.commons.lang3.Validate.validState(Validate.java:829)}}
> \{{ at de.vandermeer.skb.interfaces.transformers.textformat.Text_To_FormattedText.transform(Text_To_FormattedText.java:215)}}
> \{{ at de.vandermeer.asciitable.AT_Renderer.renderAsCollection(AT_Renderer.java:250)}}
> \{{ at de.vandermeer.asciitable.AT_Renderer.render(AT_Renderer.java:128)}}
> \{{ at de.vandermeer.asciitable.AsciiTable.render(AsciiTable.java:191)}}
> \{{ at org.apache.nutch.indexer.IndexWriters.describe(IndexWriters.java:326)}}
> \{{ at org.apache.nutch.indexer.IndexerOutputFormat.getRecordWriter(IndexerOutputFormat.java:45)}}
> \{{ at org.apache.hadoop.mapred.ReduceTask$NewTrackingRecordWriter.<init>(ReduceTask.java:542)}}
> \{{ at org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:615)}}
> \{{ at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:390)}}
> \{{ at org.apache.hadoop.mapred.LocalJobRunner$Job$ReduceTaskRunnable.run(LocalJobRunner.java:347)}}
> \{{ at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)}}
> \{{ at java.util.concurrent.FutureTask.run(FutureTask.java:266)}}
> \{{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}}
> \{{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}}
> \{{ at java.lang.Thread.run(Thread.java:748)}}
>
> Thanks,
> Joe
--
This message was sent by Atlassian Jira
(v8.3.4#803005)