-
Notifications
You must be signed in to change notification settings - Fork 384
Add Knowledgebase #1795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Add Knowledgebase #1795
Conversation
The latest Buf updates on your PR. Results from workflow Buf CI / lint-and-breaking (pull_request).
|
// KnowledgeBase ID. | ||
string id = 1 [ | ||
(google.api.field_behavior) = REQUIRED, | ||
(buf.validate.field).required = true, | ||
(buf.validate.field).string.pattern = "^[A-Za-z0-9-_/]+$" | ||
]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should autogenerate the id and not have it user-specified I think.
Also this id will likely go into a Kafka topic name (e.g. __redpanda_cloud__rag_<kb-id>_source_confluence-with-id
) so we need to limit the character set. Slashes wouldn't be allowed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh yeah, absolutely. my mistake. should be xid
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the resource. so it's required, because it's never an input
} | ||
|
||
oneof vector_database { | ||
Postgres postgres = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we differentiate as db type, since there are many flavours of postgres based DBs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what different fields would we support? in the end, it's a conn via PG protocol. and, i guess, it needs pgvector, we could also call it PGVector
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 call it PGVector - we shouldn't be specific and will want to support different extensions I'm sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbh, i did not go for PGVector. In the end, this is just postgres: dsn, table, ...
not suuper important for me though
} | ||
|
||
oneof vector_database { | ||
Postgres postgres = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 call it PGVector - we shouldn't be specific and will want to support different extensions I'm sure
EmbeddingGenerator embedding_generator = 6 [ | ||
(google.api.field_behavior) = REQUIRED, | ||
(buf.validate.field).required = true | ||
]; | ||
|
||
// API url for retrieval API, that allows lookup of documents. | ||
string retrieval_api_url = 4 [(google.api.field_behavior) = OUTPUT_ONLY]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
funky field number ordering?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah i will get it ordered before merging, still iterating a bit
c34d0b2
to
caedc8c
Compare
The latest Buf updates on your PR. Results from workflow Buf CI / validate (pull_request).
|
8b0116d
to
96c0ea1
Compare
96c0ea1
to
9553bf1
Compare
8f6c7b3
to
cbcdcfd
Compare
247c9a1
to
f58a32d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very interesting piece of code, could be a beginning of a way to integrate it with auto form component to use grpc for validating the form directly without any intermediate measures.
@@ -188,6 +194,8 @@ const setConfig = ({ fetch, urlOverride, jwt, isServerless, featureFlags, ...arg | |||
transformsClient: transformClient, | |||
rpcnSecretsClient: secretGrpcClient, | |||
clusterStatusClient: clusterStatusGrpcClient, | |||
knowledgebaseClient: knowledgebaseGrpcClient, | |||
userClient: userGrpcClient, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do we use userClient
for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i added it for the "auto create users", but had to stop implementing it, it was a bit too tricky.
i can remove the client - i did keep it because it's reasonable to have this client available
}; | ||
|
||
@observer | ||
class KnowledgeBaseList extends PageComponent<{}> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an outdated pattern as well.
We should use functional React components (not class-based), and try to do something similar to frontend/src/components/pages/agents/create/create-agent-page.tsx where you do not rely on any MobX state at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done, could you check the result is what you expected?
84ef6f2
to
e2b00b3
Compare
1e53e73
to
1cbacde
Compare
migrated to v1alpha3 |
buf.yaml
Outdated
@@ -27,3 +27,4 @@ breaking: | |||
ignore: | |||
- redpanda/api/console/v1alpha1 | |||
- redpanda/api/dataplane/v1alpha1 | |||
- proto/redpanda/api/dataplane/v1alpha1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this can be removed now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
c36056a
to
d4e982e
Compare
d4e982e
to
4766383
Compare
191aa88
to
d454f96
Compare
36b2e82
to
91c9283
Compare
62e08a0
to
e5ae477
Compare
e5ae477
to
efbfcf0
Compare
Uh oh!
There was an error while loading. Please reload this page.