ScanQuery with IgniteBiPredicate fails with Exception 2.16/2.17
Open
- Dominant language
- Java
- Stars
- 5.1k
- Forks
- 1.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
Hello guys, faced absolutely the same issue (Java 17/21) and looks like it's still not fixed - https://issues.apache.org/jira/browse/IGNITE-17866 Could you please confirm if it's still here or maybe there's a way to avoid it (though I've tried a lot of options)?
Contributor guide
Research direction
Start by reviewing the issue body and the linked IGNITE-17866 report, then reproduce the ScanQuery failure with Ignite 2.16 or 2.17 on Java 17 or 21. Done would mean confirming whether the problem remains and documenting a verified workaround or the evidence needed for a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100