Find answers from the community

s
F
Y
a
P
Updated 7 months ago

I am trying to use `IngestionPipeline`

I am trying to use IngestionPipeline to be executed locally but it has a dependency on llama_index_client which comes from a poetry module mapping:
Plain Text
poetry_requirements(
    name="poetry",
    module_mapping={"llamaindex-py-client": ["llama_index_client"]},
)

which is not installed by default, and even when installing llamaindex-py-client with pip, there is no way to get this mapping.

Therefore, I am wondering if we are able to use IngestionPipeline standalone ?
L
G
8 comments
hmm, this mapping is only used in our CICD, specifically by a tool called pants -- curious how this is causing issues?

llamaindex-py-client is included as a direct dependency of llama-index-core, which the ingestion pipeline comes from
@GeoloeG I've never seen anyone have this issue before πŸ˜… does pip show llamaindex-py-client show anything? pip install llamaindex-py-client should install it if not
indeed, it was not properly installed... but missed it in the Dockerfile which had a --no-deps for the pip install, let's see what are the conflicts...
fixed the dep issue! Thanks @Logan M
playing around with the RedisVectorStore, it seems that redisearch is a dep, but again is not installed with redis (5.0.1), will investigate and add this as dep if really needed for the integration
Actually, there's a large PR to refactor the redis vector store to use redisVL lol
Should be merged in a few days
Add a reply
Sign up and join the conversation on Discord