Phillip Cloud
Phillip Cloud
The PySpark error class import needs an `ImportError` guard to handle the module path change from 3.3 to 3.5. There are some examples around the codebase for this that were...
I added implementations for Impala and Exasol.
Looking into Snowflake. There seems to be plenty of structured information about errors, but interpreting what it means is another story.
Added a Snowflake implementation. It's ... something.
Ok, BigQuery implementation is up.
I think this is good to go. What an absolute hellscape this problem is. Thanks for powering through @ncclementi!
Seems fine. I don't like that we have to do this but the alternative of implementing a custom pyarrow type seems less desirable than converting to strings.
The repeated UUID issue has been addressed: ``` In [4]: import ibis ...: ibis.options.interactive = True ...: from ibis.expr.api import row_number, uuid, now, pi ...: ...: ibis.set_backend("sqlite") ...: t =...
The original issue of > same uuid generated by sqlite was addressed previously when we changed the SQLite `uuid` UDF to be non-deterministic, which prevents SQLite from running a function...
Based on > A job I run daily suddenly started giving the first error. With the error I got, it took some experimenting to figure out that it was actually...