Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify what happened on successful upsert #33

Open
zackproser opened this issue Jan 8, 2024 · 1 comment
Open

Clarify what happened on successful upsert #33

zackproser opened this issue Jan 8, 2024 · 1 comment

Comments

@zackproser
Copy link
Contributor

zackproser commented Jan 8, 2024

On successful upsert, we currently show:

  • N results

Like this:

vercel-starter-results-count

I think this feature is awesome, but it could be more clear what happened. Something like:

N results successfully converted to embeddings and upserted to your Pinecone index: ${process.env.PINECONE_INDEX}

@zackproser
Copy link
Contributor Author

By the way, it might be a nice change to also add a fetching, crawling, scraping, etc state to the frontend app.

Currently, the button only says "embed and upsert" so it's less clear that the app is actually:

  • Reading from a web page
  • Converting that text into embeddings
  • Upserting the embeddings to Pinecone, etc.

A lower lift that could accomplish the same end goal would be a sentence or two of descriptive text above the "embed and upsert" button explaining what the app is doing when you click that button?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant