field has \n LIKE gives wrong results index vs non index scan(primary)

The \n makes difference.

insert into default values("kk20",{"text":"[[File:River \nFile Thames"});

select * from default USE KEYS "kk20" WHERE text LIKE "Fil%";

Above query returns results. Is this expected ? If yes

CREATE INDEX ix20 ON default(text);

select * from default WHERE text LIKE "Fil%";

With Index scan returns 0 results because we used prefix Scan which doesn't match with runtime LIKE evaluation.

If Indexscan result in wrong results we should not use that index.