What could be down sides of using mysql json field instead of many nullable fields on a table in laravel 5

As you know, mysql 5.7 provides json fields. What could be down sides of using a data json fields instead of having many nullable fields on a table? Let's say i'm working on a products table which has length, width, height, thickness, margin, ... all in nullable property. I think is better to use json data column instead of using all these nullable columns. But i don't know what could be down sides!

from Newest questions tagged laravel-5 - Stack Overflow http://ift.tt/2rfg6N8
via IFTTT