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
During creation of VIEW space, string containing its definition (i.e.
"SELECT ...") is parsed to fetch names of referenced spaces. By those
names real struct space objects are found using schema_find_id().
This function processes lookup in _space using its secondary index.
On the other hand, secondary indexes of _space are unavailable during
this stage of recovery, so this lookup fails and whole recovery process
aborts.
It is worth mentioning that now we can fetch space directly from
in-memory cache using its name (originally, when view reference counter
was introduced, we couldn't do this due to absence of name-cache). So,
to fix this issue, let's use space_by_name() instead of schema_find_id()
Closes#3814
I have Ubuntu 18.04. I have Tarantool 2.1, pulled from source today.
I execute this request:
Result:
Alas, I failed to see exactly what caused this, although I remember that I was trying out SQL statements including tables with strange names, for example create table ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ (s1 int primary key); -- but not names like the ones in the error messages above. I am attaching the earliest .snap file, zipped, and i know that if this .snap file is present then Tarantool will produce the above error messages.
issue.zip
issue.zip
The text was updated successfully, but these errors were encountered: