Issue with 'Auto' Type in Collection Schema
TLDR Gabriel reported an issue with the 'auto' type in collection schema. Kishore Nallan recommended trying the 0.23 RC builds which resolved the issue.
Powered by Struct AI
1
3
22mo
Mar 10, 2022 (22 months ago)
Gabriel
Gabriel
03:49 PMHi, I have a question.
At some point this schema was valid and working:
[
{'name': 'fname', type: 'string'},
{ 'name' : 'user', type: 'auto' }
]
but now if I try to create a new collection it says "Cannot use type
So has this been changed and 'auto' can no longer be set if the name is not '.*' ?
At some point this schema was valid and working:
[
{'name': 'fname', type: 'string'},
{ 'name' : 'user', type: 'auto' }
]
but now if I try to create a new collection it says "Cannot use type
auto for user. It can be used only for a field name containing .*" "So has this been changed and 'auto' can no longer be set if the name is not '.*' ?
Kishore Nallan
Kishore Nallan
04:10 PMI think we fixed this regression on the 0.23 RC builds. Can you check against that?
1
Gabriel
Gabriel
04:44 PMok worked with 0.23 20RC
Typesense
Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI
Indexed 3015 threads (79% resolved)
Similar Threads
Fixing "bad json" error in Typesense 0.24
Adam experiences "bad json" error when creating collections in Typesense 0.24. Jason identifies a typo in the docs causing the error and helps troubleshoot additional errors.
23
9mo
Auto-generating Typesense Collection Types with TypeScript
Udo asked about auto-generating types using schema definitions in Typesense. Jason clarified the limitations and suggested defining types manually. Udo agreed to add TypeScript notes to README.
7
9mo
Troubleshooting RequestMalformed Error in Schema Creation
Ailish had issues with creating a schema and received a "RequestMalformed Error". Jason advised making `"type": "auto"` fields optional and specifying the types upfront.
6
21mo