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

Search Failed: Make sure that your index has a 'default' sementic configuration. #208

Open
divyansh-23906 opened this issue Jul 4, 2023 · 4 comments

Comments

@divyansh-23906
Copy link

Deployed using redis openai template and followed every step from the 4th video, and getting the same response for every request - 'Search Failed: Make sure that your index has a 'default' sementic configuration'. Why is this happening and how can I fix it?

@divyansh-23906
Copy link
Author

divyansh-23906 commented Jul 6, 2023

@hoffj66 Thought after yesterday's update maybe some things have been fixed. Deployed everything once again using vector store deployment template, used pre-built vector search pipeline, uploaded document, still getting same response.
image

@hoffj66
Copy link
Contributor

hoffj66 commented Jul 6, 2023

From the screen shot it looks like the pipeline name is blank? Are you internal MS? It's hard to tell from the screen. Maybe we could do a screen share.

@divyansh-23906
Copy link
Author

divyansh-23906 commented Jul 7, 2023

Hi James, we can certainly try screen share and maybe you can see where's the problem coming from.
About the blank pipeline it is one the pre-built pipeline which is in three stages and it's last stage name is '-stage3' which you can see is selected as the vector index in the screenshot.
Also the app is deployed and if you connect with me on teams, I'll share the link of the static app with you and you can see for yourself.
Thanks for replying 🙂

@hoffj66
Copy link
Contributor

hoffj66 commented Jul 7, 2023

The intention is that you put a name into the input before creating the pipeline. it uses that name in several places. It should create "example-stage1, example-stage2...."

I'm having capacity issues today and not able to test all of the templates. It looks like there was another round of model additions and deletions. When they remove one it breaks the deployment templates.

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

2 participants