alibaba/QLExpress

为什么自定义符号很多不支持 比如 ≠、≥、≤

Open

#414 opened on Dec 2, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (4,457 stars) (1,113 forks)batch import
help wanted

Description

Caused by: com.alibaba.qlexpress4.exception.QLSyntaxException: [Error SYNTAX_ERROR: rule nextStatement failed predicate: {_input.LA(1) == Token.EOF || _input.LA(1) == QLexer.RBRACE}?] [Near: 1 ≠ 2] ^ [Line: 1, Column: 2] at com.alibaba.qlexpress4.exception.QLException.reportScannerErr(QLException.java:56) at com.alibaba.qlexpress4.aparser.QLErrorListener.syntaxError(QLErrorListener.java:28) at com.alibaba.qlexpress4.a4runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41) at com.alibaba.qlexpress4.a4runtime.Parser.notifyErrorListeners(Parser.java:544) at com.alibaba.qlexpress4.a4runtime.DefaultErrorStrategy.reportFailedPredicate(DefaultErrorStrategy.java:344) at com.alibaba.qlexpress4.a4runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:142) at com.alibaba.qlexpress4.aparser.QLParser.nextStatement(QLParser.java:469)

Contributor guide

Tech stack
java
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaANTLR/parser knowledgeQLExpress grammar
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the QLExpress grammar definition files (e.g., QLParser.g4) to understand current operator parsing. The error occurs in QLParser.nextState(). Determine if symbols like ≠, ≥, ≤ are missing from lexer/parser tokens and add them, mapping to Java operators. Check for existing operator extension mechanisms. Engage with reporter to confirm exact symbol set required.