Hello, I experience some issues with the use of the Topic Extractor Node. Even though I do everything correctly, the third output(iteration) becomes empty (rows are equal to zero). The other two outputs (Document table with topics and topic terms) is just fine, it is only the third output (iteration statistics) that gets empty. Have tried in different workflows, checked the numbers (use of , and .), tried different number of threds and I have also gotten an executed workflow from another person where I could see the iteration output - but when I executed on my PC the same workflow it became zero again…
Workflow is attached. Any advice?
Topic Extractor Problem.knwf (2.9 MB)
Hi @Nadine_H and welcome to the forum.
Sorry for the trouble! This definitely looks like a bug, and one of our data scientists filed a ticket for it last week (AP-17814). This issue has come up in the past and was a bit hard to reproduce, so thank you for providing a workflow that clearly demonstrates the problem. Once there is news to report, someone will update this topic in the future.
Dear @Nadine_H :
thanks for the information. To narrow it further down, could you (or anybody else who experiences the same issue and reads this thread) please help me with the following questions?
- Does this issue occur in Knime AP 4.4.2? Or somewhere else as well?
- Do you use Windows/Mac/Unix? Also, which version?
- Maybe the most interesting; you mentioned working workflows from other persons, could you tell differences between your computer and theirs?
I apologize, so far this is a bit tricky as I and my team-mates cannot reproduce it yet.
Hi all. For the workflow provided here, I could not reproduce the issue after resetting all nodes (except for the Excel Reader) followed by re-execution of everything (with configurations intact). Here’s my iteration output:
Hello Steffen. Thanks for your help on this. Please let us know if you need more examples.
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.
Dear @Nadine_H and @fvillarroel,
my team has probably fixed the issue, which was technically not possible before the 4.7 release because of an Java update. When 4.7 will be released (December 2022), please try it again, as we can not verify our fix.
Best regards and sorry for the long time