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

Look into adding API operation to return non existant row columns. #811

Open
keith-turner opened this issue Dec 13, 2016 · 2 comments
Open

Comments

@keith-turner
Copy link
Contributor

A few times I have written Fluo code to find the row columns that do not exists. A primitive operation for this could be optimized.

@keith-turner
Copy link
Contributor Author

keith-turner commented Oct 30, 2017

I deleted the comment I had made here because I was thinking of #527 when I wrote that comment. I copied the comment that was here to #527 and modified it a bit. I realized setIfAbsent() doing something similar to delete() would not work, so I changed that when copying.

I wish I had recorded the use case I was thinking of for this operation, because I can't remember. It may be that if setIfAbsent() is available then there is no use case for this operation. I think it it would be good to defer this until there is a use case is identified that is not efficiently satisfied by setIfAbsent()

@kennethmcfarland
Copy link
Contributor

I would like to claim this if possible. The other issues I have currently are fairly trivial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants