You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After switching from home-grown DH DateTime type to Java's own Instant and siblings to store date/time data in DH, the utility provided by time.py could be achieved by 3rd party/DH built conversion support between Java Instant and Python DateTime and Python's own DateTIme manipulation libraries.
A number of the wrapper functions in time.py, including lower_bin(), upper_bin(), now(), when used in queries, make the execution 20x+ slower because of the double-crossing between JVM/Python. The effort to automatically substitute them with their Java camelCase counterparts has proven to be messy and unsatisfactory.
Since these utility functions should not be considered as typical Python UDFs, but rather part of the built-ins of DH query language, it is arguably better/more acceptable to clearly document them and educate the user on how to use them than for purist reasons to wrap them in Python but making it confusing for the users and trying to solve the performance problem that could be avoided otherwise.
This would also render following #2777, #2306, #2303 non-issues.
The text was updated successfully, but these errors were encountered:
Reasons:
This would also render following #2777, #2306, #2303 non-issues.
The text was updated successfully, but these errors were encountered: