David S. Batista
David S. Batista
I've added a single disclaimer explaining that `_split_overlap` with Chroma is lost and added the same info to the docs. I would merge it now.
is this tied to a release or can the breaking change warning be generic, i.e.: "in the upcoming releases `gpt-3.5-turbo` will be replaced by `gpt-4o-mini` as de default model"
I've added a generic deprecation message not tied to any specific version
What's the current status of this issue? - It started with a proposal from @sjrl to enhance Haystack with more robust chunking methods (some of these methods are linked at...
Hi @alperkaya , thanks for your contribution. We need to treat this as a breaking change. Can you please also open a separate PR to issue a warning whenever `gpt-3.5-turbo`...
no need to add the warning to the tests just in the initialisation of the following components: - OpenAIChatGenerator - OpenAIGenerator
@alperkaya please sign the Contributor License Agreement otherwise this can't be merged. Just a few notes: - Be sure to fill in the PR comments giving a bit more details...
It's a good suggestion, but we can't just blindly convert everything back to integers. To make this generic, we need to know which type the values were originally, i.e.: before...
`` > Yes, I understand. > > I'm simply suggesting that we move the `_convert_to_int` method to Pinecone with the same keys used here. > ah ok, now I understand...
moving to core-integrations