Closed Mazzesy closed 5 months ago
https://github.com/run-llama/llama_index/blob/main/llama-index-core/llama_index/core/utils.py#L48
Looks it has been replaced by NLTK_DATA
@logan-markewich is it expectd?
Hi, @Mazzesy,
I'm helping the LlamaIndex team manage their backlog and am marking this issue as stale. The reported issue involved the LLAMA_INDEX_CACHE_DIR
environment variable not being respected by LlamaIndex, despite following the documentation. User semoal suggested that the variable has been replaced by NLTK_DATA
, and the maintainers, including logan-markewich, were asked if this replacement is expected.
Could you please confirm if this issue is still relevant to the latest version of the LlamaIndex repository? If it is, please let the LlamaIndex team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days.
Thank you for your understanding and cooperation. If you have any further questions or need assistance, feel free to reach out to me or the LlamaIndex team.
Bug Description
According to the documentation (Link), I can control the location where additional data is downloaded by setting the
LLAMA_INDEX_CACHE_DIR
environment variable. However, despite setting this environment variable, LlamaIndex seems to ignore it and continues to store data in a different location.Version
0.10.4
Steps to Reproduce
Here's how I'm setting the environment variable in my Python script:
When creating the index storage (see code below),
nltk_data
gets downloaded to /Users/user/nltk_data instead of the path I set as the environment variable.Relevant Logs/Tracbacks