Jeremy Taylor

Results 145 issues of Jeremy Taylor

Adds backwards compatibility for tx-logs that inadvertently contain serializations of `clojure.lang.PersistentVector$ChunkedSeq` instead of plain vectors. How these serializations might have ended up on the tx-log is unclear to me for...

Currently the Java pom.xml example in the docs doesn't include Clojars as a repository, which means multiple required deps from xtdb-core won't be found (needed for in-process testing), but more...

bug
2.x

Currently the generated column names look rather odd: `SELECT LEAST(1,2), LEAST(3,4) FROM (VALUES (1)) x` => `{".column-1/":1,".column-2/":3}` Via `application/jsonl` it similarly looks like: `{".column-1/": 1, ".column-2/": 3}` I would guess...

bug
2.x

## Context For various reasons (batching of ~distinct logical transactions into the same `submit-tx` call for performance, or invalid assumptions about how historical data should be inserted, etc.), a user...

debate-reqd
1.x
documentation

e.g. https://app.circleci.com/pipelines/github/xtdb/xtdb/4563/workflows/e1040ce1-929f-42f9-b171-35ac81850be3/jobs/14257?invite=true#step-103-61095_31

bug
1.x
ci

Similar error with (at least) INTERSECT or UNION: ```sql SELECT language.name FROM language INTERSECT SELECT film.name FROM film ``` ``` 1. Unhandled java.lang.IllegalArgumentException (No message) Preconditions.java: 122 org.apache.arrow.util.Preconditions/checkArgument BaseVariableWidthVector.java: 1376...

bug
2.x

EDIT: minimal repro `SELECT DATE '2000-01-01' < '2010-01-01'` ```sql SELECT r.xt$id FROM rental r WHERE r.xt$valid_from

error-msgs

```SQL SELECT DISTINCT film.xt$id AS id, film.title, film.description, COUNT(inventory.xt$id) AS inventory_count FROM film JOIN inventory ON (inventory.film_id = film.xt$id AND inventory.store_id = 1) LEFT JOIN rental ON (rental.inventory_id = inventory.xt$id...

bug
2.x

e.g. `*` projection from a joined relation like ```sql SELECT film.*, language.name FROM film JOIN language ON language.xt$id = film.language_id ``` ...can't be translated 1:1 into XTQL currently because `*`...

documentation
xtql

Currently always expects a user-specified date-time.

bug
2.x