ShingleFilter produces invalid queries #943
Labels
Milestone
Comments
tohidemyname
pushed a commit
to tohidemyname/lucenenet
that referenced
this issue
Jun 4, 2024
|
My patch is submitted: #944 |
tohidemyname
pushed a commit
to tohidemyname/lucenenet
that referenced
this issue
Jun 5, 2024
tohidemyname
pushed a commit
to tohidemyname/lucenenet
that referenced
this issue
Jun 5, 2024
4 tasks
|
Sorry. I am unfamiliar with submitting pull requests. I may wrongly close my pull request. I have submitted a new pull request. |
paulirwin
pushed a commit
to tohidemyname/lucenenet
that referenced
this issue
Oct 29, 2024
paulirwin
added a commit
that referenced
this issue
Nov 4, 2024
* ShingleFilter produces invalid queries #943 * Add LUCENENET-specific backport comment, fix test name, fix test position and code style --------- Co-authored-by: tohidemyname <tohidemyname> Co-authored-by: Paul Irwin <paulirwin@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Describe the bug
ShingleFilter uses the position length attribute of the token stream to encode the number of terms they put in a single token.
This breaks the query parsing because it creates disconnected graphs.
Expected Behavior
No response
Steps To Reproduce
I will implement a test case to show the bug.
Exceptions (if any)
No response
Lucene.NET Version
No response
.NET Version
8.0.300
Operating System
win 10
Anything else?
No response
The text was updated successfully, but these errors were encountered: