linuxuser
(Abhinav pandey)
September 11, 2021, 5:47am
21
Thanks for guidance
There is one doubt that what will be the effect if we use DEFLATE in elastic search at the place of LZ4. Is there any disadvantage rather than time?
gsmith
(GSmith)
September 13, 2021, 11:11pm
22
Hello,
I found these, they might help.
elastic:master
← rmuir:lucene_r1644303
opened 03:45AM - 10 Dec 14 UTC
upgrades lucene to latest, and supports the BEST_COMPRESSION parameter now suppo… rted (with backwards compatibility, etc) in Lucene. This option uses deflate, tuned for highly compressible data.
`index.codec`::
The `default` value compresses stored data with LZ4 compression, but
this can be set to `best_compression` for a higher compression ratio,
at the expense of slower stored fields performance.
IMO its safest to implement as a named codec here, because ES already has logic to handle this correctly, and because its unrealistic to have a plethora of options to Lucene's default codec... we are practically limited in Lucene to what we can support with back compat, so I don't think we should overengineer this and add additional unnecessary plumbing.
See also:
https://issues.apache.org/jira/browse/LUCENE-5914
https://issues.apache.org/jira/browse/LUCENE-6089
https://issues.apache.org/jira/browse/LUCENE-6090
https://issues.apache.org/jira/browse/LUCENE-6100
Here is a description of the two.
Deflate Defined
LZ4 Defined
I personal have not tried switching the data compression algorithm in elasticsearch.
system
(system)
Closed
September 27, 2021, 11:12pm
23
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.