How Two Mapping Tweaks Cut Easysearch Index Size by One‑Third
A storage audit of an Easysearch cluster revealed that overly generic field mappings caused the index to bloat to 500‑600 GB, and by correcting two mapping mistakes—using text + autocomplete only where needed and storing numeric IDs as long types—the index size shrank by over 200 GB, roughly one‑third, without data loss or functional changes.
