Improve langchain4J integration #771
Replies: 4 comments 3 replies
-
Never mind the previous comment. I actually see we only configure @jmartisk does it make sense to move into the core? |
Beta Was this translation helpful? Give feedback.
-
Yeah I found that some useful things are currently only in easy-rag:
Compounded to that, when you add easy rag to the classpath, you then have to set it up (path etc), so you cannot use it as a simple dependency. It makes the easy rag to less easy rag a big wall. I wonder if we want to move these conversdations in Discussions as "Improve langchain4J integration". WDYT? Emmanuel |
Beta Was this translation helpful? Give feedback.
-
Makes sense! I'm on a phone now, so I'll check if I can move the issue when I get to a proper machine |
Beta Was this translation helpful? Give feedback.
-
I want to see how we can move forward. My understanding is that at the moment we have the following behavior
So I think we need to define the expected ideal behavior and a way to scale in complexity (e.g. multiple dependencies e.g. between dev and prod or two flows in a single app) What do you think we should do? |
Beta Was this translation helpful? Give feedback.
-
From
I did that because the Redis example seem to imply it works
https://docs.quarkiverse.io/quarkus-langchain4j/dev/retrievers.html
Adding this class "fixed" the problem
Beta Was this translation helpful? Give feedback.
All reactions