HyeonUk Kang created ZEPPELIN-6257:
--------------------------------------
Summary: Implement ADD JAR, REMOVE JAR, and SHOW JARS Commands in
Flink Interpreter
Key: ZEPPELIN-6257
URL: https://issues.apache.org/jira/browse/ZEPPELIN-6257
Project: Zeppelin
Issue Type: Task
Components: flink
Affects Versions: 0.12.0
Reporter: HyeonUk Kang
Assignee: HyeonUk Kang
Fix For: 0.12.1
Currently, there are TODOs in
`org.apache.zeppelin.flink.Flink115SqlInterpreter`,
`org.apache.zeppelin.flink.Flink116SqlInterpreter`, and
`org.apache.zeppelin.flink.Flink117SqlInterpreter` related to ADD/REMOVE/SHOW
JAR commands. This feature request aims to address these outstanding tasks by
implementing full support for ADD JAR, REMOVE JAR, and SHOW JARS SQL CLI
commands within the Apache Zeppelin Flink Interpreter.
*Implementation Plan*
1. Add Command Descriptions
Add entries for ADD JAR, REMOVE JAR, and SHOW JARS with clear, concise
descriptions of their syntax and purpose. This ensures that users can discover
these commands using HELP.
2. Define New Operation Types
To allow the Flink Interpreter to parse and identify these new commands,
custom Operation classes need to be defined.
*Create new classes* such as AddJarOperation, RemoveJarOperation, and
ShowJarsOperation. These classes will represent the respective commands and
will hold any necessary information (e.g., jarPath for AddJarOperation).
3. Update the StatementParser
Implement parsing logic to identify ADD JAR '<path>', REMOVE JAR '<path>', and
SHOW JARS statements from the input SQL string.
4. Extend the callOperation Method
Add new else if blocks to check for *instanceof AddJarOperation*, *instanceof
RemoveJarOperation*, and *instanceof ShowJarsOperation*. Each block will then
call a dedicated private method responsible for handling that specific command.
5. Implement Dedicated Command Handler Methods
This is where the core logic for each new command will reside.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
