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.

Sign up for GitHub

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

Jump to bottom

soft automatic schema reload #7

Closed
kostja opened this issue Dec 4, 2015 · 0 comments · Fixed by #200
Closed

soft automatic schema reload #7

kostja opened this issue Dec 4, 2015 · 0 comments · Fixed by #200
Assignees
@nicktorwald

Comments

@kostja
Copy link

kostja commented Dec 4, 2015

Now that the iproto protocol has sc_schema_id, fix the driver to perform "soft" schema reload.

  • load the current schema automatically when connection is established
  • include sc_schema_id in queries
  • if the response is ER_SCHEMA_CHANGED, reload the schema and re-issue the query.

tarantool/tarantool#1183
@Totktonada Totktonada mentioned this issue Jan 23, 2019
Open
@Totktonada Totktonada mentioned this issue Mar 19, 2019
Closed
nicktorwald added a commit that referenced this issue Jun 18, 2019
@nicktorwald
Soft automatic schema reload
2894a02 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
@nicktorwald nicktorwald mentioned this issue Jun 18, 2019
Merged
nicktorwald added a commit that referenced this issue Jun 19, 2019
@nicktorwald
Soft automatic schema reload
51ed9ea 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Jun 19, 2019
@nicktorwald
Soft automatic schema reload
eeefdca 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Jun 19, 2019
@nicktorwald
Soft automatic schema reload
178337c 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Jul 1, 2019
@nicktorwald
Soft automatic schema reload
a627f21 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Jul 1, 2019
@nicktorwald
Soft automatic schema reload
258f1d4 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137

Soft automatic schema reload

Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Jul 5, 2019
@nicktorwald
Soft automatic schema reload
672a687 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137

Soft automatic schema reload

Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
@Totktonada Totktonada mentioned this issue Aug 2, 2019
Open
nicktorwald added a commit that referenced this issue Sep 4, 2019
@nicktorwald
Soft automatic schema reload
8ef4616 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 4, 2019
@nicktorwald
Soft automatic schema reload
e99d0dd 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 5, 2019
@nicktorwald
Soft automatic schema reload
fd33520 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 6, 2019
@nicktorwald
Soft automatic schema reload
39b7dfb 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 6, 2019
@nicktorwald
Soft automatic schema reload
7f107c0 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
05d7b8c 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
6ffa1a5 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
8aed0a1 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
456385e 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 18, 2019
@nicktorwald
Soft automatic schema reload
ecf165d 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Sep 19, 2019
@nicktorwald
Soft automatic schema reload
31c2dd9 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Oct 25, 2019
@nicktorwald
Soft automatic schema reload
b591fab 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
@Totktonada Totktonada mentioned this issue Nov 17, 2019
Open
nicktorwald added a commit that referenced this issue Nov 20, 2019
@nicktorwald
Soft automatic schema reload
567851c 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Nov 21, 2019
@nicktorwald
Soft automatic schema reload
4056cb2 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Nov 21, 2019
@nicktorwald
Soft automatic schema reload
de7faf9 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
nicktorwald added a commit that referenced this issue Nov 21, 2019
@nicktorwald
Soft automatic schema reload
dd1f29f 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
Totktonada pushed a commit that referenced this issue Nov 26, 2019
@nicktorwald @Totktonada
Soft automatic schema reload
f32bafa 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

Closes: #7, #137
@Totktonada Totktonada mentioned this issue Nov 30, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nicktorwald nicktorwald

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Soft automatic schema reload tarantool/tarantool-java
2 participants
@kostja @nicktorwald