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

Mismatch of schemas on the storage and in the net_box connection #361

Open
GRISHNOV opened this issue May 18, 2023 · 0 comments
Open

Mismatch of schemas on the storage and in the net_box connection #361

GRISHNOV opened this issue May 18, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@GRISHNOV
Copy link
Contributor

In the course of solving the issue with mismatch of schemas on the storage and in the net_box connection on router through patch, some problems were discovered. If there is a need to calculating the hash of the schema to determine if schema_reload is necessary, there may be false positive mismatches:

And separately for tarantool v1:

  • net.box's schema always states index as non-unique. Related issue, which was not backported to tarantool v1.
  • Information about collation is described in different ways via net.box for router and locally via box on the storage. Related issue.
@DifferentialOrange DifferentialOrange added bug Something isn't working teamE labels May 18, 2023
locker pushed a commit to tarantool/tarantool that referenced this issue Aug 18, 2023
Currently the `exclude_null` field of `index_object.parts` is inconsistent
between local box and net.box connection. It returns the following values:
- locally: true / null
- net.box: true / false

This mismatch makes it difficult to compare schemas on the storage and via
the net.box connection on the router (see tarantool/crud#361).

Closes #8649

NO_DOC=minor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants