lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Svensson <si...@devhost.se>
Subject Re: Lucene 3.0.3 index reported as 2.9?
Date Thu, 01 Aug 2013 14:37:07 GMT
Hi,

I think so. Reading [Index File Formats][1] notes "In version 3.0, 
compressed fields are no longer written to the index (they can still be 
read, but on merge the new segment will write them, uncompressed)." This 
sounds like an implementation detail, and wouldn't require changes to 
the index format.

// Simon

[1]: http://lucene.apache.org/core/3_5_0/fileformats.html#Index File Formats

On 2013-08-01 16:27, Allan, Brad (Bracknell) wrote:
>
> Hi
>
> I recently update our code line to 3.0.3. When I look in Luke, the 
> index format is reported as 2.9 -- is this expected behaviour?
>
> *Brad Allan
> *Development Manager
>
> Risk & Compliance
>
> *Fiserv*
> Office: +44 (0) 845 013 1137
> Mobile: +44 (0) 786 672 0024
> www.fiserv.com <http://www.fiserv.com/>
>
>
> ------------------------------------------------------------------------
>
> CheckFree Solutions Limited (trading as Fiserv)
> Registered Office: Eversheds House, 70 Great Bridgewater Street, 
> Manchester, M15 ES
> Registered in England: No. 2694333


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message