• Need to implement IQueryParser Interface and register as OSGi-Service
  • Methods are called from the framework
  • Idea:
    • Translate Text (query) into sequence of executor commands
    • Execute each executor command on server side

Executor Commands

  • AddQueryCommand -ExecutorCommand:
    • Combine a parser, (query) text and some configurations
    • Is used by our „Mother Language“ Odysseus Script (e.g. #PARSER- and #ADDQUERY-Command)
    • In a query create a call to another compiler
  • Our approach in (now) most cases: Translate to PQL Query
    • No need to handle with the underlying (logical) operator model
    • Easier to maintain
    • Can be easily moved around in the network
  • Other ExecutorCommands for starting, stopping, pausing of queries or creating users, change user rights, ...
  • In our first CQL version: creating user, roles etc. was directly applied from the parser of the data dictionary à Now only the information is encapsulated by the Executor Commands


  • No labels