Michael and Forum,-
This is amazing, thanks.
i will try both cases.
i can also have "term1 term2Char1term2Char2*"
and so on with term2's next chars.
I hope the latest version on github for this
class works with Lucene Version 7.7.2.
Best regards
> On Feb 18, 2020, at 8:33 PM, Michael Froh wr
In your example, it looks like you wanted the second term to match based on
the first character, or prefix, of the term.
While you could use a WildcardQuery with a term value of "term2FirstChar*",
PrefixQuery seemed like the simpler approach. WildcardQuery can handle more
general cases, like if yo
Michael and Forum,-
Thanks for thegreat explanations.
one question please:
why is PrefixQuery used instead of WildCardQuery in the below snippet?
Best regards
> On Feb 17, 2020, at 3:01 PM, Michael Froh wrote:
>
> Hi Baris,
>
> The idea with PhraseWildcardQuery is that you can mix literal "
HI Team,
1.We Upgraded Lucene 4.6 to 8+, After upgrading we are facing issue with
UpdateDocument API. We are using UpdateDocument for editing existing records
and adding new records.
2.Adding a new record to the index file is working fine.
3.When we are trying to edit one of record from
