Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postprocessing: undefined field: "cr_host_chance_d" #627

Open
okybaca opened this issue Jan 30, 2024 · 0 comments
Open

Postprocessing: undefined field: "cr_host_chance_d" #627

okybaca opened this issue Jan 30, 2024 · 0 comments
Labels
bug Indicates an unexpected problem or unintended behavior index prio low question Indicates that an issue, pull request, or discussion needs more information

Comments

@okybaca
Copy link
Contributor

okybaca commented Jan 30, 2024

During the automatically started prostprocessing, indicated by

I 2024/01/30 18:33:14 CollectionConfiguration * postprocessed 1445900 from 20273883 collection documents; 4633 ppm; 4063 minutes remaining

lines in the log, every several hunderds of entries, an error is thrown:

request: http://127.0.0.1:8983/solr/collection1/update?wt=javabin&version=2 Remote error message: undefined field: "cr_host_chance_d" at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.sendUpdateStream(ConcurrentUpdateSolrClient.java:394) at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.run(ConcurrentUpdateSolrClient.java:191) at org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)

From which I guess, yacy is trying to update some entry, where "cr_host_chance_d" field is undefined.

Should such state of database result in solr error, since it's a normal application run?
Shouldn't it be soluted in the app's code instead?
Is the error corrected afterwards and the field is filled?

@okybaca okybaca added bug Indicates an unexpected problem or unintended behavior question Indicates that an issue, pull request, or discussion needs more information prio low labels Jan 30, 2024
@okybaca okybaca added the index label Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior index prio low question Indicates that an issue, pull request, or discussion needs more information
Projects
None yet
Development

No branches or pull requests

1 participant