You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "John Blum (Jira)" <ji...@apache.org> on 2020/11/11 15:58:00 UTC
[jira] [Created] (GEODE-8699) Expose the OQL Parser as a public API
John Blum created GEODE-8699:
--------------------------------
Summary: Expose the OQL Parser as a public API
Key: GEODE-8699
URL: https://issues.apache.org/jira/browse/GEODE-8699
Project: Geode
Issue Type: Wish
Components: querying
Reporter: John Blum
This is a request to have the OQL Parser API used by Apache Geode under the hood be exposed as a public API, consumable by Frameworks and Tooling.
While applications may not have a need to use the OQL Parser API, Frameworks and Tooling most certainly do. For instance, Spring Data for Apache Geode (SDG) is currently parsing and generating OQL queries in the Spring Data Repository infrastructure.
Currently, there is no easy way to consistently parse or generate OQL statements given the API to parse OQL is "internal". This leaves Framework and Tool designers to have to either 1) create a Grammar for OQL and generating a Parser using JavaCC or ANTLR (thereby reinventing the wheel) or 2) resorting to a poor mans recursive descent parser or using simple REGEX and String parsing/concatenation.
#1 is dangerous if Geode's Grammar for OQL ever changes. #2 is error prone at best.
Please consider making the OQL Parser API along with the model for the OQL query components (e.g. projection, predicates, etc) public.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)