Closed kingkupps closed 2 years ago
This might be a "works-as-intended" case, but knn_vector
is an OpenSearch type (docs are here).
There is also a workaround in that you can always create the index mapping ahead of time and leave off mappings in the pgsync schema. It would be really nice to be able to specify the mapping for documents that use knn_vector
from the schema though.
Hi,
I haven't quite worked out how to handle differences between opensearch and elasticsearch yet and there is bound to be more of these differences.
I'm happy to add knn_vector
for now.
Is this sufficient for your immediate use case?
Yes that should be good enough 👍
thia has now been added to the master branch
how to define the dimension and method fields in knn_vector type ? Getting an issue that dimension invalid elastic search mapping parameter .
PGSync version: 2.2.1
Postgres version: 12.5
Elasticsearch version: Opensearch 1.2.4
Redis version: 6.0.10
Python version: 3.10
Problem Description: PGSync does not allow fields mapped to the
knn_vector
type described here.Schema:
Error Message (if any):