Hi Roy, Lucene uses Java Service Loader for identifying extensions of its APIs (codec, tokenizer, etc.), the mentioned OakCodec [1] implementation sits in oak-lucene.
Regards, Tommaso [1] : https://github.com/apache/jackrabbit-oak/blob/trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/OakCodec.java Il giorno lun 8 mag 2017 alle ore 15:22 Roy Teeuwen <[email protected]> ha scritto: > Hey Tommaso, > > Cool thanks. I tried it out, and when using luke-4.7.0 jar I get the > following exception: > > Invalid directory at the location, check console for more information. > Last Exception: java.lang.IllegalArgumentException: A SPI class of type > org.apache.lucene.codes.Codec with name 'oakCodec' does not exist. You need > to add the corresponding jar file supporting this SPI to your classpath. > > Could you tell me which jar it is that I should be adding to the > classpath? Thanks! > > Greetings > Roy > > On 8 May 2017, at 15:07, Tommaso Teofili <[email protected]> wrote: > > > > Hi Roy, > > > > if you have copy on read enabled (it is by default) for the Oak Lucene > > index you should be able to take the index at their paths on the file > > systems and use Luke as per any other Lucene index (btw Oak is currently > > using Lucene 4.7.1). > > > > Hope it helps, > > Tommaso > > > > [1] : http://jackrabbit.apache.org/oak/docs/query/lucene.html#CopyOnRead > > > > Il giorno lun 8 mag 2017 alle ore 15:01 Roy Teeuwen <[email protected]> ha > > scritto: > > > >> Hey all, > >> > >> I got a question relating the oak:indexes in Jackrabbit OAK. Is it > >> possible to actually open these indexes and see what is inside them? I > know > >> it is possible to use Luke to open a Lucene index and query it > manually, is > >> this also possible for the property index and the Lucene index inside > oak? > >> If so, how would I go about this, where are they situated on file > system so > >> that I could open them with Luke or something > >> > >> Thanks! > >> Roy > >> > >
