kostas
Schema and tables
Thank you for the sample. Indeed, these timestamps are incompatible with the UI CSV importer which expects RFC3339 format (
2014-01-05T16:12:45.000Z).
There is work planned to make the UI CSV import feature work with pg-native timestamps (like the ones in the sample csv above).16 replies
Schema and tables
If you hover over the column name or type while it is red, it should show a pop up with more information about the error. Typically that would be "Some values could not be interpreted as type: timestamptz" which may occur if some values are incompatible or for some reason cannot be "cast" as datetime
16 replies
Schema and tables
Hi and welcome! Importing CSV to a schema other than the default is currently only supported from the command line (i.e. with
psql).
You will find the connection string to use with psql in your database's Settings page under "PostgreSQL endpoint". You can then create your custom schema and table(s) in it, and use the \copy command to import CSV \copy myschema.mytable FROM 'my.csv' csv;
Some more information about the issues you encountered:
The UI CSV importer uses Xata's REST API, which only supports the default schema and requires the built-in column xata_id. In case no xata_id is present in your CSV file, the id column is automatically used instead for it. There is a command-line tool in the xata CLI, xata import csv https://xata.io/docs/csv-data/import-data#import-data-with-an-auto-generated-schema which supports importing csv with your own id field, without a xata_id in the csv file, and it autogenerates values for xata_id, keeping your own id field as well. That said, this only works for the xata default schema.
More capabilities will be added to the UI importer down the line to support multiple schemas and avoid the xata_id/id interference.16 replies
Vector search with filtering.
This would be because there are 2 documents that match both the filter and the vector query. The size parameter is the max number of results to return but if there aren't enough matches then the API will only return those that satisfy the query parameters.
Is there a document returned when running the vector query with the filter not applied, which should normally match the filter and be returned when the filter is applied? If so, can you grant us access to your workspace by enabling the "Allow support to view your workspace" under Settings, and share here the the vector query you are using so we can reproduce and investigate?
11 replies