Heat is passing values to the query engine that look like expressions, but aren't. The code in the API that tries to convert the incoming value to the right type using ast is getting an unhandled SyntaxError for that case.
>>> ast.literal_eval('WWW-Layer-4a80714f-0232-4580-aa5e-81494d1a4147-uolhh25p5xxm')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 49, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py", line 37, in parse
return compile(source, filename, mode, PyCF_ONLY_AST)
File "<unknown>", line 1
WWW-Layer-4a80714f-0232-4580-aa5e-81494d1a4147-uolhh25p5xxm
We should:
1. Catch SyntaxError.
2. Not try to do type guessing if the incoming value contains punctuation characters (especially - and + since those will result in expressions, so a value like 10-1 will come out 9 and be completely wrong in all senses).
Fix proposed to branch: master
Review: https:/