Christian Himpe comments

Results 151 comments of


                                            Christian Himpe

Creating root after databases already exists makes whole REST API insane

May be the server script is run from the wrong folder. Can you post the contents of the `entrypoint.sh`? BTW: you could consider using the ready endpoint `/api/V1/ready` for the...

Creating root after databases already exists makes whole REST API insane

This could be due to file permissions. You can temporarily give all the files in the mounted folders all permissions like `777` and see if it works. I ran into...

Console Error on Attempt to Create an Index that Exists even with IF NOT EXISTS Clause

Trying from studio (`24.11.2-SNAPSHOT`), I get no response form the server sending the second `CREATE INDEX ... IF NOT EXISTS`. From console (`24.11.2-SNAPSHOT`) I get an empty response.

Console Error on Attempt to Create an Index that Exists even with IF NOT EXISTS Clause

More info: the error above happens for remote connections from the console. For local connections an empty response is given.

Console Error on Attempt to Create an Index that Exists even with IF NOT EXISTS Clause

This seems **NOT** to be fixed by the latest changes.

SQL: Index can return too many entries when used with `ORDER BY`

Using either `UPDATE ... MERGE ... UPSERT` or `UPDATE ... CONTENT ... UPSERT` produces too many index results.

SQL: Index can return too many entries when used with `ORDER BY`

Here is some more testing which may help locate the source: * Both sorting directions `ASC` and `DESC` produce these duplicate results but different numbers: 146 for `ASC`, and 117...

SQL: Index can return too many entries when used with `ORDER BY`

More testing reveals: * Using multiple order keys like `ORDER BY publicationYear, name` returns the correct amount of results. @lvca This does also not use the `publicationYear` index, right? *...

SQL: Index can return too many entries when used with `ORDER BY`

@robfrank Here is another test case using 25.1.1. It is the smallest I could produce yet with 39 records: [metadatalake-backup-20250130-122441030.zip](https://github.com/user-attachments/files/18601697/metadatalake-backup-20250130-122441030.zip) The query: `SELECT name FROM metadata ORDER BY publicationYear` produces...

SQL: Index can return too many entries when used with `ORDER BY`

Here is some more info that may help: * The records are UPSERTed (see example above) via the HTTP `command` endpoint using the `SQLscript` language. * A `Unique` index is...