Why not apply to Full text searches

I was doing some tests as part of 📌 Make Search API backend agnostic Needs review and it seems the reason this is not activated, is because type "string" seems to get a separate database table when using search_api_db, whereas type "text" does not. I haven't investigated this further, but this could probably be fixed if this behaviour is indeed correct and consistent.

This will get (partially) solved with 📌 Make Search API backend agnostic Needs review , there will be some limitations on full text fields regarding paged queries especially. Follow 📌 Make Search API backend agnostic Needs review if you are still interested.

Closing this issue as duplicate now.