typesense / typesense/typesense
Help Needed : Breaking Change: Auto Detect Wild Card for New Fields Dosent work in version upgrade 0.21 from 0.20
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 973
- Avg merge
- 18h 45m
- Merged PRs (30d)
- 4
Description
Description
Future fields that can't be determined before hand have to be indexed as Auto Detect
Steps to reproduce
Auto detection for fields with Wild Card dosent work in 0.21. When we set type as auto when name contains .* when creating the collection. What is the alternate for this or how best should we handle it.
Expected Behavior
Should be backward compatible with 0.20
Actual Behavior
Gives errors in production, as all such fields auto schema are marked as optional.
Metadata
Typsense Version: 0.21.0
OS: AWS Linux ECS optimised EC2 Instance
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. First reproduce wildcard auto-detection during collection creation on Typesense 0.21 and compare it with 0.20, then trace the schema behavior that marks these fields optional; done means backward-compatible handling without the reported production errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100