I am creating plain index products. Some search strings can be up to 6000 characters long. But when I give an index listing (over mysql client)
SELECT * FROM index WHERE id = 1
I assume that the document string ends somewhere at 390 characters. And if I want to find something, whatever is beyond 390 characters, it won’t find anything. And in the spb file, the entire document string is not present.
For testing the maticore I am using mysql client. But the whole string of that product is not even in that produsts.spb file. And if I’m looking for anything beyond the 390 character, nothing is found
But still nowhere did he seriously answer me whether the spb file should contain all the text that is indexed. I keep saying that not everything that is loaded from the sql server is in it. Plain text from the server has 15305852 bytes, but spb is 20 times smaller and has 7689807 bytes. This means that when saving to the index, something shortens it to just about 390 characters.
could you provide minimal reproducible example with couple of documents there you indexes long document when select query from daemon returns only part of the string?
Good news, when I load data via csv pipe, all data is present. Although I did not make any changes to the products index configuration, it also loaded in its entirety. And the spb file already roughly matches the length of the csv file. So I don’t understand this at all.
I’m sorry, but I can’t provide the dump tables, I’m using sharp data and they’re reaching sensitive business information.
In addition, after a few server starts and data loading from both csv and sql servers, all data is already present in the index. Ie. the problem somehow resolved on its own. I don’t know if a server restart or something else solved the problem. My only clue that the data was not in the index was the size of the spb file. At the time of the error, the spb index file was 20 times smaller.