-
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Because the database tables have been modified, you can connect to the PostgreSQL database and then execute the following code: ALTER TABLE nexent.model_record_t |
Beta Was this translation helpful? Give feedback.
-
|
The reason is that Nexent has been updated. Alternatively, you can simply delete the original image and redeploy. |
Beta Was this translation helpful? Give feedback.
-
|
Thank u |
Beta Was this translation helpful? Give feedback.
-
重新部署之后还是这种情况，我是重新从第一步开始的
|
Beta Was this translation helpful? Give feedback.
-
|
You deployed using Docker, right? The problem might be because you didn't delete the original image. Was your redeployment fast? That's because you're using the original image. You need to delete the container and image entirely within Docker, then redeploy. |
Beta Was this translation helpful? Give feedback.
Because the database tables have been modified, you can connect to the PostgreSQL database and then execute the following code:
ALTER TABLE nexent.model_record_t
ADD COLUMN expected_chunk_size INT4,
ADD COLUMN maximum_chunk_size INT4;
COMMENT ON COLUMN nexent.model_record_t.expected_chunk_size IS 'Expected chunk size for embedding models, used during document chunking';
COMMENT ON COLUMN nexent.model_record_t.maximum_chunk_size IS 'Maximum chunk size for embedding models, used during document chunking';