Fix: ts upload file does not create index and document store

[leehuwuj]

Summary by CodeRabbit

• New Features

  • Enhanced file upload process to automatically create an index and document store when uploading files without an existing index.
  • Introduced a default environment variable for local storage cache to improve configuration.

• Bug Fixes

  • Improved handling of null indices during document uploads, ensuring a more robust and reliable experience.
  • Added error handling for missing environment variables, enhancing reliability during storage context initialization.

• Documentation

  • Updated log messages to better reflect the actions taken during index creation.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: bdd7416e0e9258e776e5eddb74377bbb6c2f7484

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

| Name | Type | | ------------ | ----- | | create-llama | Patch |

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai[bot]]

Walkthrough

A new patch titled "create-llama" has been introduced to ensure that both the index and document store are created when a file is uploaded without an existing index. This change modifies the runPipeline function to incorporate a new storage context and updates the logic for index creation, enhancing the robustness of the file upload process.

Changes

File Path	Change Summary
.changeset/big-turtles-own.md	Added patch "create-llama" to ensure index and document store creation during file uploads.
templates/components/llamaindex/typescript/documents/pipeline.ts	Updated runPipeline function to use storageContextFromDefaults and modified index creation logic.
helpers/env-variables.ts	Modified getVectorDBEnvs to return a default environment variable for STORAGE_CACHE_DIR.
templates/components/vectordbs/typescript/none/shared.ts	Removed hardcoded STORAGE_CACHE_DIR constant.
templates/components/vectordbs/typescript/none/generate.ts	Added check for STORAGE_CACHE_DIR environment variable in generateDatasource function.
templates/components/vectordbs/typescript/none/index.ts	Introduced check for STORAGE_CACHE_DIR in getDataSource function.

Possibly related PRs

• #149: The main PR introduces a patch titled "create-llama," which is also referenced in this PR that adds functionality related to using LlamaCloud for chat, indicating a direct connection in terms of the feature being developed.
• #202: This PR also includes a patch labeled "create-llama," focusing on enhancing reusability for chat LLM components, which aligns with the main PR's objective of improving file upload processes related to Llama.
• #236: The changes in this PR involve implementing the LlamaCloud pipeline, which is relevant to the main PR's focus on creating a robust file upload process that integrates with LlamaCloud.
• #343: This PR updates the dependency to use the latest LITS version, which may relate to the enhancements in the main PR regarding the integration of LlamaCloud functionalities.
• #352: This PR specifies that the generate script for LlamaCloud is no longer required, which could simplify the implementation discussed in the main PR regarding file uploads and indexing.
• #378: This PR enhances data types, which may relate to the changes in the main PR that involve improving the handling of document uploads and metadata.

Suggested reviewers

• thucpn
• marcusschiesser

Poem

🐰 In fields of data, we hop and play,
With "create-llama," we pave the way.
When files are uploaded, no index in sight,
We build them anew, making everything right!
So let’s cheer for the changes, both big and small,
For a smoother upload, we’ll have a ball! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.