-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
Bleve index fails with "converting NULL to string is unsupported" #14929
Comments
/cc @mgdelacroix |
same here |
Also receiving this error, in 5.26 |
Ironically, I'm also getting this error when attempting to use elasticsearch... Digging now to see if I can figure out what's going on here... (E20 instance) |
Please check what we have done with @shieldsjared probably you're having the same issue |
Sorry for the delay here, but I did not have time previously to focus on this issue. Anyway, it was a similar case that the one describes in #15357. After having checked the messages manually (I had only 62 in my case) and taking a backup of my database, I did run the following: DELETE FROM Posts
WHERE id IN ( SELECT p.id
FROM Posts p
LEFT JOIN Channels c
ON p.ChannelId = c.Id
WHERE p.ChannelId IS NULL
OR c.Id is NULL
OR p.ChannelId = ''); (Don't run that blindly! Be sure to understand what's going on) Indexing has been running for the past 2h now, but before it was failing after 3 minutes. So I guess we can say this is solved. |
Summary
Bleve indexing fails on our E10 instances with the following error:
Steps to reproduce
Thought I'm pretty sure this is highly dependent of the data in the server
Expected behavior
I expect Bleve indexing to succeed.
Observed behavior (that appears unintentional)
Bleve indexing return the following error in the UI:
The server logs have similar error (but way more):
Possible fixes
No idea.
The text was updated successfully, but these errors were encountered: