opteryx
opteryx copied to clipboard
mabel-dev
🦖 A SQL-on-everything Query Engine you can execute over multiple databases and file formats. Query your data, where it lives.
Some queries may be able to be completely responded to by buffered blobs. Also reduces the likelihood of a read evicting blobs it wanted to read but evicting it and...
### Thanks for stopping by to let us know something could be better! **Is your feature request related to a problem? Please describe.** _A clear and concise description of what...
https://stackoverflow.com/questions/73016064/how-to-make-my-self-hosted-github-runner-run-jobs-in-a-docker-container-instead
https://techcult.com/4-ways-to-split-string-by-delimiter-in-sql/ Split returns an array, split string returns a relation. Split string should be a function relation, so can be used in from and joins, split just a standard function....
Show functions isn't much use without info about the functions.
This test opteryx/tests/query_execution/test_show_functions.py currently tests for UnsupportedSyntaxErrors rather than the result
Currently we convert literals into arrays and then usually only work with element 0. We would avoid work and memory management if we only created the array when needed.
Int comparison is probably very well written in numpy and pyarrow, but can we beat them for strings.
Even if we can't push predicates, we may be able to push components to SQL source. Eg SELECT * FROM planets WHERE id + gravity > rand() We could push...
Currently only predicates which are simple three-part (x = y style) are pushed, if only identifiers from a single relation are being used, we should be able to push more...