Jeremy Taylor
Jeremy Taylor
Completely different context (non-existent column on an ARROW_TABLE table file), same error ([Play](https://play.xtdb.com/?version=2.0.0-SNAPSHOT&type=sql&txs=W3sic3lzdGVtLXRpbWUiOm51bGwsInR4cyI6IklOU0VSVCBJTlRPIGRvY3MgKF9pZCwgZm9vKSBWQUxVRVMgKDEsICdiYXInKSJ9XQ%3D%3D&query=U0VMRUNUIG1vcmVfcG9zdHMudAogIEZST00gQVJST1dfVEFCTEUoJ2h0dHBzOi8veHRkYi5jb20vbW9yZV9wb3N0cy5hcnJvdycpCiAgQVMgbW9yZV9wb3N0cyAodCk7)): ``` SELECT more_posts.t FROM ARROW_TABLE('https://xtdb.com/more_posts.arrow') AS more_posts (t); ``` For reference, the correct & working version is:...
Also the same error message as https://github.com/xtdb/xtdb/issues/3337
Another example - you can't `ORDER BY` a non-SELECTed column... ``` INSERT INTO foo (_id, value) VALUES (1, 2); ``` Fails with `java.lang.NullPointerException: Cannot invoke "org.apache.arrow.vector.types.pojo.Field.getType()" because "field" is null`:...
@jarohen is this still relevant given the move to XT Arrow?
Since the changes to use XT Arrow in #3596 the user now reports that _ingestion_ completes successfully and they are able to run queries :tada: Unfortunately though it is not...
> The 'write-type' is set on the _first insertion_ to each key-path Is this intended to apply equally _within_ a transaction? Or could/should "first insertion" take into account the full...
This spec may need to be extended to accommodate _optional_ auto-casting - for example, to accept ints into a float column without throwing an error.
Noting that subsequently working around issues caused by mixed columns is possible by casting to strings and back again like this: ``` SELECT NOW() - CASE WHEN col1::TEXT ~ '^\d{4}-\d{2}-\d{2}.*'...
New repro / edge case: ``` (-> (rel [{:a 1}] [a]) (with {:buggy-col (array_agg a)}))) ```
Yep the error is ambiguous and _may_ actually be unrelated to this original reported issue (on reflection!): ``` xtdb.IllegalArgumentException Unknown symbol: 'xt$_sqp_0' {:symbol "xt$_sqp_0", :xtdb.error/error-key "xtdb.expression/unknown-symbol"} ``` Similar looking error...