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
Is your feature request related to a problem? Please describe.
Is it possible to support an argument in the write query to optionally bypass the index update? Thus it's possible to have better write performance and make the index update deferred?
Describe the solution you'd like
Optionally improve write performance when the index is a must while index-based lookup query can tolerant this consistency-loss. (AP over CP on data-index consistency).
The deferred index rebuild could be triggered manually or periodically in the background.
Describe alternatives you've considered
Maybe not an option per request(if it's leading mess with mixed requests for both sync/async index-update), but to introduce an option adopted globally?
Additional context
Not sure if it's reasonable or even silly, just thinking that if the user could tolerant this inconsistency before it's eventually updated periodically in batch background jobs(or planned in cold time).
The text was updated successfully, but these errors were encountered:
wey-gu
changed the title
Support bypass index write[async index update/ eventual data-index consistency]
Support deferring index write[async index update/ eventual data-index consistency]
Jul 12, 2021
<!--
Thanks for your contribution!
In order to review PR more efficiently, please add information according to the template.
-->
## What type of PR is this?
- [x] bug
- [ ] feature
- [ ] enhancement
## What problem(s) does this PR solve?
#### Issue(s) number:
closevesoft-inc/nebula-ent#2571closevesoft-inc/nebula-ent#2570
#### Description:
## How do you solve it?
## Special notes for your reviewer, ex. impact of this fix, design document, etc:
## Checklist:
Tests:
- [ ] Unit test(positive and negative cases)
- [ ] Function test
- [ ] Performance test
- [ ] N/A
Affects:
- [ ] Documentation affected (Please add the label if documentation needs to be modified.)
- [ ] Incompatibility (If it breaks the compatibility, please describe it and add the label.)
- [ ] If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
- [ ] Performance impacted: Consumes more CPU/Memory
## Release notes:
Please confirm whether to be reflected in release notes and how to describe:
> ex. Fixed the bug .....
Migrated from vesoft-inc#5500
Co-authored-by: jimingquan <mingquan.ji@vesoft.com>
Is your feature request related to a problem? Please describe.
Is it possible to support an argument in the write query to optionally bypass the index update? Thus it's possible to have better write performance and make the index update deferred?
Describe the solution you'd like
Optionally improve write performance when the index is a must while index-based lookup query can tolerant this consistency-loss. (AP over CP on data-index consistency).
The deferred index rebuild could be triggered manually or periodically in the background.
Describe alternatives you've considered
Maybe not an option per request(if it's leading mess with mixed requests for both sync/async index-update), but to introduce an option adopted globally?
Additional context
Not sure if it's reasonable or even silly, just thinking that if the user could tolerant this inconsistency before it's eventually updated periodically in batch background jobs(or planned in cold time).
The text was updated successfully, but these errors were encountered: