Bug #95270 for REST-Neo4p: Legacy fulltext index does not work with utf8 string values

Hi Andrii, I hope I can look at your issues soon, probably this weekend Cheers Mark Sent from my T-Mobile 4G LTE Device <div>-------- Original message --------</div><div>From: "stesin@gmail.com via RT" <bug-REST-Neo4p@rt.cpan.org> </div><div>Date:05/02/2014 7:27 AM (GMT-05:00) </div><div>To: </div><div>Subject: [rt.cpan.org #95270] Legacy fulltext index does not work with utf8 string values </div><div> </div>Fri May 02 07:27:58 2014: Request 95270 was acted upon. Transaction: Ticket created by stesin@gmail.com Queue: REST-Neo4p Subject: Legacy fulltext index does not work with utf8 string values Broken in: 0.2242 Severity: (no value) Owner: Nobody Requestors: stesin@gmail.com Status: new Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=95270 > Dear Mark, I'm not sure is it a bug or maybe some kind of my fault. I have a bunch of nodes with text properties payload, say {code} (n:MyNode {name_ua: 'some utf8 Cyrillic text in Ukrainian'}) {code} I want to do fulltext search on name_ua, so: - I created the fulltext name_ua_index, - run script which performs query {code} MATCH (n:MyNode) RETURN n {code} - script loops fetching node array refs $node_aref one by one and does {code} unless( defined($node_aref->[0]) ) { last MYNODE; }; $name_ua_index->add_entry( $node_aref->[0], 'name_ua' => $node_aref->[0]->get_property( 'name_ua' ) ) or die "Failed to add " . $node_aref->[0]->get_property( 'name_ua' ) . " into index, stopped"; {code} Ok so far, but given I am 100% sure I *do* have an indexed string (n:MyNode {name_ua: 'Вітаю зі святом'}), I can not match it with START n = node:name_ua_index("name_ua:віта*") whatever I try. What I am doing wrong? Thanks in advance! WBR, Andrii