You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a similar is #190 but for regular rather than Xapian indexing. This is due to the word field in eprint__rindex being a VARCHAR(128). That is not unreasonable as it is unlikely that a word that might be searched on would be longer than that number of characters. The issue is not due to multi-bytes words, it is due to MariaDB 10.3+ complaining about inserting words longer than 128 characters to eprint__rindex rather than just truncating. Neither truncating or error is appropriate. It is unlikely to be useful to index a word greater than 128 characters even it if is possible, so these should be excluded from indexing.
The text was updated successfully, but these errors were encountered:
This original fix would allow short words and stop words to be indexed when before they would not. $ok should only be set changed (from 1 to 0) if the word lentgth is too long.
This is a similar is #190 but for regular rather than Xapian indexing. This is due to the
word
field ineprint__rindex
being aVARCHAR(128)
. That is not unreasonable as it is unlikely that a word that might be searched on would be longer than that number of characters. The issue is not due to multi-bytes words, it is due to MariaDB 10.3+ complaining about inserting words longer than 128 characters toeprint__rindex
rather than just truncating. Neither truncating or error is appropriate. It is unlikely to be useful to index a word greater than 128 characters even it if is possible, so these should be excluded from indexing.The text was updated successfully, but these errors were encountered: