opengauss vector functionality support

[jzs1997]

Description

opengauss also suport vector data type and distance calculation since 7.0.0
Found that the syntax for vector operations in opengauss is similar to pgvector, so reuse the code of pgvector handler to as an approach.

Type of change

(Please delete options that are not relevant)

• [ x] ⚡ New feature (non-breaking change which adds functionality)

Verification Process

To ensure the changes are working as expected:

• Test Location: Specify the URL or path for testing.
• [x ] Verification Steps: Outline the steps or queries needed to validate the change. Include any data, configurations, or actions required to reproduce or see the new functionality.

• Test Queries:

CREATE DATABASE opengauss_datasource  
WITH ENGINE = 'opengauss',
PARAMETERS = {
  "host": "localhost",                  
  "user": "bot",                  
  "password": "Huawei@123",             
  "port": 8094,               
  "database": "postgres"              
};

DROP DATABASE opengauss_datasource;

-- opengauss_datasource.tv1: a table contains a vector column
-- Create tv1 in opengauss
-- CREATE TABLE tv1(id int, content varchar(255), val vector(3));

SELECT * FROM opengauss_datasource.tv1 LIMIT 5;
SELECT * FROM opengauss_datasource.tv1 where val = '[1,2,3]';
insert into opengauss_datasource.tv1 (id, content, val) values(5, 'abvc', '[2, 3, 4]');
update opengauss_datasource.tv1 set val = '[3,4,5]' where id = 2;
SELECT * FROM opengauss_datasource.tv1 ORDER BY val <-> '[1, 2, 3]' LIMIT 5;
SELECT * FROM opengauss_datasource.tv1 ORDER BY val <#> '[1, 2, 3]' LIMIT 5;
SELECT * FROM opengauss_datasource.tv1 ORDER BY val <=> '[1, 2, 3]' LIMIT 5;
DELETE FROM opengauss_datasource.tv1 WHERE val = '[2, 3, 4]';
CREATE TABLE opengauss_datasource.tv2(select * from opengauss_datasource.tv1);

-- original sql which do not contain vector type
CREATE TABLE opengauss_datasource.items(val int);
INSERT INTO opengauss_datasource.items(val) values(1);
drop table opengauss_datasource.items;

SELECT * FROM opengauss_datasource.items LIMIT 5;
SELECT * FROM opengauss_datasource.items WHERE val < 10;
UPDATE opengauss_datasource.items SET val = 2 WHERE val = 1;
DELETE FROM opengauss_datasource.items WHERE val = 1;

Checklist:

• My code follows the style guidelines(PEP 8) of MindsDB.
• I have appropriately commented on my code, especially in complex areas.
• Necessary documentation updates are either made or tracked in issues.
• Relevant unit and integration tests are updated or added.

[mindsdbadmin]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[jzs1997]

I have read the CLA Document and I hereby sign the CLA

[MinuraPunchihewa]

Hi @jzs1997,
I believe that this makes it so that the OpenGauss integration can now only be used as a vector store and no longer as a data store? I think it would be best if we can create a separate integration for using it as a vector database instead.

[jzs1997]

Hi @jzs1997, I believe that this makes it so that the OpenGauss integration can now only be used as a vector store and no longer as a data store? I think it would be best if we can create a separate integration for using it as a vector database instead.

Hi @MinuraPunchihewa, thank you for your advices, I have some questions about this. I tried some non vector store SQL queries and they still work, could you please elaborate a bit on 'can now only be used as a vector store and no longer as a data store'.

In openGauss, vector store functionality is integrated by default, which means user can use both relational database functions and vector database functions.

Could you please give some hints on 'separate integration', I sort of do not know how to do that.