String to Document Failed

KNIME Extensions
1

After Tika Parser and some other nodes in the component, String to Document failed with the message:
ERROR Strings To Document 3:79 Could not store document in cell: C:\Users\Igor\Downloads\Cognitive_Psychology_and_Cognitive_Neuroscience.pdf
ERROR Strings To Document 3:79 Execute failed: Cell at index 0 is null!

image
image517×842 9.18 KB

Do not know how to load a pdf by itself, you can check why it failing the node.

P.S. Just uncheck Author as recommended in String to Document crashes - #3 by acommons
and it works.

1 Like
2

Glad you found a solution :+1:

3

Thank you, Scot for looking into my case. Would it be feasible to look at Author field processing? In my case it seems empty.

4

Hi Igor -

We do have an old ticket about this (AP-7588) that was closed because at the time we couldn’t reproduce the issue. Perhaps there are characters in your Content field that cause the node to fail when it tries to parse it as an Author?

Can you share the PDF file that causes this error, or is it proprietary?

5

It is a free book from Wikibooks.org
Cognitive_Psychology_and_Cognitive_Neuroscience.pdf
Forum window does not allow PDF format. Could you please provide a link I can load it?

6

I found a link to it here: https://upload.wikimedia.org/wikipedia/commons/d/d8/Cognitive_Psychology_and_Cognitive_Neuroscience.pdf

Let me see if I can reproduce the problem.

7

I can reproduce. Now I will irresponsibly speculate about the problem for a moment :slight_smile:

I suspect this is happening because the Author field in the Strings to Document node is not equipped to deal with the thousands of words being input via the Content field from the preceding Tika Parser. It could have a more descriptive error message for sure, but in practical terms, I would never expect this to work.

EDIT: Alternatively, maybe the settings for the node should have checkboxes for the metadata off by default? This might help eliminate some confusion.

2 Likes
8

@izaychik63 I added a ticket in our system to address this issue (AP-16723), with a +1 from you.

2 Likes
9

Hi @izaychik63 -

With the release of 4.4.1, this issue should now be resolved. Thanks for the detailed bug report!

3 Likes
10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.