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 dictionary key evaluation #440

Merged
merged 1 commit into from Jan 14, 2014

Conversation

Projects
None yet
2 participants
@azubanov
Contributor

azubanov commented Jan 14, 2014

Extension 788a8e3
commit (about using a nested dictionary field #324).
Code get performance penalty but easy to use with dictionaries.

@Mpdreamz

This comment has been minimized.

Show comment
Hide comment
@Mpdreamz

Mpdreamz Jan 14, 2014

Member

Sweet!

I imagine the performance penalty would be minimal for existing code since it will only branch into the Lambda compile if the cast to ConstantExpression is null 👍

Thanks for this @azubanov

Member

Mpdreamz commented Jan 14, 2014

Sweet!

I imagine the performance penalty would be minimal for existing code since it will only branch into the Lambda compile if the cast to ConstantExpression is null 👍

Thanks for this @azubanov

Mpdreamz added a commit that referenced this pull request Jan 14, 2014

Merge pull request #440 from azubanov/master
support dictionary key evaluation

@Mpdreamz Mpdreamz merged commit 45cf25a into elastic:master Jan 14, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment