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

[0.9.1+ from source] derivative function responds with error #3355

Closed
desa opened this issue Jul 16, 2015 · 7 comments · Fixed by #3361
Closed

[0.9.1+ from source] derivative function responds with error #3355

desa opened this issue Jul 16, 2015 · 7 comments · Fixed by #3361
Assignees
Milestone

Comments

@desa
Copy link
Contributor

desa commented Jul 16, 2015

Just upgraded to the latest version.

Issuing the command

select derivative(value) from cpu_user

returns

ERR: expected function argument to derivative
@desa
Copy link
Contributor Author

desa commented Jul 16, 2015

@jwilder any idea why this is happening?

@otoolep
Copy link
Contributor

otoolep commented Jul 17, 2015

You mean you built from master?

@otoolep
Copy link
Contributor

otoolep commented Jul 17, 2015

I change the query-engine code. Is this a regression?

@otoolep
Copy link
Contributor

otoolep commented Jul 17, 2015

Can you show us:

service influxd version

@connor4312
Copy link
Contributor

I also get this, just having pulled from master (hash 6402079)

@otoolep otoolep self-assigned this Jul 17, 2015
@otoolep otoolep added this to the 0.9.2 milestone Jul 17, 2015
otoolep added a commit that referenced this issue Jul 17, 2015
The multiple checks for Mapper and Executor type -- the lack of DRYness
in this code -- meant the same checks would need to be copied. Therefore
this change, as well as fixing the bug, improves the situation a little
bit by *asking* the Mappers what type of Executor is required. This code
is still not ideal.

Fixes #3355.
@otoolep
Copy link
Contributor

otoolep commented Jul 17, 2015

Fixed by #3361

@otoolep
Copy link
Contributor

otoolep commented Jul 17, 2015

Thanks for the report @mjdesa @connor4312

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 a pull request may close this issue.

3 participants