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

merge operator with managed db #1016

Closed
yangzh opened this issue Aug 28, 2019 · 2 comments
Closed

merge operator with managed db #1016

yangzh opened this issue Aug 28, 2019 · 2 comments
Labels
area/api Issues related to current API limitations. help wanted Please help us fix this! kind/feature Something completely new we should consider. priority/P3 Low priority, something to be done once everything else is fixed. skip/stale Skip stalebot

Comments

@yangzh
Copy link

yangzh commented Aug 28, 2019

What version of Go are you using (go version)?

It doesn't matter for this, it's a feature request.

What version of Badger are you using?

2.0 pre.

Does this issue reproduce with the latest master?

N/A.

What are the hardware specifications of the machine (RAM, OS, Disk)?

What did you do?

It seems merge operator currently is only available for non-managed db.
For feature parity, it would also be available (and there is no fundamental reason why it cannot) for managed db.

I don't have a concrete use case yet, but maybe someone can come up with one?

What did you expect to see?

What did you see instead?

@jarifibrahim jarifibrahim added area/api Issues related to current API limitations. kind/feature Something completely new we should consider. priority/P3 Low priority, something to be done once everything else is fixed. status/accepted We accept to investigate or work on it. labels Aug 29, 2019
@jarifibrahim jarifibrahim added the help wanted Please help us fix this! label Sep 23, 2019
@lgalatin lgalatin removed the status/accepted We accept to investigate or work on it. label Jan 6, 2020
@stale
Copy link

stale bot commented Feb 5, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale The issue hasn't had activity for a while and it's marked for closing. label Feb 5, 2020
@jarifibrahim jarifibrahim added skip/stale Skip stalebot and removed status/stale The issue hasn't had activity for a while and it's marked for closing. labels Feb 7, 2020
@minhaj-shakeel
Copy link

Github issues have been deprecated.
This issue has been moved to discuss. You can follow the conversation there and also subscribe to updates by changing your notification preferences.

drawing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Issues related to current API limitations. help wanted Please help us fix this! kind/feature Something completely new we should consider. priority/P3 Low priority, something to be done once everything else is fixed. skip/stale Skip stalebot
Development

No branches or pull requests

4 participants