# 0.21.0.Beta Status (Lucene 4.x) **URL:** \ **Category:** Elasticsearch\ **Created:** [February 12, 2013, 11:01pm UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718 "2013-02-12T23:01:07Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [February 12, 2013, 11:01pm UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/1 "2013-02-12T23:01:07Z")
Heya fellows, Wanted to give a quick update regarding 0.21.0.Beta release with Lucene 4.x. As I mentioned, we have already fully upgraded to Luceen 4.1, and practically done with exposing the most important features we can get for it. We also concluded our major refactoring for a field data code that has significant reduction in memory used for field data (specifically multi valued fields) for faceting/sorting/scripts. The last major bit we have left is additional refactoring on our faceting code, to allow for more pluggable faceting implementation and different execution modes. The work is progressing nicely, and I hope that by next week we will be able to release 0.21.0.Beta with it in it. Once the Beta is out, we will have a short release cycle gearing towards GA, hopefully it should't take long. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Justin\_Treher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justin_treher/32/45243_2.png) [@Justin\_Treher](https://discuss.elastic.co/u/Justin_Treher)\ **Post date:** [February 13, 2013, 1:45pm UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/2 "2013-02-13T13:45:25Z")
Thanks for the communication! On Tuesday, February 12, 2013 6:01:07 PM UTC-5, kimchy wrote: > Heya fellows, > > Wanted to give a quick update regarding 0.21.0.Beta release with Lucene > 4.x. As I mentioned, we have already fully upgraded to Luceen 4.1, and > practically done with exposing the most important features we can get for > it. We also concluded our major refactoring for a field data code that has > significant reduction in memory used for field data (specifically multi > valued fields) for faceting/sorting/scripts. > > The last major bit we have left is additional refactoring on our faceting > code, to allow for more pluggable faceting implementation and different > execution modes. The work is progressing nicely, and I hope that by next > week we will be able to release 0.21.0.Beta with it in it. > > Once the Beta is out, we will have a short release cycle gearing towards > GA, hopefully it should't take long. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jagdeep](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@jagdeep](https://discuss.elastic.co/u/jagdeep)\ **Post date:** [February 13, 2013, 1:55pm UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/3 "2013-02-13T13:55:24Z")
Thanks Shay for the update. Eagerly looking forward for the new release. On Wednesday, February 13, 2013 4:31:07 AM UTC+5:30, kimchy wrote: > Heya fellows, > > Wanted to give a quick update regarding 0.21.0.Beta release with Lucene > 4.x. As I mentioned, we have already fully upgraded to Luceen 4.1, and > practically done with exposing the most important features we can get for > it. We also concluded our major refactoring for a field data code that has > significant reduction in memory used for field data (specifically multi > valued fields) for faceting/sorting/scripts. > > The last major bit we have left is additional refactoring on our faceting > code, to allow for more pluggable faceting implementation and different > execution modes. The work is progressing nicely, and I hope that by next > week we will be able to release 0.21.0.Beta with it in it. > > Once the Beta is out, we will have a short release cycle gearing towards > GA, hopefully it should't take long. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Leonardo\_Menezes](https://avatars.discourse-cdn.com/v4/letter/l/b487fb/32.png) [@Leonardo\_Menezes](https://discuss.elastic.co/u/Leonardo_Menezes)\ **Post date:** [February 14, 2013, 8:25am UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/4 "2013-02-14T08:25:16Z")
Hey Shay, that's great news. For the new code in faceting, should we also expect performance improvement, or just memory? thanks Leonardo Menezes (+34) 688907766 [http://lmenezes.com](http://lmenezes.com) On Wed, Feb 13, 2013 at 2:55 PM, jagdeep [reach.jagdeep@gmail.com](mailto:reach.jagdeep@gmail.com) wrote: > Thanks Shay for the update. Eagerly looking forward for the new release. > > On Wednesday, February 13, 2013 4:31:07 AM UTC+5:30, kimchy wrote: > > > Heya fellows, > > > > Wanted to give a quick update regarding 0.21.0.Beta release with Lucene > > 4.x. As I mentioned, we have already fully upgraded to Luceen 4.1, and > > practically done with exposing the most important features we can get for > > it. We also concluded our major refactoring for a field data code that has > > significant reduction in memory used for field data (specifically multi > > valued fields) for faceting/sorting/scripts. > > > > The last major bit we have left is additional refactoring on our faceting > > code, to allow for more pluggable faceting implementation and different > > execution modes. The work is progressing nicely, and I hope that by next > > week we will be able to release 0.21.0.Beta with it in it. > > > > Once the Beta is out, we will have a short release cycle gearing towards > > GA, hopefully it should't take long. > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\ **Post date:** [February 14, 2013, 8:41am UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/5 "2013-02-14T08:41:38Z")
"We also concluded our major refactoring for a field data code that has significant reduction in memory used for field data" - this is great news for me 🙂 I can't wait for the release 🙂 2013/2/14 Leonardo Menezes [leonardo.menezess@gmail.com](mailto:leonardo.menezess@gmail.com) > Hey Shay, > that's great news. For the new code in faceting, should we also expect > performance improvement, or just memory? thanks > > Leonardo Menezes > (+34) 688907766 > [http://lmenezes.com](http://lmenezes.com) > > On Wed, Feb 13, 2013 at 2:55 PM, jagdeep [reach.jagdeep@gmail.com](mailto:reach.jagdeep@gmail.com) wrote: > > > Thanks Shay for the update. Eagerly looking forward for the new release. > > > > On Wednesday, February 13, 2013 4:31:07 AM UTC+5:30, kimchy wrote: > > > > > Heya fellows, > > > > > > Wanted to give a quick update regarding 0.21.0.Beta release with Lucene > > > 4.x. As I mentioned, we have already fully upgraded to Luceen 4.1, and > > > practically done with exposing the most important features we can get for > > > it. We also concluded our major refactoring for a field data code that has > > > significant reduction in memory used for field data (specifically multi > > > valued fields) for faceting/sorting/scripts. > > > > > > The last major bit we have left is additional refactoring on our > > > faceting code, to allow for more pluggable faceting implementation and > > > different execution modes. The work is progressing nicely, and I hope that > > > by next week we will be able to release 0.21.0.Beta with it in it. > > > > > > Once the Beta is out, we will have a short release cycle gearing towards > > > GA, hopefully it should't take long. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [February 14, 2013, 8:51am UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/6 "2013-02-14T08:51:12Z")
I think the facet framework is going to be overhauled to add custom facet features more easily. For example, right now, there can't be plugins that add new capabilities to faceting. So I hope I can use collation based sorting on facet elements soon, or facet value mappings, where facet values can be augmented with other values for display (like sort keys in collations). Jörg Am 14.02.13 09:25, schrieb Leonardo Menezes: > Hey Shay, > that's great news. For the new code in faceting, should we also > expect performance improvement, or just memory? thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Nicolas\_Blanc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolas_blanc/32/2030_2.png) [@Nicolas\_Blanc](https://discuss.elastic.co/u/Nicolas_Blanc)\ **Post date:** [February 14, 2013, 10:15am UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/7 "2013-02-14T10:15:22Z")
As we need one boring guy... Is this means that i am near to trash my nightmare code about grouping ? Mainstream ES will be able to group soon ? 🙂 -- Nicolas BLANC. Le mercredi 13 février 2013 00:01:07 UTC+1, kimchy a écrit : > Heya fellows, > > Wanted to give a quick update regarding 0.21.0.Beta release with Lucene > 4.x. As I mentioned, we have already fully upgraded to Luceen 4.1, and > practically done with exposing the most important features we can get for > it. We also concluded our major refactoring for a field data code that has > significant reduction in memory used for field data (specifically multi > valued fields) for faceting/sorting/scripts. > > The last major bit we have left is additional refactoring on our faceting > code, to allow for more pluggable faceting implementation and different > execution modes. The work is progressing nicely, and I hope that by next > week we will be able to release 0.21.0.Beta with it in it. > > Once the Beta is out, we will have a short release cycle gearing towards > GA, hopefully it should't take long. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [February 14, 2013, 3:49pm UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/8 "2013-02-14T15:49:19Z")
Exciting news. I have an idea for a new facet type, but the current framework is too much work for a feature I do not fully need. New fuzzy queries means spell checking soon as well? -- Ivan On Thu, Feb 14, 2013 at 12:51 AM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > I think the facet framework is going to be overhauled to add custom facet > features more easily. For example, right now, there can't be plugins that > add new capabilities to faceting. > > So I hope I can use collation based sorting on facet elements soon, or > facet value mappings, where facet values can be augmented with other values > for display (like sort keys in collations). > > Jörg > > Am 14.02.13 09:25, schrieb Leonardo Menezes: > > Hey Shay, > > > ``` > > that's great news. For the new code in faceting, should we also > > > > ``` > > > > expect performance improvement, or just memory? thanks > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscribe@\*\*[googlegroups.com](http://googlegroups.com)[elasticsearch%2Bunsubscribe@googlegroups.com](mailto:elasticsearch%2Bunsubscribe@googlegroups.com) > . > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > . -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![mattweber](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattweber/32/44940_2.png) [@mattweber](https://discuss.elastic.co/u/mattweber)\ **Post date:** [February 14, 2013, 5:23pm UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/9 "2013-02-14T17:23:45Z")
Spell checking/suggestions is already in master.... > > > \# Suggest feature > > The suggest feature suggests similar looking terms based on a… provided text by using a suggester. At the moment there the only supported suggester is \`fuzzy\`. The suggest feature is available from version \`0.21.0\`. > \# Fuzzy suggester > > The \`fuzzy\` suggester suggests terms based on edit distance. The provided suggest text is analyzed before terms are suggested. The suggested terms are provided per analyzed suggest text token. The \`fuzzy\` suggester doesn't take the query into account that is part of request. > \# Suggest API > > The suggest request part is defined along side the query part as top field in the json request. > > \`\`\` > curl -s -XPOST 'localhost:9200/\_search' -d '{ > "query" : { > ... > }, > "suggest" : { > ... > } > }' > \`\`\` > > Several suggestions can be specified per request. Each suggestion is identified with an arbitary name. In the example below two suggestions are requested. Both \`my-suggest-1\` and \`my-suggest-2\` suggestions use the \`fuzzy\` suggester, but have a different \`text\`. > > \`\`\` > "suggest" : { > "my-suggest-1" : { > "text" : "the amsterdma meetpu", > "fuzzy" : { > "field" : "body" > } > }, > "my-suggest-2" : { > "text" : "the rottredam meetpu", > "fuzzy" : { > "field" : "title", > } > } > } > \`\`\` > > The below suggest response example includes the suggestion response for \`my-suggest-1\` and \`my-suggest-2\`. Each suggestion part contains entries. Each entry is effectively a token from the suggest text and contains the suggestion entry text, the original start offset and length in the suggest text and if found an arbitary number of options. > > \`\`\` > { > ... > "suggest": { > "my-suggest-1": \[ > { > "text" : "amsterdma", > "offset": 4, > "length": 9, > "options": \[ > ... > \] > }, > ... > \], > "my-suggest-2" : \[ > ... > \] > } > ... > } > \`\`\` > > Each options array contains a option object that includes the suggested text, its document frequency and score compared to the suggest entry text. The meaning of the score depends on the used suggester. The fuzzy suggester's score is based on the edit distance. > > \`\`\` > "options": \[ > { > "text": "amsterdam", > "freq": 77, > "score": 0.8888889 > }, > ... > \] > \`\`\` > \# Global suggest text > > To avoid repitition of the suggest text, it is possible to define a global text. In the example below the suggest text is defined globally and applies to the \`my-suggest-1\` and \`my-suggest-2\` suggestions. > > \`\`\` > "suggest" : { > "text" : "the amsterdma meetpu" > "my-suggest-1" : { > "fuzzy" : { > "field" : "title" > } > }, > "my-suggest-2" : { > "fuzzy" : { > "field" : "body" > } > } > } > \`\`\` > > The suggest text can in the above example also be specied as suggestion specific option. The suggest text specified on suggestion level override the suggest text on the global level. > \# Other suggest example. > > In the below example we request suggestions for the following suggest text: \`devloping distibutd saerch engies\` on the \`title\` field with a maximum of 3 suggestions per term inside the suggest text. Note that in this example we use the \`count\` search type. This isn't required, but a nice optimalization. The suggestions are gather in the \`query\` phase and in the case that we only care about suggestions (so no hits) we don't need to execute the \`fetch\` phase. > > \`\`\` > curl -s -XPOST 'localhost:9200/\_search?search\_type=count' -d '{ > "suggest" : { > "my-title-suggestions-1" : { > "text" : "devloping distibutd saerch engies", > "fuzzy" : { > "size" : 3, > "field" : "title" > } > } > } > }' > \`\`\` > > The above request could yield the response as stated in the code example below. As you can see if we take the first suggested options of each suggestion entry we get \`developing distributed search engines\` as result. > > \`\`\` > { > ... > "suggest": { > "my-title-suggestions-1": \[ > { > "text": "devloping", > "offset": 0, > "length": 9, > "options": \[ > { > "text": "developing", > "freq": 77, > "score": 0.8888889 > }, > { > "text": "deloping", > "freq": 1, > "score": 0.875 > }, > { > "text": "deploying", > "freq": 2, > "score": 0.7777778 > } > \] > }, > { > "text": "distibutd", > "offset": 10, > "length": 9, > "options": \[ > { > "text": "distributed", > "freq": 217, > "score": 0.7777778 > }, > { > "text": "disributed", > "freq": 1, > "score": 0.7777778 > }, > { > "text": "distribute", > "freq": 1, > "score": 0.7777778 > } > \] > }, > { > "text": "saerch", > "offset": 20, > "length": 6, > "options": \[ > { > "text": "search", > "freq": 1038, > "score": 0.8333333 > }, > { > "text": "smerch", > "freq": 3, > "score": 0.8333333 > }, > { > "text": "serch", > "freq": 2, > "score": 0.8 > } > \] > }, > { > "text": "engies", > "offset": 27, > "length": 6, > "options": \[ > { > "text": "engines", > "freq": 568, > "score": 0.8333333 > }, > { > "text": "engles", > "freq": 3, > "score": 0.8333333 > }, > { > "text": "eggies", > "freq": 1, > "score": 0.8333333 > } > \] > } > \] > } > ... > } > \`\`\` > \# Common suggest options: > \- \`text\` - The suggest text. The suggest text is a required option that needs to be set globally or per suggestion. > \# Common fuzzy suggest options > \- \`field\` - The field to fetch the candidate suggestions from. This is an required option that either needs to be set globally or per suggestion. > \- \`analyzer\` - The analyzer to analyse the suggest text with. Defaults to the search analyzer of the suggest field. > \- \`size\` - The maximum corrections to be returned per suggest text token. > \- \`sort\` - Defines how suggestions should be sorted per suggest text term. Two possible value: > \*\\\* \`score\` - Sort by sore first, then document frequency and then the term itself. > \*\\\* \`frequency\` - Sort by document frequency first, then simlarity score and then the term itself. > \- \`suggest\_mode\` - The suggest mode controls what suggestions are included or controls for what suggest text terms, suggestions should be suggested. Three possible values can be specified: > \*\\\* \`missing\` - Only suggest terms in the suggest text that aren't in the index. This is the default. > \*\\\* \`popular\` - Only suggest suggestions that occur in more docs then the original suggest text term. > \*\\\* \`always\` - Suggest any matching suggestions based on terms in the suggest text. > \# Other fuzzy suggest options: > \- \`lowercase\_terms\` - Lower cases the suggest text terms after text analyzation. > \- \`max\_edits\` - The maximum edit distance candidate suggestions can have in order to be considered as a suggestion. Can only be a value between 1 and 2. Any other value result in an bad request error being thrown. Defaults to 2. > \- \`min\_prefix\` - The number of minimal prefix characters that must match in order be a candidate suggestions. Defaults to 1. Increasing this number improves spellcheck performance. Usually misspellings don't occur in the beginning of terms. > \- \`min\_query\_length\` - The minimum length a suggest text term must have in order to be included. Defaults to 4. > \- \`shard\_size\` - Sets the maximum number of suggestions to be retrieved from each individual shard. During the reduce phase only the top N suggestions are returned based on the \`size\` option. Defaults to the \`size\` option. Setting this to a value higher than the \`size\` can be useful in order to get a more accurate document frequency for spelling corrections at the cost of performance. Due to the fact that terms are partitioned amongst shards, the shard level document frequencies of spelling corrections may not be precise. Increasing this will make these document frequencies more precise. > \- \`max\_inspections\` - A factor that is used to multiply with the \`shards\_size\` in order to inspect more candidate spell corrections on the shard level. Can improve accuracy at the cost of performance. Defaults to 5. > \- \`threshold\_frequency\` - The minimal threshold in number of documents a suggestion should appear in. This can be specified as an absolute number or as a relative percentage of number of documents. This can improve quality by only suggesting high frequency terms. Defaults to 0f and is not enabled. If a value higher than 1 is specified then the number cannot be fractional. The shard level document frequencies are used for this option. > \- \`max\_query\_frequency\` - The maximum threshold in number of documents a sugges text token can exist in order to be included. Can be a relative percentage number (e.g 0.4) or an absolute number to represent document frequencies. If an value higher than 1 is specified then fractional can not be specified. Defaults to 0.01f. This can be used to exclude high frequency terms from being spellchecked. High frequency terms are usually spelled correctly on top of this this also improves the spellcheck performance. The shard level document frequencies are used for this option. On Thu, Feb 14, 2013 at 7:49 AM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > Exciting news. I have an idea for a new facet type, but the current > framework is too much work for a feature I do not fully need. > > New fuzzy queries means spell checking soon as well? > > -- > Ivan > > On Thu, Feb 14, 2013 at 12:51 AM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > > > I think the facet framework is going to be overhauled to add custom facet > > features more easily. For example, right now, there can't be plugins that > > add new capabilities to faceting. > > > > So I hope I can use collation based sorting on facet elements soon, or > > facet value mappings, where facet values can be augmented with other values > > for display (like sort keys in collations). > > > > Jörg > > > > Am 14.02.13 09:25, schrieb Leonardo Menezes: > > > > > Hey Shay, > > > that's great news. For the new code in faceting, should we also > > > expect performance improvement, or just memory? thanks > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:51am UTC](https://discuss.elastic.co/t/0-21-0-beta-status-lucene-4-x/10718/10 "2017-07-06T02:51:26Z")