Fields check should only run on VDB provider

Created on 20 March 2025, 17 days ago

Problem/Motivation

There is a small bug in the logic currently, when it verified the fields of the Postgres connection, when it tries to check if the backend is not postgres, it fails.

This causes issues when you have multiple VDB providers installed, since it will do a sanity check against the postgres provider, even if the index is another AI Search backend.

Steps to reproduce

1. Install two VDB Provider modules, where one is Postgres
2. Setup the none Postgres vdb provider and the other one fails when indexing.

Proposed resolution

Fix the if statement in the module file.

🐛 Bug report

Status

Active

Version

1.0

Component

Code

Created by

🇩🇪Germany marcus_johansson

Live updates comments and jobs are added and updated live.

Merge Requests

!3Fields check should only run on VDB provider
Merged
🇩🇪Germany marcus_johansson
updated 15 days ago

Comments & Activities

Issue created by @marcus_johansson
Merge request !3Resolve #3514289 "Fields check should" → (Merged) created by marcus_johansson
Comment 17 days ago →
🇩🇪Germany marcus_johansson
Comment 16 days ago →
🇬🇧United Kingdom justanothermark
Looks like a good description of the issue and a good fix to me. Marking as RTBC.
Comment 16 days ago →
🇩🇪Germany marcus_johansson
Comment 15 days ago →
System Message

marcus_johansson → committed 7ceb49e1 on 1.0.x
Resolve #3514289 "Fields check should"
Comment 15 days ago →
🇩🇪Germany marcus_johansson
Comment 1 day ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024