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
I searched existing ideas and did not find a similar one
I added a very descriptive title
I've clearly described the feature request and motivation for it
Feature request
When using "MilvusCollectionHybridSearchRetriever", I found that using "as_tool()" cannot specify the return of both content and artifact like using "@tool(response_format="content_and_artifact")". Should we consider adding support in future versions? Otherwise, it may be inconvenient to convert runnable to tool
Motivation
I think "as_tool()" should be as convenient as "@tool (responsive_format="content_and_artifact")"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Checked
Feature request
When using "MilvusCollectionHybridSearchRetriever", I found that using "as_tool()" cannot specify the return of both content and artifact like using "@tool(response_format="content_and_artifact")". Should we consider adding support in future versions? Otherwise, it may be inconvenient to convert runnable to tool
Motivation
I think "as_tool()" should be as convenient as "@tool (responsive_format="content_and_artifact")"
Proposal (If applicable)
No response
Beta Was this translation helpful? Give feedback.
All reactions