Re: [I] IndexableField changes its IndexableFieldType when the index is re-opened for reading [LUCENE-7171] [lucene]

woj-tek commented on issue #8226: URL: https://github.com/apache/lucene/issues/8226#issuecomment-2282902978 > So the StringField data should still match against a TermQuery that uses the untokenized word right.. I guess @woj-tek was not seeing that.. Hmm... I think the issue in my cas

Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]

uschindler commented on code in PR #13636: URL: https://github.com/apache/lucene/pull/13636#discussion_r1713051966 ## lucene/core/src/java21/org/apache/lucene/internal/vectorization/MemorySegmentPostingDecodingUtil.java: ## @@ -0,0 +1,109 @@ +/* + * Licensed to the Apache Softwa

Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]

jpountz commented on code in PR #13636: URL: https://github.com/apache/lucene/pull/13636#discussion_r1713050918 ## lucene/core/src/java21/org/apache/lucene/internal/vectorization/MemorySegmentPostingDecodingUtil.java: ## @@ -0,0 +1,109 @@ +/* + * Licensed to the Apache Software

Re: [I] IndexableField changes its IndexableFieldType when the index is re-opened for reading [LUCENE-7171] [lucene]

gautamworah96 commented on issue #8226: URL: https://github.com/apache/lucene/issues/8226#issuecomment-2282867667 @mikemccand > This is indeed irritating, but it is a long standing issue in Lucene It should still match against the original untokenized Term right, when queried