vshard: introduce `connection_fetch_schema` config option
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Related dev. issue(s): GitHub link(s)
Product: Tarantool, Cartridge, TDG, connectors, tools?
Since: product version
Root document: (https://www.tarantool.io/ru/doc/latest/reference/reference_rock/vshard/vshard_ref/)
SME: @ expert to ask for more information
A new configuration option connection_fetch_schema has been added.
It controls whether vshard connections should fetch the database schema
(to allow using conn.schema.<...> or conn.space.<space_name>).
vshard itself doesn’t need this fetching at all, so you can safely set
connection_fetch_schema = false - as long as you’re not relying on its
internal connections. This will improve performance.
By default, it’s set to true (enabled) for backward compatibility.
Requested by @Astronomax in https://github.com/tarantool/vshard/commit/c83deb1983757df1b2ab030776a72bea919cf25b.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the vshard reference page linked as the root document and locate the connection configuration options. Document connection_fetch_schema, its default, effect on schema access, and performance and backward-compatibility implications; it is done when the option is clearly covered there.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100