Seeking guidance on uncompressed storage options in Lucene 9.7.0

Dear Lucene Community, We're currently using Lucene 4.10.4 with Lucene410Codec for storing fields without compression. However, transitioning to Lucene 9.7.0 presents a challenge as we haven't found a similarly uncompressed codec. Interestingly, even with the Mode.BEST_SPEED compression mode, the

Unsupported queries in Lucene XML CoreParser

We are using Lucene 4.10.4 We parse query in one server and search happens in other servers(RMI call). Since the lucene query object is not serializable, we try to use XML Query Parser

Re: Tokens produced by Shingle filter are not added in the query

u’re printing the output stream from one > (CustomSynynymAnalyzer, the source of which is not shown in your email), > but constructing a query from a different one (CustomAnalyzer). > > -- > Steve > www.lucidworks.com > > > On Jul 24, 2017, at 10:53 AM, hariram ravichandran <

Tokens produced by Shingle filter are not added in the query

I'm using Lucene 4.10.4 and trying to construct (shingles) combinations of tokens. Code: public class CustomAnalyzer extends Analyzer { @Override protected Analyzer.TokenStreamComponents createComponents(final String fieldName, final Reader reader) { final WhitespaceTokenizer src

Decompose compound words

I'm using Lucene 4.10.4 I would like that if a document contains the word *"* *cheeseburger "* and the search for *" cheese burger " or " cheese " or " **burger "* should bring this document. I tried *" DictionaryCompoundWordTokenFilter ". * But it uses a brute-force algorithm. And the words to

Split / Concatenation of search term

Is it possible to handle the split and concatenation of words when a space was inserted in a word or removed between two words? For example, "entert ainment"will match with "entertainment" and "smartwatch" will match with "smart watch".

Re: Query expansion

results (massive recall, poor > precision) to the user! > > Mike McCandless > > http://blog.mikemccandless.com > > > On Mon, Nov 28, 2016 at 6:24 AM, hariram ravichandran > wrote: > > I need to perform *fuzzy search* for the whole search term. I > > extended M

Query expansion

I need to perform *fuzzy search* for the whole search term. I extended MultiFieldQueryParser and overridden getFieldQuery() protected Query getFieldQuery(String field, String fieldText,boolean quoted) throws ParseException{ return *super.getFuzzyQuery(field,fieldText,3.0f); //construct

'OR' search using Automaton query

I use automaton query to combine fuzzy and wildcard query.(for example a query on "*lucy*" should also return "*lucene*"). That's working great. Now, if I search for "*lucy Automaton query*", I want all the documents containing *lucene* or *Automaton* or *query* or *lucene Automaton* or *lucene qu