hi from a jcr point of view i would expect it to work but it might well be that this hasn't been carefully tested.
may i suggest that write a simple unit-test and attach it to a jira issue? that's probably to best way to get it verified and fixed if there was an issue. kind regards angela ps: since there is not much active development in jackrabbit-core, it would good if you could also try it with jackrabbit-oak... this is where most of efforts are being put into. On 27/10/15 09:13, "techie2k" <developer.spr...@gmail.com> wrote: >Hi, > >I'm using jackrabbit 2.8.0 and tika-parser 1.3 > >Adding custom node 'et:document' with 'nt:resource' as binary file content > >While trying to make full text search using following query, english >phrases, returns result, but arabic phrases always yields empty result >set. > >*String query2 = "//element(*,et:document)[jcr:contains(*, '*\""+ >searchParam +"\"*')]"; //Content Search >QueryManager queryManager = session.getWorkspace().getQueryManager(); >Query testQuery= queryManager.createQuery(query, Query.XPATH); >// execute query and fetch result >QueryResult testResult = testQuery.execute(); >NodeIterator nodes = testResult.getNodes(); >* > > >Does jackrabbit support arabic text search?? > >I tried JCR.SQL2 query, different tika-parser config, but to no avail. > >Thanks. > > > >-- >View this message in context: >http://jackrabbit.510166.n4.nabble.com/Arabic-content-search-tp4663228.htm >l >Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
