Baur
Baur
Main user facing problem: Confusion if some rows are not inserted (for example because of constraint violation). Current behaviour: Errors are swallowed, number of successfully inserted rows is returned. Listing...
Given that pos `column` is a geo point, `MATCH using intersects` works. See https://github.com/crate/crate/pull/14942#issuecomment-1794509999.
Support for adding multiple columns in a single `ALTER TABLE` statement has been implemented in https://github.com/crate/crate/pull/13383 and will be available in the next release (CrateDB 5.2)
It seems like there are couple of follow ups to do: https://github.com/crate/crate/pull/13528#issuecomment-1411426039
Related: https://github.com/elastic/elasticsearch/issues/85876 and https://github.com/gocd/gocd/issues/10722 (both applying same workaround)
Yep, I'm also waiting for fix for that issue=)
@lukemurray, could you please give me an idea to fix it by myself? What scripts and functions should be investigated?
Original query plan ``` [Eval[(SELECT field2 FROM (cte2)) AS field3] (rows=unknown) └ CorrelatedJoin[target_field2, field1, (SELECT field2 FROM (cte2))] (rows=unknown) └ Rename[target_field2, field1] AS subquery1 (rows=unknown) └ Eval['abc' AS target_field2, 'def'...
Not posting plan without ORDER BY as issue is probably related to ORDER BY + correlated subquery. Last posted plan (without filters) is quite different from other 3, has only...
> Not posting plan without ORDER BY as issue is probably related to ORDER BY + correlated subquery. left side is a plan for not working query, right side is...