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
[Python] Integers greater than 32 bits don't resolve properly in the query engine #1461
Comments
Casting
I'm guessing it's an |
|
Update This issue is not related to the
This code results in the same issue, with Raw numbers in the update query (using Ryan's example above) work properly |
This may be a result of else if (JPy_IS_CLONG(pyArg) && (type == JPy_JObject || ((*jenv)->IsAssignableFrom(jenv, JPy_Integer_JClass, type->classRef)))) {
return JType_CreateJavaIntegerObject(jenv, type, pyArg, objectRef);
} else if (JPy_IS_CLONG(pyArg) && (type == JPy_JObject || ((*jenv)->IsAssignableFrom(jenv, JPy_Long_JClass, type->classRef)))) {
return JType_CreateJavaLongObject(jenv, type, pyArg, objectRef);
} The scale of the python |
We can work around this (without needing to modify jpy) by using more type-appropriate return values, either by checking |
Description
The following python code is supposed to make a table with 2 columns, one containing a date-time and the other containing the date-time floored via the
lowerBin()
method, and print the equivalent result oflowerBin()
to console.However, the print statement and the table result in 2 different results
2020-01-01T00:30:00.000000000 NY
vs2020-01-01T00:34:59.016
Steps to reproduce
Described above
Expected results
The output of the print statement for
lowerBin()
should match the column computed bylowerBin()
.Actual results
The output of the print statement for
lowerBin()
appears correct, while the column computed bylowerBin()
is not correct.Additional details and attachments
This does not happen in groovy.
This may be the same issue as #1348. If that's the case, feel free to close this to avoid duplicated issues.
Versions
The text was updated successfully, but these errors were encountered: