You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UPDATE: I will be going with approach 2 and give examples in the documentation. If you do have feedback, please comment. Thanks!
In the 3.x client, creating index signature has changed. Now, they use podSpec or serverlessSpec classes to pass configurations w.r.t infra. I've been thinking how to rewrite the hook and am split between two ways and need help in finalizing which one to go with.
Approach 1:
will have two methods in PineconeHook namely create_pod_index and create_serverless_index which will take all possible parameters w.r.t index and the spec and internally will create the Spec object and pass it to the create_index method
method will be as follows for the pod based index creation
Will have helper methods to create PodSpec and ServerlessSpec objects and then have the create_index method follow the pinecone signature and accept only one of these two types.
@rawwar difficult to say which approach are better. I can't find any usage into the operators, so assume this might only use into the custom operators or taskflow operators, so maybe create method create_index_from_spec?
Activity
rawwar commentedon Feb 7, 2024
I will be working on this. Thanks
rawwar commentedon Feb 15, 2024
UPDATE: I will be going with approach 2 and give examples in the documentation. If you do have feedback, please comment. Thanks!
Taragolis commentedon Feb 17, 2024
@rawwar difficult to say which approach are better. I can't find any usage into the operators, so assume this might only use into the custom operators or taskflow operators, so maybe create method
create_index_from_spec?rawwar commentedon Feb 22, 2024
rawwar commentedon Apr 12, 2024
I am picking this back up.