-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add user-interface for Runtime UDF registration #261
Comments
My biggest concern about adding these as dependencies is that we're trying to maintain pip/PyPI installation. Are any of these packages conda only? |
All these packages are available via pip. The |
Some of them are dependent on Cython? That's the biggest issue that caused us to re-write the IPC code, people were having a hard time installing pymapd via pip (especially on Windows) |
thriftpy2 has optional Cython dependency that is disabled for non-linux platforms. |
I have updated rbc to work on Windows. Also installing rbc via pip seems to work fine (tested on Windows). |
Please go ahead and start working on this @pearu, and before we merge we can do a final pip/conda & linux/osx/windows check |
This was implemented in #272 |
The latest OmnisciDB release contains support for Runtime UDF registration. Python users can use the rbc package for registering Python functions as Runtime UDFs in OmnisciDB server.
This issue proposes adding Runtime UDF registration user-interface to pymapd. The proposal would consist of the following tasks:
__call__
method toConnection
class so that theConnection
instance can be used as a decorator on Python functions.rbc
) to all query methods likeselect_ipc_gpu
, etc.rbc
package optional dependency topymapd
. Whilerbc
is a pure Python package, it depends on the following packages:numba
,llvmlite>=0.29
,tblib
,thriftpy2
, andsix
. Therbc
optional dependency means that therbc
would be imported withinConnection.__call__
method only, that is,pymapd
would be functional even whenrbc
is not installed.As a result, here is how a typical workflow of using Runtime UDFs would look like:
Are there any suggestions or concerns about the proposed UI for Runtime UDFs?
The text was updated successfully, but these errors were encountered: