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

Support deferring index write[async index update/ eventual data-index consistency] #2635

Open
wey-gu opened this issue Jul 11, 2021 · 0 comments
Labels
type/feature req Type: feature request

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Jul 11, 2021

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).

@wey-gu 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
@CPWstatic CPWstatic transferred this issue from vesoft-inc/nebula-graph Aug 27, 2021
@CPWstatic CPWstatic added the type/feature req Type: feature request label Aug 28, 2021
yixinglu pushed a commit to yixinglu/nebula that referenced this issue Sep 14, 2023
<!--
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: 
close vesoft-inc/nebula-ent#2571
close vesoft-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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature req Type: feature request
Projects
None yet
Development

No branches or pull requests

2 participants