Skip to content

EVAL/EVALSHA support #15

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

Merged
merged 1 commit into from
Jul 29, 2014
Merged

EVAL/EVALSHA support #15

merged 1 commit into from
Jul 29, 2014

Conversation

lstrojny
Copy link
Contributor

This PR ads support for EVAL/EVALSHA. Please note that this is a very early PR to get feedback as soon as possible. A lot of stuff needs to be done. I will add a bunch of questions inline.

TODOs

  • Move parameter parsing to commands
  • Error handling for non-scalar values in lists
  • Uneven number of elements in a list that should be treated like a hash
  • Non-float value as a hash value
  • Error handling for null
  • README
  • Logging

return ResultUtil.stringIteratorToMap(result);
}

private Map<String, Float> returnHash(final Iterable result) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any better and more efficient way to do this? Thing is: you can’t return a hash from LUA, that’s why we need to kinda fake it.

@lstrojny
Copy link
Contributor Author

Ready for final review.

@lstrojny
Copy link
Contributor Author

Bump

prog8 added a commit that referenced this pull request Jul 29, 2014
@prog8 prog8 merged commit 3d30f90 into sematext:master Jul 29, 2014
@lstrojny lstrojny deleted the feature/eval branch July 29, 2014 13:23
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

Successfully merging this pull request may close these issues.

2 participants